- From: Steve Green <steve.green@testpartners.co.uk>
- Date: Mon, 28 Apr 2025 15:34:09 +0000
- To: Mario Toscano <mario.toscano@spindox.it>, "w3c-wai-ig@w3.org" <w3c-wai-ig@w3.org>
- Message-ID: <PR3PR09MB526837203104F8210C38694FC7812@PR3PR09MB5268.eurprd09.prod.outlook.com>
If an overlay was able to provide an accessible conforming version of a website, that would be acceptable. In principle, an overlay could address some non-conformances, but it depends on what they are. You certainly cannot claim that an overlay will address all the non-conformances on any website, even though some vendors make this claim. In my experience, the overlays on websites we have tested have never been able to address any of the WCAG non-conformances we have reported. Overlays may get better as AI improves, but I doubt that they will ever be able to correctly address more than a small proportion of WCAG non-conformances. If you want to claim conformance, you need to do a full WCAG audit, identify the non-conformances, then determine whether the overlay can address them all. If the website is in really good shape, maybe the overlay can do that. But if that's the case, you may as well fix the non-conformances. If the website is in bad shape, the overlay won't help. Either way, you're better off not using the overlay. WCAG already accommodates overlays. Whether or not the underlying code remains unchanged is irrelevant - all that matters is whether the success criteria are met. My recommendation is to forget about overlays, now and forever. Steve Green Managing Director Test Partners Ltd From: Mario Toscano <mario.toscano@spindox.it> Sent: 28 April 2025 15:54 To: w3c-wai-ig@w3.org Subject: Clarification on AI-Based Accessibility Overlays and WCAG Conformance Dear all, I am reaching out to ask for clarification regarding the use of AI-based overlay tools for web accessibility. Many current solutions on the market claim to make a website accessible through overlay that adds functionalities such as: * text resizing, * color contrast adjustments, * screen reader support, * keyboard navigation, * and simulation of assistive technologies. However, these tools do not modify the original source code or semantic structure of the website. My questions are: 1. According to WCAG 2.1 or 2.2, can a website that relies solely on such AI overlay tools be considered conformant at Level AA? 2. Is the use of such AI-based overlays sufficient for public or private and private organizations to legally declare conformance with WCAG standards? 3. Will future versions of WCAG (e.g., WCAG 3.0) possibly include such overlays as acceptable methods of achieving compliance, even if the underlying code remains unchanged? Thank you very much for your tim. Best regards [Immagine che contiene schermata, Rettangolo, Elementi grafici, design Descrizione generata automaticamente] Mario Toscano SW QA Deputy Director Mobile: +39 340.9569893 E-mail: mario.toscano@spindox.it<mailto:mario.toscano@spindox.it> Linkedin: https://www.linkedin.com/in/mariotoscano1/ [Immagine che contiene nero, oscuritą Descrizione generata automaticamente] ********* Avvertenze Legali - Internet Email Confidentiality Footer ********* Le informazioni contenute in questo messaggio di posta elettronica ed in ogni eventuale allegato sono riservate e confidenziali e ne č vietata la diffusione, in qualunque modo eseguita. Qualora Lei non fosse la persona cui il presente messaggio č destinato, La invitiamo ad eliminarlo e a non leggerlo, dandocene gentilmente comunicazione. / The information contained in this e-mail message and any attachments are confidential and privileged, and its dissemination, in whatever manner executed, is prohibited. If you are not the person for whom this message is intended, please delete it and do not read it and kindly notify us. 2018-2025 © Spindox SpA. All rights reserved. [Image] Aiutaci a rispettare il Pianeta, risparmia la carta. Stampa questa mail solo se davvero necessario. / Help us respect the Planet, save paper. Print this email only if really necessary.
Attachments
- image/png attachment: image001.png
- image/png attachment: image002.png
- image/png attachment: image003.png
Received on Monday, 28 April 2025 15:34:19 UTC