[meta] Support ARIA Annotations
Categories
(Core :: Disability Access APIs, enhancement)
Tracking
()
People
(Reporter: aaronlev, Unassigned)
References
(Depends on 1 open bug, Blocks 1 open bug)
Details
(Keywords: dev-doc-complete, meta)
Explainer: https://github.com/aleventhal/aria-annotations
The explainer links to GitHub issues and pull requests for the ARIA spec.
Here is the Chrome issue where we've been implementing stuff, it links to the code changes. Most of it is straightforward.
Updated•4 years ago
|
Comment 1•4 years ago
•
|
||
Release Note Request (optional, but appreciated)
[Why is this notable]: New properties for accessible rich internet applications, for authors to use.
[Affects Firefox for Android]: No.
[Suggested wording]: Firefox now supports the new WAI-ARIA 1.3 draft proposed annotation roles "suggestion", "mark", and "comment", as well as the aria-description property. In addition, aria-details can be given multiple element IDs as references.
[Links (documentation, blog post, etc)]: Intent to prototype and ship: ARIA annotations.
Comment 2•4 years ago
|
||
This might be more suited for the developer-focused notes on MDN than the main user-facing release notes?
Comment 3•4 years ago
|
||
Dependent bugs have a test in the test suite, don't need manual testing.
Comment 5•4 years ago
|
||
We already documented this in the 75 cycle, and put it in the MDN 75 rel notes: https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Releases/75#Accessibility
With caveats about what support actually means at this point.
Were we wrong to do that? What has changed in 76?
Comment 6•4 years ago
|
||
Sounds like we're good here.
Description
•