Re: [EXT] CFC - Errata for WCAG 2.1 accessibility supported definition

+1

This seems like a great clarification, especially for web application implementations of location functionality. For example, text directions and content provide the accessible content that a map is unable to at this point in the technology’s evolution. Thank you for documenting this very useful change!

From: Alastair Campbell <acampbell@nomensa.com>
Date: Thursday, January 6, 2022 at 12:33 PM
To: WCAG list (w3c-wai-gl@w3.org) <w3c-wai-gl@w3.org>
Subject: [EXT] CFC - Errata for WCAG 2.1 accessibility supported definition

Call For Consensus — ends Monday January 10th at mid-day Boston time.



The Working Group has discussed a small change to a note on a definition:

https://www.w3.org/TR/WCAG21/#h-note-43



Whilst it is a small change, it is normative therefore we are going through the CFC process.



It was raised in this issue:

https://github.com/w3c/wcag/issues/1758



Discussed and agreed in this meeting:

https://www.w3.org/2022/01/04-ag-minutes.html#t06



The specific changes are detailed in this pull request:
https://github.com/w3c/wcag/pull/1777/files



If you have concerns about this proposed consensus position that have not been discussed already and feel that those concerns result in you “not being able to live with” this decision, please let the group know before the CfC deadline.

Kind regards,

-Alastair

--

@alastc / www.nomensa.com<http://www.nomensa.com>