Intent to implement and ship: ARIA 1.1

52 views
Skip to first unread message

Dominic Mazzoni

unread,
Dec 20, 2016, 1:14:41 PM12/20/16
to blink-dev, Alice Boxhall, nek...@chromium.org
Contact emails

Spec

Summary
The ARIA 1.1 spec has stabilized to the point that we can safely implement and ship it without any compatibility risks.

Is this feature supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)?
Yes

Interoperability and Compatibility Risk
Very low, implementation is under way in Safari and Firefox too.

Entry on the feature dashboard

Requesting approval to ship?
Yes. There's little value in implementing ARIA attributes behind a flag. Typically browsers implement support for an ARIA attribute first, then assistive technology is updated to recognize it (if needed), and finally web developers start adopting it as it becomes more widely supported. Because of the two-sided nature of support (i.e. the new ARIA attributes have no effect until assistive technology is updated to support it too), there's little risk of web developers adopting and depending on an attribute before it's stable.

Notes
We've actually already shipped a bit of ARIA 1.1, mostly trivial changes like role=switch. As this version of the spec is nearly wrapped up and cross-platform test suites are being written, we'd like to complete the implementation in Chrome. Note that relative to the big picture of Chrome accessibility work, implementing ARIA 1.1 is a pretty small piece of it. Most of the changes are very straightforward to implement and provide incremental benefits over existing accessibility support. More of our focus is on improving performance and compatibility of existing accessibility support, and working on more significant spec changes such as the Accessibility Object Model.

Changes in progress:

Dimitri Glazkov

unread,
Dec 20, 2016, 1:16:26 PM12/20/16
to Dominic Mazzoni, blink-dev, Alice Boxhall, nek...@chromium.org
LGTM1

Rick Byers

unread,
Dec 20, 2016, 2:53:35 PM12/20/16
to Dimitri Glazkov, Dominic Mazzoni, blink-dev, Alice Boxhall, nek...@chromium.org
LGTM2

Can you point me to the cross-browser test suite you mentioned is being written?  I'm just curious how this sort of feature is tested for interop.

Chris Harrelson

unread,
Dec 20, 2016, 5:55:33 PM12/20/16
to Rick Byers, Dimitri Glazkov, Dominic Mazzoni, blink-dev, Alice Boxhall, nek...@chromium.org
LGTM3

--
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.

Dominic Mazzoni

unread,
Dec 21, 2016, 5:21:07 PM12/21/16
to Rick Byers, Dimitri Glazkov, blink-dev, Alice Boxhall, nek...@chromium.org
On Tue, Dec 20, 2016 at 11:53 AM Rick Byers <rby...@chromium.org> wrote:
LGTM2

Can you point me to the cross-browser test suite you mentioned is being written?  I'm just curious how this sort of feature is tested for interop.

Rick Byers

unread,
Dec 21, 2016, 5:34:08 PM12/21/16
to Dominic Mazzoni, Dimitri Glazkov, blink-dev, Alice Boxhall, nek...@chromium.org
On Wed, Dec 21, 2016 at 5:20 PM, Dominic Mazzoni <dmaz...@chromium.org> wrote:
On Tue, Dec 20, 2016 at 11:53 AM Rick Byers <rby...@chromium.org> wrote:
LGTM2

Can you point me to the cross-browser test suite you mentioned is being written?  I'm just curious how this sort of feature is tested for interop.


Cool, you guys have thought a lot about thorough interop testing here - thank you!
Reply all
Reply to author
Forward
0 new messages