Closed
Bug 559761
Opened 15 years ago
Closed 11 years ago
make <input type="number"> accessible
Categories
(Core :: Disability Access APIs, defect)
Tracking
()
RESOLVED
FIXED
mozilla29
People
(Reporter: surkov, Assigned: surkov)
References
(Depends on 2 open bugs, Blocks 1 open bug, )
Details
(Keywords: access, Whiteboard: [qa-])
Attachments
(1 file)
14.28 KB,
patch
|
tbsaunde
:
review+
smaug
:
review+
bkerensa
:
approval-mozilla-aurora+
|
Details | Diff | Splinter Review |
Manage invalid state, expose nsIAccessibleValue
Assignee | ||
Updated•13 years ago
|
Summary: make <input type="number"> accessible → add a11y mochitests <input type="number">
Assignee | ||
Updated•13 years ago
|
Summary: add a11y mochitests <input type="number"> → add a11y mochitests for <input type="number">
Assignee | ||
Comment 1•13 years ago
|
||
changed summary by accident, sorry for spam
Summary: add a11y mochitests for <input type="number"> → make <input type="number"> accessible
Assignee | ||
Comment 2•12 years ago
|
||
per HTML spec (https://dvcs.w3.org/hg/html-api-map/raw-file/tip/Overview.html) we need to expose ROLE_SYSTEM_SPINBUTTON role.
Also see open HTML spec bug https://www.w3.org/Bugs/Public/show_bug.cgi?id=13562
Comment 3•11 years ago
|
||
Assuming the patch for bug lands, the patch for this bug should be sure to back out that patch.
Comment 4•11 years ago
|
||
C&P fail. Comment 3 is referring to bug 927326.
Assignee | ||
Comment 5•11 years ago
|
||
marking it blocking bug a11y q4 bug since bug 635240 seems breaks basic accessibility we have by freshing the layout for the control.
Blocks: 2013q4a11y
Comment 6•11 years ago
|
||
The implementation that's currently in mozilla-central should be complete enough to work on a patch for this now. The dom.forms.number pref just needs to be flipped to true.
Comment 7•11 years ago
|
||
Just pinged surkov about this, and he said he will aim to take a look this week.
Here's a quick summary of the essential things to know: input type=number> contains a native anonymous tree that looks like this:
<input type=number>
<div> - outer wrapper with "display:flex" by default
<input type=text> - text input field
<div> - spinner box wrapping up/down arrow buttons
<div> - spin up (up arrow button)
<div> - spin down (down arrow button)
The anonymous text field grandchild can take focus for the number input. If the a11y code looks at the focused element and it is a text field, it needs to be careful to check HTMLInputElement::ownerNumberControl to see if what it's dealing with is actually a number control and not a text control.
Comment 8•11 years ago
|
||
Also note that the pref is on for v28, so hopefully this can be uplifted. I'm very much hoping to keep it on since Tom's Hardware's Browser Grand Prix puts a fair bit of focus on <input type=number> and there's a reasonable chance v28 will be the next version they test.
Assignee | ||
Comment 9•11 years ago
|
||
Assignee: nobody → surkov.alexander
Status: NEW → ASSIGNED
Attachment #8344953 -
Flags: review?(trev.saunders)
Attachment #8344953 -
Flags: review?(bugs)
Updated•11 years ago
|
Attachment #8344953 -
Flags: review?(bugs) → review+
Comment 10•11 years ago
|
||
Comment on attachment 8344953 [details] [diff] [review]
patch
>+++ b/layout/forms/nsNumberControlFrame.cpp
>+#ifdef ACCESSIBILITY
>+#include "nsAccessibilityService.h"
>+#endif
mozilla/a11y/AccTypes.h should be enough right?
Attachment #8344953 -
Flags: review?(trev.saunders) → review+
Assignee | ||
Comment 11•11 years ago
|
||
Flags: in-testsuite+
Comment 12•11 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla29
Comment 13•11 years ago
|
||
Thank you!
Comment 14•11 years ago
|
||
Comment on attachment 8344953 [details] [diff] [review]
patch
[Approval Request Comment]
Bug caused by (feature/regressing bug #): N/A
User impact if declined: <input type=number> not accessible in v28
Testing completed (on m-c, etc.): landed m-i, merged to m-c
Risk to taking this patch (and alternatives if risky): low and early
String or IDL/UUID changes made by this patch: none
We're early in the cycle so hopefully this is fine to uplift. Probably neded to keep <input type=number> on in v28.
Attachment #8344953 -
Flags: approval-mozilla-aurora?
Comment 15•11 years ago
|
||
So, Jonathan, we do want this in Aurora (Mozilla 28), right?
Comment 16•11 years ago
|
||
(In reply to Jonathan Watt [:jwatt] from comment #14)
> Bug caused by (feature/regressing bug #): N/A
Bug 344616 and its dependencies if you need one to blame.
(In reply to Marco Zehe (:MarcoZ) from comment #15)
> So, Jonathan, we do want this in Aurora (Mozilla 28), right?
Yes, which is why I requested approval.
Updated•11 years ago
|
Comment 17•11 years ago
|
||
Comment on attachment 8344953 [details] [diff] [review]
patch
Review of attachment 8344953 [details] [diff] [review]:
-----------------------------------------------------------------
Looks good we will go ahead approve this for uplift.
Attachment #8344953 -
Flags: approval-mozilla-aurora? → approval-mozilla-aurora+
Assignee | ||
Updated•11 years ago
|
Keywords: checkin-needed
Comment 18•11 years ago
|
||
Comment 19•11 years ago
|
||
Given in-testsuite coverage this fix will not be manually verified by QA. If you believe this warrants extra QA attention please nominate for testing by removing this whiteboard tag and adding the verifyme keyword. Please also provide any details you have that may inform our testing.
Whiteboard: [qa-]
You need to log in
before you can comment on or make changes to this bug.
Description
•