This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 13562 - input type=number is listed in table with control of "text box or spinner control."
Summary: input type=number is listed in table with control of "text box or spinner con...
Status: RESOLVED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML a11y APIs (editor: Steve Faulkner, Cynthia Shelly) (show other bugs)
Version: unspecified
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: steve faulkner
QA Contact: HTML a11y API spec bugbot
URL:
Whiteboard:
Keywords: a11y, a11ytf
Depends on:
Blocks:
 
Reported: 2011-08-03 03:03 UTC by Cynthia Shelly
Modified: 2016-02-23 11:52 UTC (History)
11 users (show)

See Also:


Attachments

Description Cynthia Shelly 2011-08-03 03:03:58 UTC
We need to pick one control (perhaps with a fallback) so that we know how to map it to accessibility APIs.
Comment 1 Tab Atkins Jr. 2011-08-03 15:33:17 UTC
The role depends on how the UA implements it.  The UA should provide the appropriate mapping to a11y APIs itself.
Comment 2 Michael[tm] Smith 2011-08-04 05:36:07 UTC
mass-move component to LC1
Comment 3 Anne 2011-08-15 13:39:59 UTC
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.
Comment 4 alexander surkov 2013-06-17 07:00:03 UTC
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
Comment 5 Charles McCathieNevile 2016-02-23 11:52:04 UTC
This is a bug for aria documentation and has been fixed there.