Re: [Proposal] Addition of ARIA to the accessibilityFeatures list of values

My apologies yes please respond by February 1st 2022 lets say 20:00 UTC (12PM Pacific / 3PM Eastern) since I gave the wrong month :)

Thanks
EOM

Charles LaPierre
Principal, Accessibility Standards, and Technical Lead, Global Certified Accessible
Benetech
Twitter: @CLaPierreA11Y




On Jan 27, 2022, at 10:17 AM, Matt Garrish <matt.garrish@gmail.com<mailto:matt.garrish@gmail.com>> wrote:

> Please respond by March 1, 2022 16:00 UTC

Did you mean February 1, Charles?

We’ve been mulling this for a long time, so a definite +1 from me.

FYI, there’s also an open issue for this if you want to respond there: https://github.com/w3c/a11y-discov-vocab/issues/4


Matt

From: Charles LaPierre <charlesl@benetech.org<mailto:charlesl@benetech.org>>
Sent: January 27, 2022 10:42 AM
To: public-a11y-discov-vocab@w3.org<mailto:public-a11y-discov-vocab@w3.org>
Subject: [Proposal] Addition of ARIA to the accessibilityFeatures list of values

Hello everyone,
As we make improvement on the "Schema.org Accessibility Properties for Discoverability Vocabulary"<https://www.w3.org/2021/a11y-discov-vocab/latest/>

I would like to propose including "ARIA" to the accessibilityFeatures list of values.
Currently we have this under the accessibilityAPI with a definition of:

2.2.2 ARIA: Indicates the resource uses ARIA markup to improve interoperability with platform APIs.


I propose to move "ARIA" from accessibilityAPI to accessibilityFeature instead as I don't feel this makes sense as an accessibilityAPI.

Please respond by March 1, 2022 16:00 UTC if you have any concerns over this proposed change.

Thank You
Accessibility Metadata co-chair
Charles LaPierre


EOM
Charles LaPierre
Principal, Accessibility Standards, and Technical Lead, Global Certified Accessible
Benetech
Twitter: @CLaPierreA11Y