RE: 48 hour CFC: Advance AAMs (Core-AAM, HTML-AAM and ACCAME) to CR

+1 for AccName CFC, we can discuss whatever remains unclear in the upcoming ARIA WG meetings or at TPAC in prep for CR.


Bryan Garaventa
Principal Accessibility Architect
Level Access, Inc.
Bryan.Garaventa@LevelAccess.com
415.624.2709 (o)
www.LevelAccess.com

-----Original Message-----
From: James Nurthen <nurthen@adobe.com> 
Sent: Tuesday, August 30, 2022 10:54 AM
To: public-aria-admin@w3.org
Subject: 48 hour CFC: Advance AAMs (Core-AAM, HTML-AAM and ACCAME) to CR

CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.


This is a Call for Consensus (CfC) to the ARIA Working Group on the question of advancing the "Core Accessibility API Mappings" (Core AAM), "HTML Accessibility API Mappings" (HTML AAM), and "Accessible Name and Description Computation" (ACCNAME) to Candidate Recommendation. The specifications can be found here:

https://w3c.github.io/core-aam/
https://w3c.github.io/html-aam/
https://w3c.github.io/accname/


Action

This CfC is now open for objection, comment, as well as statements of support via email. Silence will be interpreted as support, though messages of support are certainly welcome.

If you object to this proposal, or have comments concerning it, please respond by replying on list to this message no later than 14:00 Boston Time, Thursday, 1 September 2022.

For objections only, please copy the main public-aria@w3.org list to allow technical discussion of the objection to happen there.

Process

This CfC is conducted per the ARIA WG decision policy:
https://www.w3.org/WAI/ARIA/decision-policy

Received on Tuesday, 30 August 2022 22:25:32 UTC