- From: Janina Sajka <janina@rednote.net>
- Date: Tue, 27 May 2025 08:32:20 -0400
- To: Jason Taylor <jason@usablenet.com>
- Cc: "Janina.sajka@gmail.com" <Janina.sajka@gmail.com>, Lionel Wolberger <lionel.wolberger@levelaccess.com>, Michael Paciello <michael.paciello@audioeye.com>, "jason.taylor" <jason.taylor@usablenet.com>, Accessibility at the Edge <public-a11yedge@w3.org>
Colleagues: As Jason has long suggested, I've now taken a pass to exchange 'edge' language for 'post-source' wherever it seemed meaningful. Specific changes include: * All 11 instances of "there's no particular benefit to performing * this mediation at the edge" now say "to performing this * mediation post-source." * Similarly modified our "not a redundant capability" language * instances. I further made a significant number of edits by hand exchanging 'post-source' where we previously had 'edge.' Hopefully, this now clarifies according to our definition in Sec 1.2. https://A11yEdge.github.io/capabilities/#edgedef Looking forward to talking with you all on our long-delayed call Wednesday! Janina Jason Taylor writes: > > Hi team, > > > As a final input, and as we are in the two-week period of edits, I want to strongly recommend we simplify and clarify our terminology???especially around the use of ???Edge??? in this document. > > > To be direct: what we???re describing as post-source remediation is not Edge technology. Nothing in the process occurs at the network edge. Post-source solutions???whether overlays, widgets, or browser plugins???run client-side and retrieve updates from a third-party server. That???s fundamentally different from true Edge mechanisms, which operate within the network layer itself to improve speed or enforce security policies like bot blocking. Nothing is ???done??? at the edge. > > > Using ???Edge??? invites unnecessary scrutiny and misinterpretation. It implies automation or infrastructure-level integration that simply doesn???t exist here. More importantly, it undercuts the important narrative we???ve built???that post-source requires deliberate and considered approaches, well-engineered systems, and skilled developers to deliver real accessibility outcomes. > > > To avoid opening ourselves up to technical challenges or appearing to overstate the capability, I recommend we remove all references to Edge and consistently use ???post-source??? instead. > > > Thanks???I hope you understand I have the success of the document in mind. > > > Regards, > > Jason > > > > 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/
Received on Tuesday, 27 May 2025 12:32:26 UTC