- From: Janina Sajka <janina@rednote.net>
- Date: Wed, 5 Feb 2025 08:01:47 -0500
- To: Kevin White <kevin@w3.org>
- Cc: Lionel Wolberger <lionel.wolberger@levelaccess.com>, Accessibility at the Edge <public-a11yedge@w3.org>, team-wai-archive@w3.org
Hi Kevin: Really happy to have you in this conversation. Let me provide just a bit of context ... The Accessibility at the Edge (A11yEdge) Community Group wants to wrap up their report--preferably this month: https://A11yEdge.github.ios/capabilities/ Lionel's diagram is intended to graphically/textually summarize this specific report document. It is my intention to pull this CG report into APA via my proposed Xtech TF (Work Statement coming soon!). I've spoken with Matthew whose reaction is: "Great in theory, but it doesn't work." So, I'm not sure how we engaged you at this specific time, but very happy to have your engagement. It has certainly been my intent to widen the conversation. Note the authorship on the report 3 of the 4 companies working in post-source a11y remediation. Needless to say yours truly will not render the dispositive opinion on any graphic! :) Best, Janina Kevin White writes: > Hi Lionel, > > I have a few thoughts on this diagram. I am not sure it adequately captures or reflects the full stack of components that are involved in delivery of the final user experience. We do have a page which talks about the Essential Components of Web Accessibility <https://www.w3.org/WAI/fundamentals/components/>. It is in need of a wee refresh but it does try to outline the major components involved in delivering an accessible experience. I feel the proposed diagram downplays the significance of a both the content creation and content delivery. What I mean by that is that there is plenty that could be done in the first bubble by authoring tools, for example, and there is a huge amount that goes in in the last section in the browser. > > Just wondering how the broader view might be incorporated into this diagram. > > Thanks > > Kevin > > > On 29 Jan 2025, at 20:56, Lionel Wolberger <lionel.wolberger@levelaccess.com> wrote: > > > > Dear Community Group, > > > > We revised the diagram based on today???s discussion. > > The diagram is attached here and described below. > > > ??? > > > > The diagram represents a model where post-source adaptations enhance accessibility beyond the original content provided by the publisher. Here???s a breakdown of its structure: > > 1. Content Publisher (Content/Code) ??? At the top is the starting point, where the original web content or code is created by the publisher. The publisher has the sole authority to configure, or allow, any post-source adaptations to be called into play. > > 2. Post-Source A, B, C ??? These represent various post-source accessibility modifications or enhancements that occur after the content is published. Examples include (a) Automated or third-party-generated captions for videos (b) image alternative texts (c) personalization widgets and many other adaptations described in the document. > > 3. Client User???s Tools (e.g., Browser, AT) ??? This is the endpoint where the content is consumed by the user. The client cannot easily distinguish the provenance of all the content and adaptations, which are processed equally for rendering by the end-user???s user agent and its ecosystem. Assistive technologies (AT), such as screen readers, browsers, or other user-side tools, integrate the post-source modifications for improved accessibility, and are consumed on the end user???s devices. > > > > The diagram visually conveys the concept that accessibility is not solely dependent on the content publisher but can be enhanced through external post-source mechanisms before reaching the user. Let me know if you need a refined version or additional context! > > > > > > The minutes can be found here, https://www.w3.org/2025/01/29-a11yedge-minutes.html > > > > > > > > > > > > > > > > > > > > -- > > Lionel Wolberger > > CCOO UserWay, A Level Access Company > -- 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 Wednesday, 5 February 2025 13:01:54 UTC