Btw, Joseph, I didn't really suggested to change GTK+ mappings :)
Oh, sorry, I didn't mean to imply that. The point was that the mapping
for placeholder for GTK (desktop) widgets is inconsistent with widgets
in webpages, and that the HTML mapping spec is not backward compatible
with that. Put another way: the proposed mapping of aria-placeholder
is backward compatible with GTK mappings.
Joanie wrote:
FWIW, it was made years ago and by several developers (which I point out
simply because this isn't something I just decided for this new mapping
which we could turn around and change in order to be closely synced).
changing it there now obviously isn't an option. In that case,
this discussion is purely academic for you.
As long as Alex agrees, then you are correct regarding it being purely
academic for me.
There might be a sense in which it isn't purely academic. *If* we
decide that aria-placeholder is mapped to the acc name or acc
description in certain cases, then we should avoid making exceptions
based on the a11y platform. The accessible name spec would change near
step 2G [1], to something like:
"Otherwise, if the current node has a non-empty aria-placeholder
attribute, return the value of aria-placeholder".
But not:
"Otherwise, if the current node has a non-empty aria-placeholder
attribute, and the AAPI is not ATK/AT-SPI, return the value of
aria-placeholder".
[1] http://w3c.github.io/aria/accname-aam/accname-aam.html#step2G
--
;;;;joseph.
'Array(16).join("wat" - 1) + " Batman!"'
- G. Bernhardt -
_______________________________________________
Accessibility-ia2 mailing list
[email protected]
https://lists.linuxfoundation.org/mailman/listinfo/accessibility-ia2
