Support ARIA Annotation roles in Automation API, ChromeVox screen reader

Support the new markup in the ARIA annotations editor’s draft (5 new roles): annotation-attribution, annotation-commentary, annotation-presence, annotation-revision, annotation-suggestion. The new roles will be reflected in the ChromeOS Automation API, and a UX will be developed for them in ChromeVox. The rest of the draft spec does not require additional core implementation as it simply reuses existing markup that is already implemented in browsers.

To support screen reader accessibility of comments, suggestions and other annotations in published documents and online word processing scenarios such as Google Docs, iCloud Pages, and MS Office Online. This is not currently possible without resorting to live region hacks, which are not as reliable as semantics and do not work well with Braille displays. As a result, screen reader users have non-optimal support for collaboration features of online word processors.




Editor's draft

Status in Chromium


Proposed (tracking bug)

Consensus & Standardization

After a feature ships in Chrome, the values listed here are not guaranteed to be up to date.

  • No public signals
  • No public signals
  • No public signals
  • No signals


Intent to Implement url

Intent to Implement thread

Last updated on 2019-10-09