Re: Last sentence in 1.4 could be removed

Done ...

Jason Taylor writes:
> Hi
> 
> Just doing a quick read and the last sentence in 1.4 could be removed. I am not sure its is 100% correct - there could be some technology you can use in-source but not in post source. Plus I do not feel it adds anything.
> 
> Suggest we remove: "There is no post-source technology available only to post-source, and there is no in-source method post-source may not appropriate."
> 


While the polemicist in me loves that sentence, I agree it's a
nontechnical argument that can't be proved. So, I reluctantly agree that
it's unnecessary in this document and have removed it!

Best,
Janina

> regards
> ________________________________
> From: Janina Sajka <janina@a11y.nyc>
> Sent: Tuesday, September 16, 2025 12:45 PM
> To: Jason Taylor <jason@usablenet.com>
> Cc: Accessibility at the Edge <public-a11yedge@w3.org>
> Subject: Re: Section 1.3 needs edits
> 
> Dear Jason, All:
> 
> These proposed edits to Sec 1.3 offer some clear improvement, but I
> think we should discuss before adopting any or all.
> 
> Let's discuss on tomorrow's call.
> 
> For comparison, Sec. 1.3 is here:
> 
> https://a11yedge.github.io/capabilities/#overlays
> 
> Jason Taylor writes:
> > Suggested edit to help:
> >
> > 1.3 Post-Source & Overlays
> >
> >
> > The term ???overlays,??? while not an officially defined category, has been repeatedly called out and has generated significant negative feedback from assistive technology users???particularly because of added UI features such as pop-up control panels. Overlays do incorporate post-source remediation techniques but can also introduce these additional interface elements that have been widely criticized.
> >
> >
> > The problem of overstating what overlays can achieve has already been reflected in U.S. Government action such as Federal Trade Commission (FTC) issued a consent decree against a vendor for advertising claims involving an ???overlay.???  However The U.S. Attorney General referenced overlays could offer acceptable solutions, in a regulatory ruling tied to an earlier version of this publication. In both cases, the term was applied to post-source implementations that modify web content in real time, often through injected scripts and a visible on-screen button.
> >
> >
> > Ultimately, overlays represent only one subset of post-source approaches. It is essential that vendors using post-source remediation be transparent about both the scope and the limits of their technologies. Clear and forthright communication builds trust and ensures that claims align with what these methods can genuinely deliver.
> >
> >
> > ???-
> >
> > End
> >
> >
> > ???
> > 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 Sep 12, 2025, at 1:33???PM, Janina Sajka <janina@a11y.nyc> wrote:
> >
> > ???Just a quick response to confirm I have your email, Jason. Thanks!
> >
> > I'm off grid to relax a bit now. My brain and body both need it. I'll
> > look at this more closely this weekend.
> >
> > Jason Taylor writes:
> > Hi
> >
> > Reading 1.3 as it includes overlay in the title - it will get a lot of attention.
> >
> > It should outline and flow -
> >
> > A. Overlay is used to describe solutions that combine some post source capabilities but also additional UI interfaces such as pop-up control panels that are not post source remediations
> >
> > B. There has been actions around overlays vendors that overstate their capabilities . Examples
> >
> > C. Vendors  that leverage post source should be transparent in terms of what they do and what they achieve
> >
> > - area B and C is covered well but I do not feel - and it should be at the start, we have not framed part A very well.
> >
> > ???
> > 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
> >
> > On Sep 12, 2025, at 11:46???AM, Janina Sajka <janina@a11y.nyc> wrote:
> >
> > ???Dear All:
> >
> > As the Subject above says--per our conversation on this week's
> > teleconference, the first line of our Abstract is short and sweet!
> >
> > https://A11yEdge.github.io/capabilities/
> >
> > PS: If this email goes through, my email issues are resolved!
> >
> > Best,
> > Janina
> >
> >
> > --
> >
> > 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/
> >
> 
> --
> 
> 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 Friday, 26 September 2025 10:42:14 UTC