This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
We need to pick one control (perhaps with a fallback) so that we know how to map it to accessibility APIs.
The role depends on how the UA implements it. The UA should provide the appropriate mapping to a11y APIs itself.
mass-move component to LC1
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: <http://dev.w3.org/html5/decision-policy/decision-policy.html>. Status: Rejected Change Description: no spec change Rationale: The exact type of control depends on the UI team and is therefore out of scope of HTML.
Currently the spec says that input@type="number" is equivalent to ARIA spinbutton role and mapped to roles like ROLE_SYSTEM_SPINBUTTON which seems ok because spinbutton role rather means a text edit used to type numbers, in other words related spin buttons used to increment/decrement values are optional. It's worth to add 'Note' section under IAccessible2/ATK saying that the control should implement IAccessibleValue and AtkValue interfaces (https://developer.gnome.org/atk/unstable/AtkValue.html). Events: MSAA EVENT_OBJECT_VALUECHANGE and "accessible-value" ATK signal are fired when value is changed
This is a bug for aria documentation and has been fixed there.