Re: Final Note on Terminology: simplify around ???Post-Source??? vs. post course and ???Edge???

Mike Paciello writes:
> Thanks Janina! I believe this brings greater clarity to the document.
> 
Thanks, Mike! I had the same reaction as I was editing. I love the
several instances where we have the "source" and "post-source" pairing
in addressing content accessibility. Then, too, it makes use of "edge"
where aspirational services are discussed more meaningful because it's
more clearly something distinctive.

I want to report, though, on my conversation with Chat GPT last
Saturday.

I asked for a definition of "edge computing."

Chat GPT returned with a definition focussing on processing proximate to
content sources.

I then asked how that possibly benefits the user and was told all about
faster response and loading times.

I then asked how that possibly could help people who require
personalization like different fonts or other screen characteristics.

"Oh, very good point," said the AI. It continued to explain how user
devices would be the locus for that kind of processing.

Lastly, I asked whether Chat GPT might want to reconsider its definition
of edge computing as a result of our conversation and recieved a
definition that, this time, did include user triggered modifications.

I don't know whether that's now the canonical Chat GPT answer, but it
shows me that one can negotiate with the bots!


Best,
Janina

> -Mike
> 
> Mike Paciello
> Chief Accessibility Officer
> michael.paciello@audioeye.com
> +1.603.484.1938
> 
> [image: AudioEye Registered Trademark Logo]
> [image: Follow us on LinkedIn for more accessibility tips!]
> <https://www.linkedin.com/company/audioeye-inc/>
> 
> 
> On Tue, May 27, 2025 at 8:32???AM Janina Sajka <janina@rednote.net> wrote:
> 
> > 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/
> >
> >
> 
> -- 
> The information in this communication is intended for the use of the 
> individual or entity to which it is addressed, and may contain information 
> that is PRIVILEGED, CONFIDENTIAL and/or exempt from disclosure under law. 
> If you are not the intended recipient, you are hereby notified that any 
> dissemination, distribution or copying of this communication is strictly 
> prohibited.

-- 

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 17:54:15 UTC