Hi Steve,
On 2015-04-28 9:44 AM, Steve Faulkner wrote:
On 28 April 2015 at 14:33, Joseph Scheuhammer <[email protected]
<mailto:[email protected]>> wrote:
Thus, the text above regarding @placeholder vs. @aria-placeholder
belongs in the HTML-AAM.
gotcha,
a few questions is aria-placeholder ever to be used as fallback for
accname/description calculation?
It's under discussion.
My position is that, yes, aria-placeholder text can be used as a
fallback for a name, but the decision should be left to the AT. The
placeholder text should be mapped to a "placeholder" property in all
cases, and if the accessible has no "name" property, then the AT can use
other properties as alternatives, including the "placeholder" property.
That way the AT knows that it's using placeholder text for the name.
In short, placeholder should not be part of the accname/description
calculation done by the user agent.
note: aria-desribedby is not used as fallback for accname.
Right. But (pure speculation ahead), if an accessible has no name, and
only a description property, I'm guessing ATs use the description for
the name as a fallback.
do we have the slots for placeholder in all API's?
I don't know about UIA yet. AXAPI has an AXPlaceHolderValue property.
ATK/AT-SPI is going to use an object attribute for the time being, but
is considering adding a new "placeholder" property. And, Alex has
likewise proposed using an object property for IA2.
--
;;;;joseph.
'Array(16).join("wat" - 1) + " Batman!"'
- G. Bernhardt -
_______________________________________________
Accessibility-ia2 mailing list
[email protected]
https://lists.linuxfoundation.org/mailman/listinfo/accessibility-ia2
