- From: Janina Sajka <janina@a11y.nyc>
- Date: Mon, 29 Sep 2025 05:58:37 -0400
- To: Lionel Wolberger <lionel.wolberger@levelaccess.com>
- Cc: Accessibility at the Edge <public-a11yedge@w3.org>
Done, but please read on ... I edited Lionel's language quite a bit. Opinions most appreciated. I cross referenced our Introduction where we note today's web page is a mashup. I added a link to the WAI Accessibility Statement Generator. I also provided cross references to the previous "Accessibility Statement" and the following accessibility bug tracking sections. Lionel Wolberger writes: > 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 -- Janina Sajka (she/her/hers) Accessibility Consultant https://linkedin.com/in/jsajka The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI) Co-Chair, Accessible Platform Architectures http://www.w3.org/wai/apa Linux Foundation Fellow https://www.linuxfoundation.org/board-of-directors-2/
Received on Monday, 29 September 2025 09:58:42 UTC