On 04/29/2015 06:37 PM, James Teh wrote: > On 30/04/2015 3:16 AM, Joanmarie Diggs wrote: >> It's possible to have a name and description and placeholder. > True, but it's also possible to have multiple other things which would > normally get mapped to name or description. That's why we have > precedence rules. :) > >> Beyond that, because the placeholder is the displayed text when the >> input element lacks a value, an AT might wish to present the placeholder >> only when there is not a value. In other words, provide the same >> experience sighted users have. In order to do that, the AT needs to know >> it's a placeholder. Exposing it as the description -- without also >> exposing it as the placeholder -- prevents ATs from being able to do >> that. > Good point. There's an alternative, though: the UA could expose it as a > description only if there is no value. Once there is a value, it isn't > exposed. If the value is cleared, it gets exposed again.
And UAs would also have to emit a signal to indicate the accessible description has changed. Aside from general principle (notify platforms of changes), this would be needed for platforms where caching is done to trigger the cached property to be updated. And what happens if you have an indecisive form-filler-outer who types a character, thinks "no", and BackSpaces. Tries again, reconsiders, and BackSpaces. Should user agents really clear the description, set the description, clear the description, etc., emitting signals each time? <grins> Regardless, this mapping would be inconsistent with happens on my platform for both Gtk+ and WebKitGtk. So if it floats your platform's boat go for it on your platform. Please do not take this approach on mine. --joanie _______________________________________________ Accessibility-ia2 mailing list [email protected] https://lists.linuxfoundation.org/mailman/listinfo/accessibility-ia2
