- From: Janina Sajka <janina@rednote.net>
- Date: Sat, 23 Aug 2025 14:20:38 -0400
- To: Jason Taylor <jason@usablenet.com>
- Cc: Accessibility Edge <w3ca11yedge@gmail.com>, Accessibility at the Edge <public-a11yedge@w3.org>
Good point, Jason. Thanks! Your suggested language is now (mostly) the Trade-Offs text. I've moved some of what was previously in Trade-Offs up to the Source field. We are talking about Third Party in this section, after all! https://a11yedge.github.io/capabilities/a11yedit3rd Jason Taylor writes: > Hi Janina > > I would revisit 5.3 and trade offs . It???s long and starts with a false statement plus then talks about benefits than trade offs. This area should be very focused on the trade offs. > > My suggestion would be to just write the below or similar. > > 5.3. Tradeoffs > > > Relying on a third party for post-source remediation creates increased dependency, which means the internal team loses direct ownership and control over key accessibility fixes. This dependency also introduces the risk that fixes could override or conflict with other parts of the site???s code, so additional care must be taken to check both accessibility and the original site???s functionality prior to updates. In addition, sustainability becomes a challenge because post-source fixes are always reliant on the underlying source; when the source changes, due diligence is required to ensure that the post-source remediation remains effective and does not fail or create new accessibility barriers. > > ??? > End > > > Relying on a third party for post-source remediation creates increased dependency, which means the internal team loses direct ownership and control over key accessibility fixes. This dependency also introduces the risk that fixes could override or conflict with other parts of the site???s code, additional care must be taken to check both the Accessibilty and original sites functionality piror to updates.. In addition, stastainabilty becomes a challenge because post-source fixes are always reliant on the underlying source; when the source changes, due diligence is required to ensure that the post-source remediation remains effective and doesn???t fail or create new accessibility barriers. > > > > 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 Aug 23, 2025, at 3:09???PM, Janina Sajka <janina@rednote.net> wrote: > > ???Just pushed! Thanks--and keep them coming! > > Jason Taylor writes: > Hi Janina > > I had changed the second A.I reference also to automation in that paragraph. As A.I does not have a role in identifying checkpoints , it has a role in helping validate identified checkpoints. > > I want to avoid providing the negative voices a clear and simple target. We need to be as technically on point as possible. > > So the second sentence should read - changing A.I to automation and dropping the word remediation at the very end as we use at the start of the sentence. > > Updated: > > Human remediation of automatically identified checkpoints, together with the content creator's active participation to clarify meaning and intent constitutes an effective and efficient approach to accomplish accessibility. > > ??? > End > > Regards > > > > > > 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 > > -- > > 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/ > -- 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 Saturday, 23 August 2025 18:20:44 UTC