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.
Created attachment 8883326 [details] [diff] [review] patch
Assignee: nobody → jdiggs
Status: NEW → ASSIGNED
Attachment #8883326 - Flags: review?(mzehe)
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....
Created attachment 8883429 [details] [diff] [review] proposed patch
Pushed by firstname.lastname@example.org: https://hg.mozilla.org/integration/mozilla-inbound/rev/9bf712264165 The ARIA region role should be exposed as a landmark; not a pane. r=MarcoZ
Status: ASSIGNED → RESOLVED
Last Resolved: 2 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.