Closed
Bug 1378160
Opened 7 years ago
Closed 7 years ago
The ARIA region role should be exposed as a landmark; not a pane
Categories
(Core :: Disability Access APIs, defect)
Core
Disability Access APIs
Tracking
()
RESOLVED
FIXED
mozilla56
| Tracking | Status | |
|---|---|---|
| firefox56 | --- | fixed |
People
(Reporter: jdiggs, Assigned: jdiggs)
References
Details
Attachments
(1 file, 1 obsolete file)
|
(deleted),
patch
|
MarcoZ
:
review+
|
Details | Diff | Splinter Review |
In ARIA 1.1, region became a landmark*. As such it is expected to be exposed as a landmark. But currently region maps to Gecko's panel role, which in turn maps to the generic group/container role in platform accessibility APIs.
*Note that as a landmark, it is expected to have an author-provided name. If it lacks an author-provided name, then the mapping should be based on the native host language according to the Core AAM. Addressing that scenario is bug 1358462.
|
Assignee | |
Comment 1•7 years ago
|
||
|
|
Assignee | |
Comment 2•7 years ago
|
||
Comment on attachment 8883326 [details] [diff] [review]
patch
Clearing the r? flag for now. While this simple patch fixes this simple bug, we still need to deal with bug 1358462, and fixing that bug may be easier if we have a dedicated internal REGION role immediately distinguishable from the internal LANDMARK role. In which case, might as well make the REGION role here....
Attachment #8883326 -
Attachment description: proposed patch → patch
Attachment #8883326 -
Flags: review?(mzehe)
|
|
Assignee | |
Comment 3•7 years ago
|
||
Attachment #8883326 -
Attachment is obsolete: true
Attachment #8883429 -
Flags: review?(mzehe)
|
||
Updated•7 years ago
|
Attachment #8883429 -
Flags: review?(mzehe) → review+
|
|
Assignee | |
Updated•7 years ago
|
Keywords: checkin-needed
Pushed by ryanvm@gmail.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/9bf712264165
The ARIA region role should be exposed as a landmark; not a pane. r=MarcoZ
Keywords: checkin-needed
|
||
Comment 5•7 years ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
status-firefox56:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla56
You need to log in
before you can comment on or make changes to this bug.
Description
•