Closed
Bug 1732280
Opened 3 years ago
Closed 2 years ago
Implement/fix mappings for sub, sup elements and subscript, superscript roles
Categories
(Firefox :: Disability Access, defect)
Firefox
Disability Access
Tracking
()
RESOLVED
FIXED
106 Branch
Tracking | Status | |
---|---|---|
firefox106 | --- | fixed |
People
(Reporter: jdiggs, Assigned: nlapre)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
(deleted),
text/x-phabricator-request
|
Details |
Steps to reproduce:
- Load
data:text/html,<sub>foo</sub> <sup>bar</sup>
- Use a platform accessibility inspector (e.g. Accerciser) to examine the roles
Expected results:
- Each element would be in the accessibility tree with ROLE_SUBSCRIPT and ROLE_SUPERSCRIPT respectively
Actual results:
- The elements are not in the accessibility tree; the text is exposed in the parent
Changing the test case to use the ARIA 1.2 subscript and superscript roles on a div causes the elements to appear in the tree, but exposed as ROLE_SECTION.
Reporter | ||
Comment 1•3 years ago
|
||
BTW, on the mac the expected subroles are AXSubscriptStyleGroup and AXSuperscriptStyleGroup.
Assignee | ||
Updated•2 years ago
|
Assignee: nobody → nlapre
Assignee | ||
Comment 2•2 years ago
|
||
This commit adds mappings for HTML sub and sup elements, as well as ARIA
role mappings for subscript, superscript roles, with the goal of properly
exposing this information to the accessibility tree. Further, this commit
updates tests to verify that the role information is working properly.
Pushed by nlapre@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/a6cbe6d5f56f
Implement mappings for sub, sup elements and subscript, superscript roles, r=Jamie
Comment 4•2 years ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 2 years ago
status-firefox106:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 106 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•