- From: Lionel Wolberger <lionel.wolberger@levelaccess.com>
- Date: Sun, 28 Sep 2025 15:48:48 +0000
- To: Accessibility at the Edge <public-a11yedge@w3.org>
- Message-ID: <LV3PR22MB5870D9BCEA6B2E3466675F429518A@LV3PR22MB5870.namprd22.prod.outlook.com>
Hi all, 5.4.4 had no benefit section. As part of adding the missing section, I found it also needing * More accuracy regarding which accessibility provider is being discussed: there could be many in the supply chain * We should broaden this to enable exposure of things other than a company name, e.g., the use of a tool in the CI/CD pipeline For your consideration: 5.4.4 Support Accessibility Solutions Provenance Identification This capability provides users with information regarding the accessibility solutions that are employed to ensure the accessibility of the site. Users may identify the source or provider of accessibility services, whether by company name, logo, a document or signed statement. This may be part of the accessibility statement, VPAT or related machine-readable list. [CONSIDER LINK HERE TO WAI ADAPT WELL KNOWN DESTINATIONS WORK] Source Source likely has information regarding accessibility solutions that contributed to the experience. Trade-Offs Users deserve to know who is responsible for their experience of web content. While the content source is the authority on source production, the website may well include services whose accessibility is opaque. Benefit The modern web page is a mashup and the website source may not even know who is the accessibility provider of the services that render in the final result, such as a clickable advertisement. Post-source provides an opportunity to afford access to accessibility information about every service on the page. Automatability In some cases for in-source; in many cases, for post-source services. -- Lionel Wolberger, Ph.D. VP Business Operations Level Access https://levelaccess.com https://userway.org
Received on Sunday, 28 September 2025 15:48:54 UTC