Intent to implement: Accessibility Object Model

[Dominic Mazzoni]

Contact emails dmaz...@chromium.org, abox...@chromium.org Spec Explainer

Spec

Summary This effort aims to create a JavaScript API to allow developers to modify (and eventually explore) the accessibility tree for an HTML page. Motivation Fill in the gaps in ARIA. Reduce pain points for developers who want to make their sites accessible. Shrink the gap between the expressiveness of web and native accessibility APIs.

Interoperability risk Firefox: Public support Safari: Public support
Edge: Public skepticism Web developers: No signals

Compatibility risk Low. This would be all new APIs.

Ongoing technical constraints None Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)? Yes or no. Yes OWP launch tracking bug https://crbug.com/680345 Link to entry on the Chrome Platform Status https://www.chromestatus.com/features/6643371200217088 Requesting approval to ship?

No

[PhistucK]

On Fri, Mar 17, 2017 at 8:28 AM, Dominic Mazzoni <dmaz...@chromium.org> wrote:

Low. This would be all new APIs.

​Have you checked whether there are collisions?

element.accessibleNode

AccessibleNode​

​Did you find any code that currently uses those terms as fields or global variables (using GitHub, HTTPArchive, internal crawler search)?

This is the only compatibility risk I can think of at the moment.​

☆PhistucK

[mbr...@gmail.com]

The documentation links on Chrome Platform Status are a bit messed up

[PhistucK]

Fixed, thank you. Should go live soon.

☆PhistucK

--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscribe@chromium.org.