- From: Joseph Scheuhammer <clown@alum.mit.edu>
- Date: Fri, 06 Mar 2015 15:42:22 -0500
- To: Birkir Gunnarsson <birkir.gunnarsson@deque.com>, "'Bryan Garaventa'" <bryan.garaventa@ssbbartgroup.com>, "'Joseph Scheuhammer'" <clown@alum.mit.edu>, "'Joanmarie Diggs'" <jdiggs@igalia.com>, "'James Nurthen'" <james.nurthen@oracle.com>
- CC: "'W3C WAI Protocols & Formats'" <public-pfwg@w3.org>
Hi Birkir,
> What about allowing aria-selected on buttons?
> This button would be selected in the sense that when you press enter it will get activated.
It's better to declare something explicitly, than to rely on
inferences. From that perspective, declaring a button specifically as
the primary is more revealing than using aria-selected, and leaving it
to the AT to determine what selected means in this context.
However, a better guide is what a11y APIs offer in terms of the proposed
functionality, and at least two of them support the relevant state.
ATK/AT-SPI has a STATE_DEFAULT, which is separate from STATE_SELECTED,
and is defined as:
'Indicates that the object is the "default" active component, i.e. the
object which is activated by an end-user press of the "Enter" or
"Return" key. Typically a "close" or "submit" button.'
Likewise, MSAA has STATE_SYSTEM_DEFAULT defined as "the default button
in a window". I'm not sure about AXAPI nor UIA, but I would be
surprised if they didn't have something similar (and if they don't, they
should).
--
;;;;joseph.
'Array(16).join("wat" - 1) + " Batman!"'
- G. Bernhardt -
Received on Friday, 6 March 2015 20:42:57 UTC