- From: Jon Avila <jon.avila@levelaccess.com>
- Date: Thu, 22 Dec 2022 15:53:29 +0000
- To: "w3c-wai-gl@w3.org" <w3c-wai-gl@w3.org>
- Message-ID: <BL1PR22MB36835F41F664B636F287BE54F1E89@BL1PR22MB3683.namprd22.prod.outlook.com>
702.10..1 says this Web Content Accessibility Guidelines (WCAG) 2.0<http://www.w3.org/TR/WCAG20>, W3C Recommendation, December 11, 2008. So, it is in my opinion it’s locked into the 2008 version – unless some errata would change that. Jonathan From: Andrew Kirkpatrick <akirkpat@adobe.com> Sent: Thursday, December 22, 2022 10:32 AM To: Alastair Campbell <acampbell@nomensa.com>; Wilco Fiers <wilco.fiers@deque.com>; Abou-Zahra, Shadi <sabouzah@amazon.at>; Bruce Bailey <Bailey@Access-Board.gov> Cc: w3c-wai-gl@w3.org Subject: Re: Removing 4.1.1 > What we do know is how these type of regs typically update. > Section 508 is still on 2.0. If you are meeting 508, you have to meet what they have written down, which is from that dated version of 2.0. > They could go through an internal process to update based on WCAG changing, but it is up to them. (How long did people complain about section 508 being on version 1.0?) Bruce can hopefully correct me if I’m wrong, but Section 508 uses https:/www.w3.org/TR/WCAG20 as the normative reference, see https://www.access-board.gov/ict/#702.10.1 So, if WCAG 2.0 was updated via an “Edited Specification” it seems that this would impact Section 508 immediately. AWK
Received on Thursday, 22 December 2022 15:53:48 UTC