On 30/04/2015 10:26 AM, Joanmarie Diggs wrote:
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.
Sure. There's already such a signal on Windows, though I don't think
Gecko actually fires it... :)
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?
Well, that's kinda what happens visually, no? The placeholder disappears
and reappears each time. Arguably, continually exposing the placeholder
via an object attribute is actually contrary to the UX of a sighted
user, since a sighted user can't see the placeholder when the field has
a value.
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.
Fair enough. We've tried to keep IA2 and ATK fairly closely synced to
unify things/make things easier, but if you've already made this choice
for ATK, changing it there now obviously isn't an option. In that case,
this discussion is purely academic for you.
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
