Re: Perfecting Capabilitie Rhetoric with ChatGPT

You're correct, Mike. The changes were mostly subtle and hard to spot.
I'd have to go to the github change log to find them all, but they
included things like:

1.)	 Added a dash in the first sentence of the Abstract for
"trade-offs."

2.)	Added a slash in Sec 1.2 where we had "and or" without the
expect "and/or" slash.

3. Added quotes to some of our labels, e.g. "Source" rectangle, etc; in
Sec 1.2 diagram explanations.

4. While doing this I determined a number change in the first sentence
of 1.2; so now "their sources" where it was "its source" previously.

5.)	Here's agood one ...

Was: Source Rectangle & Post-Source Clouds: Represent multiple
contributors accessed via URL or URI whose provenance may not be clear
to the user.

Is: The "Source" rectangle and the post-source services--drawn as
cloud-shaped nodes: These represent multiple contributors accessed via
URL or URI whose provenance may not be clear, visible, or even of
interest to
       the user.

Not an exhaustive list -- but like the above.

If you don't see a change, that's probably a good thing! We rejected a
few changes that would have altered our rhetorical argument. We weren't
going to do that. Instead, it made us more accurate and precise, imo.

PS: I discussed my Aside coding approach, and especially the need for
aria-labelledby with my APA Co-Chair, Matthew Atkinson, who promissed to
give me a better coding template over the weekend.

So, the dotting of the i and the crossing of the t continue!

Meanwhile, have a great Friday!

Best,
Janina


Mike Paciello writes:
> The changes are all subtle to me! I haven't noticed anything (insert
> frowning face). Please let me know what changes were made and why. I
> assumed something would address the release of the OpenAI Atlass browser;
> but I see nothing here to suggest that...Or am I that ignorant????
> 
> -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 Fri, Oct 24, 2025 at 11:43???AM Janina Sajka <janina@a11y.nyc> wrote:
> 
> > Colleagues:
> >
> > Lionel and I spent the last hour or so reviewing our rhetoric with the
> > AI. This has resulted in some subtel, and perhaps not so subtle changes
> > in the Abstract and through Sec 1.2 of the Intro.
> >
> > Reactions most welcome!
> >
> > We have also planned to continue this exercise early Sunday AM Eastern.
> >
> > https://a11yedge.github.io/capabilities/
> >
> > Now, I go to work on why the Aside in Sec 1.5 is bleeding out. Lionel
> > finds only that one bleeding, so there should be something fixable!
> >
> > 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/
> >
> >
> >
> 
> -- 
> 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 Friday, 24 October 2025 20:35:18 UTC