- From: Sailesh Panchang <sailesh.panchang@deque.com>
- Date: Wed, 4 Jan 2023 15:53:24 -0500
- To: "w3c-waI-gl@w3. org" <w3c-wai-gl@w3.org>
- Cc: Gregg Vanderheiden <gregg@vanderheiden.us>, John Foliot <john@foliot.ca>, "Abou-Zahra, Shadi" <sabouzah@amazon.at>, Sheri Byrne Haber <sbyrnehaber@vmware.com>, Alastair Campbell <acampbell@nomensa.com>
I agree with all of Shadi's comments so far. But I do not believe W3C needs to seek permission of the EU's standards body or the US Access Board for making this change just like it does not need their go ahead for coming up with a new version of WCAG2.X . As technologies evolve, it is fair that standards and guidance are revised. Note that, every EU directive requires conformance with the current relevant "EN” standard(s) published in EU's Official Journal at the time the directive goes into force, which leaves room for standards to evolve with technology. This means the directives do not have to be updated when a referenced technical standard undergoes an update. Even the 2014 Procurement Directive referred to “design for all” (in Article 42), though the first version of EN 17161 “Design for All” standard came into existence only five years later. The S508 regulations are not flexible in that manner though. Is it right to say that even US Gov agencies or some of their contractors test against WCAG 2.1 voluntarily though S508 does not mandate 2.1? Also consider that new versions or updates to browsers and software happen all the time. Their makers do not seek permission of the user community. Yes sometimes one has the option not to accept the upgrade but this choice is limited. Thanks, -- Sailesh Panchang Customer Success Strategist and Principal Accessibility Consultant Deque Systems Inc 381 Elden Street, Suite 2000, Herndon, VA 20170 Mobile: 571-344-1765
Received on Wednesday, 4 January 2023 20:53:41 UTC