W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > January to March 2017

RE: Feedback wanted on new JavaScript library

From: Bryan Garaventa <bryan.garaventa@ssbbartgroup.com>
Date: Fri, 17 Mar 2017 15:42:04 +0000
To: Tobias Bengfort <tobias.bengfort@posteo.de>, Matt King <a11ythinker@gmail.com>, 'WAI IG' <w3c-wai-ig@w3.org>
Message-ID: <BN6PR03MB2785CB7E98AC761005CE81E898390@BN6PR03MB2785.namprd03.prod.outlook.com>
As an FYI, there is an accessible name calculation script included in the download at

Which includes CSS pseudo element algorithms for adding CSS rendered content within the naming calculation for setting both the Name and Description properties according to spec.

Bryan Garaventa
Accessibility Fellow
SSB BART Group, Inc.
415.624.2709 (o)

-----Original Message-----
From: Tobias Bengfort [mailto:tobias.bengfort@posteo.de] 
Sent: Thursday, March 16, 2017 12:21 AM
To: Matt King <a11ythinker@gmail.com>; 'WAI IG' <w3c-wai-ig@w3.org>
Subject: Re: Feedback wanted on new JavaScript library

On 15/03/17 23:34, Matt King wrote:
>> aria-api is a set of functions to get ARIA informatiom from the DOM
> Since the information is coming from the DOM rather than the browser's accessibility tree, does that mean that aria-api is implementing the accessible name calculation?

Yes. (But not perfectly yet)

>> AOM is a draft spec
> How much functional overlap do you see between AOM and aria-api?

aria-api allows to access ARIA information that is available in the DOM.
In that sense, it is similar to AOM Phase 4. The Syntax would likely be different tough.

However, once AOM Phase 1 was implemented and the roles and attributes could be changed without setting `aria-` attributes on the nodes, aria-api would need to adapt to that.


Received on Friday, 17 March 2017 15:42:39 UTC

This archive was generated by hypermail 2.3.1 : Friday, 17 March 2017 15:42:42 UTC