On 29/04/2015 12:08 AM, Joseph Scheuhammer wrote:
a few questions is aria-placeholder ever to be used as fallback for
accname/description calculation?
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.
Pardon my lack of awareness here; I'm coming into this discussion cold
and am not part of the W3C working groups. Feel free to point me at a
thread or something. I'm curious as to why placeholder shouldn't be
exposed as the description by UAs. There's certainly an argument for
giving the AT as much choice as possible, but there's also an argument
for abstraction. The placeholder essentially describes what a user might
enter into the field, so it would seem to amp to description quite well
where a label is already present. I don't quite follow why ATs would
want to differentiate this in such a major way as to not have it exposed
as the description. To put this another way, I can possibly understand
wanting to have an attribute like description-from-placeholder:true or
something for ATs that really want this for some reason, but I'd imagine
that in the majority of cases, this wouldn't be used. Am I missing
something obvious here?
Jamie
--
James Teh
Executive Director, NV Access Limited
Ph +61 7 3149 3306
www.nvaccess.org
Facebook: http://www.facebook.com/NVAccess
Twitter: @NVAccess
SIP: [email protected]
_______________________________________________
Accessibility-ia2 mailing list
[email protected]
https://lists.linuxfoundation.org/mailman/listinfo/accessibility-ia2
