Re: New Diagram, Minutes

We could leave out examples of 2 entirely – it is the entire document after all.

Revised:

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. Such adaptations are enumerated 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!


From: Jason Taylor <jason@usablenet.com>
Date: Wednesday, January 29, 2025 at 23:14
To: Lionel Wolberger <lionel.wolberger@levelaccess.com>
Cc: Accessibility at the Edge <public-a11yedge@w3.org>
Subject: Re: New Diagram, Minutes
Hi All

I would suggest 2. b is a little simplistic if this represents how the majority of overlays update the DOM and the CSS?

J




This e-mail and any accompanying attachments are intended only to be read or used by the named addressee(s). It is confidential and contains legally privileged information. If you have received this message in error, please notify the sender immediately and delete this message.

Sent from my iPhone


On Jan 29, 2025, at 3:57 PM, 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.

<image001.png>

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