Re: Decision: Advance Core AAM, HTML AAM and ACCNAME to CR

Bryan,
This gives the ability to advance the spec. It does not obligate us to do so right now.
Regards,
James

From: Bryan Garaventa <bryan.garaventa@levelaccess.com>
Date: Tuesday, October 4, 2022 at 11:30 AM
To: James Nurthen <nurthen@adobe.com>, public-aria-admin@w3.org <public-aria-admin@w3.org>
Cc: ARIA <public-aria@w3.org>
Subject: RE: Decision: Advance Core AAM, HTML AAM and ACCNAME to CR

EXTERNAL: Use caution when clicking on links or opening attachments.


Hi,
I have concerns about AccName based on our last meeting discussion about the AccName protocol for dealing with recursive roles, so can AccName be postponed as advancement to CR until I can submit the proposal and we can discuss in the next meeting?

This may be simpler to fix than expected.


Bryan Garaventa
Principal Accessibility Architect
Level Access, Inc.
Bryan.Garaventa@LevelAccess.com<mailto:Bryan.Garaventa@LevelAccess.com>
415.624.2709 (o)
www.LevelAccess.com<http://www.LevelAccess.com>

From: James Nurthen <nurthen@adobe.com>
Sent: Tuesday, October 4, 2022 10:23 AM
To: public-aria-admin@w3.org
Subject: Decision: Advance Core AAM, HTML AAM and ACCNAME 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.


The CfC to advance "Core Accessibility API Mappings" (Core AAM), "HTML Accessibility API Mappings" (HTML AAM), and "Accessible Name and Description Computation" (ACCNAME) to Candidate Recommendation
 received only votes of support [1]

Therefore, it is agreed as a decision of the ARIA Working Group to advance "Core Accessibility API Mappings" (Core AAM), "HTML Accessibility API Mappings" (HTML AAM), and "Accessible Name and Description Computation" (ACCNAME) to Candidate Recommendation.





[1] - https://lists.w3.org/Archives/Public/public-aria-admin/2022Aug/0001.html