Qui, Ouai, but .. that's when you "replace" labels for hintText. You can use the hinText as a descriptive info.
BTW the whole "accessibility" thing is a whole new world for lots of us. Maybe HTML interfaces will be more useful in that case, since things have been defined already for html (if I remember well what I read somewhere).
I read "Handle with care to improve not ruin user experience."
REF Mozilla's detailed documentation:
(1) PLACEHOLDER - is a brief hint to the user as to what kind of information is expected in the field. It should be a word or short phrase that demonstrates the expected type of data, rather than an explanatory message.
(2) PLACEHOLDER - is not as semantically useful as other ways to explain your form, and can cause unexpected technical issues with your content.
Indeed, I would only use this for a hint type of information. But in windows apps it really is not necessary. Placeholders have been more widely used in Mobile UIs where the space for labels is not there. It's another thing that people think is nice but is relatively useless :)
FWIW ... PowerServer has already had this feature for many releases and calls it "HintText". I have opened a support ticket suggesting that Appeon use the same feature name for all products for consistency.
I'm on the beta R2 and I checked: I only see this new property on single line edits. Not on edit mask, nor multi line edits. To be honest, I would have expected it to be available at least also for mle, but it's not (yet?). Neither am I seeing it for columns on a datawindow, while that would be probably the most useful place to have the new property.
This is from the help file:
"Other new features related with PowerScripts or PowerBuilder objects are as below:
Supports Placeholder property for SingleLineEdit control -- The Placeholder property specifies a short description for the expected value of the input field. The Placeholder value can be used as a text label or hint; hence can help to reduce the number of UI controls. The Placeholder value will not be displayed, 1) if the Text property is set (the Text value will be displayed first); or 2) when the input field has focus."
Let's do a feature request?
Before anyone says we can use the "tag" property, many times, the tag property is already used for many things like when you have a dynamic translation running on labels, etc.. Not impossible to add some functionality that separates different things out of a tag string, but it would be nice to have this new feature and just use it only for what it's intended.