- From: Bradley Montgomery, Rachael L <rmontgomery@loc.gov>
- Date: Mon, 26 Feb 2024 20:06:42 +0000
- To: "WCAG list (w3c-wai-gl@w3.org)" <w3c-wai-gl@w3.org>
- Message-ID: <DS0PR09MB10505A32E1CFBED4FABA6DEA6AB5A2@DS0PR09MB10505.namprd09.prod.outlook.co>
+1 Rachael ________________________________ From: David Cox <dav.idcox@outlook.com> Sent: Monday, February 26, 2024 2:58 PM To: Alastair Campbell <acampbell@nomensa.com> Cc: WCAG list (w3c-wai-gl@w3.org) <w3c-wai-gl@w3.org> Subject: Re: CFC - Update definition for single pointer CAUTION: This email message has been received from an external source. Please use caution when opening attachments, or clicking on links. +1 Thanks! David Cox ________________________________ From: Alastair Campbell <acampbell@nomensa.com> Sent: February 26, 2024 7:08 AM To: WCAG list (w3c-wai-gl@w3.org) <w3c-wai-gl@w3.org> Subject: CFC - Update definition for single pointer Call For Consensus — ends Tuesday March 5th at 2pm Boston time. Erratum to change to the definition of “Single Pointer”: * Current definition<https://urldefense.com/v3/__https://www.w3.org/TR/WCAG22/*dfn-single-pointer__;Iw!!EDx7F7x-0XSOB8YS_BQ!cfdnypjUVxCvku8-X8aRjI6p0rhrjIoVtcFI-yKPTPmCZkC9yo_UOPF6KUTalktk6qhhAnTO84pAj33jcAhN4A$>; * Issues 3535<https://urldefense.com/v3/__https://github.com/w3c/wcag/issues/3535__;!!EDx7F7x-0XSOB8YS_BQ!cfdnypjUVxCvku8-X8aRjI6p0rhrjIoVtcFI-yKPTPmCZkC9yo_UOPF6KUTalktk6qhhAnTO84pAj30rN7LecQ$>, 749<https://urldefense.com/v3/__https://github.com/w3c/wcag/issues/749*issuecomment-494146357__;Iw!!EDx7F7x-0XSOB8YS_BQ!cfdnypjUVxCvku8-X8aRjI6p0rhrjIoVtcFI-yKPTPmCZkC9yo_UOPF6KUTalktk6qhhAnTO84pAj327DslqIA$>. * Proposed update<https://urldefense.com/v3/__https://github.com/w3c/wcag/pull/3536__;!!EDx7F7x-0XSOB8YS_BQ!cfdnypjUVxCvku8-X8aRjI6p0rhrjIoVtcFI-yKPTPmCZkC9yo_UOPF6KUTalktk6qhhAnTO84pAj31urQc7mQ$> (file view<https://urldefense.com/v3/__https://github.com/w3c/wcag/pull/3536/files__;!!EDx7F7x-0XSOB8YS_BQ!cfdnypjUVxCvku8-X8aRjI6p0rhrjIoVtcFI-yKPTPmCZkC9yo_UOPF6KUTalktk6qhhAnTO84pAj33qpsSF5Q$>). It would apply to WCAG 2.1 and 2.2, and be listed as an errata until the next time the document is re-published. When re-published the change would appear on the face of the specification. This has been discussed and iterated in the WCAG 2 Task Force several times, and discussed in the AG meeting: https://www.w3.org/2024/02/20-ag-minutes#item03<https://urldefense.com/v3/__https://www.w3.org/2024/02/20-ag-minutes*item03__;Iw!!EDx7F7x-0XSOB8YS_BQ!cfdnypjUVxCvku8-X8aRjI6p0rhrjIoVtcFI-yKPTPmCZkC9yo_UOPF6KUTalktk6qhhAnTO84pAj33cItPS4A$> (towards the bottom of that section) 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<https://urldefense.com/v3/__http://www.nomensa.com/__;!!EDx7F7x-0XSOB8YS_BQ!cfdnypjUVxCvku8-X8aRjI6p0rhrjIoVtcFI-yKPTPmCZkC9yo_UOPF6KUTalktk6qhhAnTO84pAj32ibC6HHw$>
Received on Monday, 26 February 2024 20:22:31 UTC