From ljmaher03 at outlook.com  Mon Feb  2 11:41:29 2026
From: ljmaher03 at outlook.com (Louis Maher)
Date: Mon, 2 Feb 2026 11:41:29 +0000
Subject: [NFBCS] The Science and Engineering Division and National
 Association of
 Blind Students Joint STEM Seminar
In-Reply-To: 
 <SJ0PR14MB523024E35BCC8706955A834EAA9AA@SJ0PR14MB5230.namprd14.prod.outlook.com>
References: 
 <SJ0PR14MB5230BE948C6FAED34E791B8DAA9AA@SJ0PR14MB5230.namprd14.prod.outlook.com>
 <SJ0PR14MB523024E35BCC8706955A834EAA9AA@SJ0PR14MB5230.namprd14.prod.outlook.com>
Message-ID: 
 <SJ0PR14MB5230EFC2A50B43EE3CC03811AA9AA@SJ0PR14MB5230.namprd14.prod.outlook.com>

The Science and Engineering Division and National Association of Blind Students Joint STEM Seminar

Two divisions of the National Federation of the Blind, namely: The Science and Engineering Division (SED) and the National Association of Blind Students (NABS), are presenting a joint Zoom conference on how blind college and graduate students, and blind professionals, are succeeding in courses and careers in science, technology, engineering, and mathematics. The Zoom conference link will be the standard NABS Zoom link shown at the bottom of this message. The call will occur at 7:30 PM EST through 9 PM EST on Sunday, February 22, 2026. We will have three speakers. Each talk will be twenty minutes long with an extra five minutes for questions.

Topics will be of interest for blind students from middle school through graduate school and for professionals. Parents of blind school-aged children and educators are also welcome.

Currently, the scheduled titles, speakers, abstracts, and speaker introductions, are:

Opening Remarks
Lauren Altman, president, National Association of Blind Students (nabs.president at gmail.com<mailto:nabs.president at gmail.com>), and John Miller, president, Science and Engineering Division (Johnmillerphd at hotmail.com<mailto:Johnmillerphd at hotmail.com>) (7:30 PM)

Title: Engineering the Future: Storing Clean Energy Deep Beneath Our Feet (7:40 PM)

Speaker: Matthew Ard (mattard at stanford.edu<mailto:mattard at stanford.edu>)

Abstract: The transition to clean energy is one of the greatest challenges of our time, but what opportunities actually exist to solve this crucial problem? In this talk, I will introduce the field of Energy Science and Engineering and discuss how I am working to tackle climate change through my research on large-scale energy storage. I will share my journey from undergraduate studies to a PhD program and discuss the methods and technologies I use to conduct high-level research as a student with a visual impairment. By sharing my research and personal experience, I hope to demystify the research process and show that a career in research is a tangible reality for students from all backgrounds.

Speaker Introduction: Matthew is a second-year PhD student at Stanford University in the Energy Science and Engineering program and a National Science Foundation Graduate Research Fellow. His research is focused on enabling a clean energy future through underground energy storage. He graduated from San Jose State University with a B.S. in Mechanical Engineering. As an undergraduate, he conducted research at Stanford University and Columbia University, where he focused on solving problems related to climate change. Beyond the lab, Matthew is dedicated to improving accessibility and advocating for inclusion in his communities. He works with the Office of Access, Belonging, and Community and mentors undergraduate and graduate students to help them navigate their own paths in higher education.

Questions: (8:00 PM)

Title: Birding by Ear and Beyond; Exploring, experiencing, and engaging in the wonder of the Natural world as a person who is blind (8:05 PM)

Speaker: Donna Posont (dposont at umich.edu<mailto:dposont at umich.edu>)

Abstract: Wonder of the natural world is for everyone and that includes those who are blind or low vision. Sometimes we learn in various ways by engaging all our other senses to experience natural science. This program at the University of Michigan-Dearborn Environmental Interpretive Center meets at least monthly to learn about nature and is taught as though all participants are blind, but, friends and family are welcome.

Speaker Introduction:
Donna Posont
Coordinator: Birding by Ear and Beyond
Environmental Interpretive Center
University of Michigan-Dearborn
dposont at umich.edu<mailto:dposont at umich.edu>

I have a bachelor's degree in social work from West Liberty University in West Virginia. I returned as a non-traditional student and received a degree in Environmental Studies with a naturalist focus and a minor in Biology graduating in 2015 from the University of Michigan-Dearborn. During my time as a student I started a monthly program for blind people to learn to identify birds by sound. Upon graduation I became a staff naturalist and the program grew to Birding by Ear and Beyond. The Beyond part provides for experiencing all aspects of the natural world such as frogs, tree, and plant identification, learning about the watershed, building, and maintaining a Butterfly Garden. I received training as a Certified Interpretive Guide from the National Association of Interpretation, and this is helpful in sharing about nature. The program has been featured in national magazines such as Audubon and Birds and Blooms as well as appearing on CBS and NBC nightly news and various podcasts such as Ray Brown's Talkin Birds, Any Bird, Any body, and Eyes Free Sports. In 2016 I receive the Outstanding Part time Interpreter the Year award from the National Association of Interpretation Region IV. In 2024 I was a Merit Award recipient from Michigan Association of Environmental Outdoor Educators. My proudest moment came when I received the Jacob Bolotin Award from the National Federation of the Blind in 2024 for an outstanding program which has enhanced the lives of people who happen to be blind.

Questions: (8:25 PM)

Title: Audiom: Evaluating if digital interactive alternate text provides the same information as visual spatial maps and diagrams (8:30 PM)

Speaker: Brandon Biggs (brandon.biggs at xrnavigation.io<mailto:brandon.biggs at xrnavigation.io>)

Abstract: Sighted people view over 300 digital maps a year, in contrast to blind people, who view less than one map a year on average. Only around 17.5% of blind
people have ever viewed a map of any kind as a blind person. This talk will present Audiom, an interactive alternate text game-like digital interface that
can allow the non-visual viewing and creation of different types of spatial information, such as maps and diagrams. Over 13 academic studies and co-designs
have been performed on over 150 blind and 40 sighted participants to create and evaluate Audiom. The presentation will then discuss how Audiom is being
compared with visual digital maps and diagrams. The objective of this work is to clearly define what it means for a non-visual text map to serve the equivalent
purpose to a visual map to meet the Web Content Accessibility Guidelines. The results of this work should inform digital accessibility legislation to facilitate
equal educational and employment opportunities for professions requiring the use of spatial information.

Links to Audiom:
Personal use:
https://audiom.net
Commercial use:
https://xrnavigation.io

Speaker Introduction: Brandon Biggs is an entrepreneur, researcher, inclusive designer, developer, and life-long learner. He is the CEO of XR Navigation, an Engineer at the
Smith-Kettlewell Eye Research Institute, Co-Founder and board treasurer at Sonja Biggs Educational Services Inc., and a PhD student at the Georgia institute
of Technology. In 2016, he received his bachelor's in music from California State University East Bay, in 2019 he received his master's in Inclusive Design
from the Ontario College of Art and Design University, and in 2021, began his PhD in Human Centered Computing from the Georgia Institute of Technology.
He is almost completely blind from Leber's Congenital Amaurosis (LCA). His projects and ventures center around building tools to solve some of the most
difficult problems in the blindness field. He leverages his lived experience coupled with human centered inclusive design principles to create solutions
that create lasting and sustainable impact. To achieve this goal, Brandon is half entrepreneur and half academic.

Questions: (8:50 PM)

Closing Remarks
Lauren Altman and John Miller (8:55 PM)

Adjourn: (9:05 PM)

Division Contact Information

If you wish to learn more about NABS, including how to become a member, go to:
"https://www.nabslink.org/".

If you wish to join the SED, go to:
"http://www.nfb.org/divisiondues".

Dues for NABS and SED are $5 per division per year.

NFB divisions' fiscal years start on January 1 and end on December 31 of the same year.

Individuals may join the NABS and SED e-mail discussion groups at "https://www.nfbnet.org/".

If you have any questions about the mechanics of the seminar, please contact Louis Maher (713-444-7838, ljmaher03 at outlook.com<mailto:ljmaher03 at outlook.com>).
-----
Join Zoom Meeting:
February 22, 2026, 7:30 PM EST

Zoom Meeting Room <https://zoom.us/j/4678833687?_x_zm_rtaid=KOKAICd1R4ihtmx1LS5OTg.1769021469326.3ccbb5b08dc1b4996eb5278c87f34feb&_x_zm_rhtaid=216%23success>

Meeting ID: 467 883 3687

One tap mobile
+13017158592,4678833687 US (Germantown)

13126266799,,4678833687# US (Chicago)






Regards
Louis Maher
Phone: 713-444-7838
Email: ljmaher03 at outlook.com<mailto:ljmaher03 at outlook.com>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://nfbnet.org/pipermail/nfbcs_nfbnet.org/attachments/20260202/79ae8d20/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Announcement For A Zoom Conference On How The Blind Can Do STEM 2026-02-22 (1).docx
Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document
Size: 30778 bytes
Desc: Announcement For A Zoom Conference On How The Blind Can Do STEM 2026-02-22 (1).docx
URL: <http://nfbnet.org/pipermail/nfbcs_nfbnet.org/attachments/20260202/79ae8d20/attachment.docx>

From nadia.brancati at icar.cnr.it  Tue Feb 10 10:07:58 2026
From: nadia.brancati at icar.cnr.it (Nadia Brancati)
Date: Tue, 10 Feb 2026 11:07:58 +0100
Subject: [NFBCS] [CFP] IEEE ICTS4eHealth 2026 @ IEEE ISCC, Algarve, Portugal
Message-ID: 
 <CANxf_fXMEG87Zj5RNeKtzu1wpm6MRKRFdr0=CMv7LubwtmD0dg@mail.gmail.com>

[Apologies if you receive multiple copies of this CFP]

Dear colleagues,

We are delighted to invite you to submit your contributions to the 6th
edition of the IEEE ICTS4eHealth Conference, co-located with the 31st IEEE
Symposium on Computers and Communications (ISCC), which will take place on
June 23–26, 2026, in Algarve, Portugal.


Yours sincerely,

IEEE ICTS4eHealth Organization

=======================================================

6th Edition of IEEE International Conference on ICT Solutions for e-Health

ICTS4eHealth 2026

Algarve, Portugal - June 23-26, 2026

https://icts4ehealth.icar.cnr.it

In conjunction with the 31st IEEE Symposium on Computers and Communications

All paper submissions must be done through EDAS.

=======================================================

MISSION:

-----------------------------------------------------------------------------------------------

E-Health is one of the major research topics that have been attracting
cross-disciplinary research groups.

The deployment of new emerging ICT technologies for Health, especially
based on Cloud computing, Internet of Things (IoT), and Artificial
Intelligence (AI), is attracting the interest of many researchers.
Following the success of five workshop editions and two years as an
International IEEE Conference, we are now proud to announce the third
edition of this popular event dedicated to ICT solutions for e-Health. The
conference will bring together researchers from academia, industry,
government, and medical centers in order to present the state of the art in
the emerging area of the use of cloud systems in connected health
infrastructure and applications, and the use of IoT and AI techniques in
the area of e-Health.

TOPICS:

-----------------------------------------------------------------------------------------------

Conference topics include (but are not limited to):

- Artificial Intelligence & Data Analytics for eHealth

Artificial Intelligence for eHealth

Generative AI for Longitudinal Data

AI for Precision Medicine

Knowledge Discovery and Decision Support

Biomedical Data Processing

Data/Visual Mining for Diagnostics

Computer-Aided Diagnostics

Intelligent Bio-signal Interpretation

- Sensing, Wearables & Internet of Medical Things (IoMT)

Internet of Things (IoT) applications for eHealth

Biosensors and Sensor Networks

Wearable Devices and Smart Sensors

Monitoring of Vital Functions

Sensor-based mHealth applications

- Signal, Image & Multimodal Processing

Advanced Bio-signal Processing

Signal Processing for Health

Image Analysis for Health

Medical Imaging Analysis

Generative Models for Medical Imaging

Image-to-Image Translation

Computer Vision and Pattern Recognition

Advanced Medical Visualization

Multimodal Data Fusion

- Digital Health Systems & Architectures

Cloud Computing for eHealth

Distributed and Edge Computing for Healthcare

Telehealth, Telemonitoring and Telediagnostics

e-Healthcare, m-Healthcare, x-Health

Extended and Digital Health Ecosystems

AI-enabled Digital Twins for Healthcare

- Assistive Technologies & Human-Centered Design

Assistive Technology and Assisted Living

Personalized Assistive Technologies

User-Centered Design and Usability

e-Accessibility and Web Accessibility

Assistive Technologies for Urban and Smart Environments

- Security, Privacy & Trustworthy eHealth

Security and Privacy in eHealth

Ethical, Legal and Social Implications (ELSI)

Trustworthy AI for Healthcare

Explainable/Interpretable AI for Health

Federated/Privacy-Preserving Learning

- Modeling, Simulation & Clinical Applications

Healthcare Modeling and Simulation

Computational Biology and Bioinformatics

Modeling and Simulation in BM

Improved Therapeutic and Rehabilitation Methods


IMPORTANT DATES:

-----------------------------------------------------------------------------------------------

- Submission deadline: MARCH 15, 2026

- Notification of paper acceptance: MARCH 31, 2026

- Conference Dates: June 23-26, 2026

PAPER SUBMISSION:

-----------------------------------------------------------------------------------------------

Manuscripts should describe original work and should be no more than 7
pages in the IEEE double-column proceedings format, including tables,
figures and references. Download manuscript templates for IEEE conference
proceedings from: https://www.ieee.org/conferences/publishing/templates.html

Note that accepted papers up to 6 pages will be published with no
additional charge. Exceeding pages will be charged an additional fee.
Papers exceeding 7 pages will not be accepted.

At least one author of each accepted paper is required to register to the
conference and present the paper. Only registered and presented papers will
be published in the conference proceedings.

In IEEE ICTS4eHealth 2026, as well as in IEEE ISCC 2026, all submissions
must be done through EDAS.

Accepted papers will be included in the proceedings of ISCC 2026, of which
ICTS4eHealth conference is a co-located event, and will be submitted for
inclusion to IEEE Xplore. The ICTSeHealth and ISCC proceedings have been
indexed in the past by ISI, DBLP and Scopus. This makes the ISCC conference
one of the publication venues with very high visibility and impact in both
Computer and Communications areas.


BEST PAPER AWARD:

-----------------------------------------------------------------------------------------------

A "Best Paper Award" Certificate will be conferred on the author(s) of a
paper presented at the conference, selected by the Chairs based on
scientific significance, originality and outstanding technical quality of
the paper, as assessed also by the evaluations of the members of the
Program Committee.


SPECIAL ISSUES:

-----------------------------------------------------------------------------------------------

Authors of selected papers may be invited to submit extended versions of
their papers for publication as full journal papers in special issues
organized in prestigious indexed journals.


STEERING COMMITTEE:

-----------------------------------------------------------------------------------------------

- Antonio Celesti, University of Messina, Italy;

- Ivanoe De Falco, ICAR-CNR, Italy;

- Giovanna Sannino, ICAR-CNR, Italy;

- Massimo Villari, University of Messina, Italy.


ORGANIZATION:

-----------------------------------------------------------------------------------------------

General chair:

- Daniele Raví, University of Messina, Italy

Technical Program Co-Chairs:

- Brancati Nadia, ICAR-CNR, Italy

- Francesco La Rosa, University of Messina, Italy

- Laura Verde, University of Campania "L. Vanvitelli”, Italy

- Saber Sami, University of East Anglia, UK

Publicity Co-Chairs:

- Salvatore Giugliano, ICAR-CNR, Italy

- Gabriele Morabito, University of Messina, Italy


Please visit https://icts4ehealth.icar.cnr.it for more information, and, if
you have any questions, kindly get back to us by sending an email to
ICTS4eHealth at icar.cnr.it

Kind regards,

IEEE ICTS4eHealth Organization

####################################################################


-- 
Nadia Brancati
Senior Researcher @ AI-ISA Lab
<https://www.icar.cnr.it/en/gruppi-di-ricerca/artificial-intelligence-in-image-and-signal-analysis/>
Institute for High Performance Computing and Networking - National Research
Council of Italy (CNR - ICAR)
Via P. Castellino, 111 - 80131 Napoli
Tel. 081.6139228
nadia.brancati at icar.cnr.it
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://nfbnet.org/pipermail/nfbcs_nfbnet.org/attachments/20260210/5cc0624e/attachment.htm>

From buhrow at nfbcal.org  Wed Feb 11 07:21:31 2026
From: buhrow at nfbcal.org (Brian Buhrow)
Date: Tue, 10 Feb 2026 23:21:31 -0800
Subject: [NFBCS] Pathlight Student Team Seeking Feedback
Message-ID: <202602110721.61B7LVmh001462@nfbcal.org>

	Hello everyone!  Charles from the NFB National Office connected me with the folks who sent
the below message.  If you are interested in trying out this technology and providing feedback,
they're accepting applicants through February 15 of this year and, if you're chosen as a
participant, you'll receive a little compensation for your time.  If you do elect to
apply and are chosen to participate, please give us some feedback on what it is they're doing
and what you tink of it all.  

-thanks
-Brian


From: Pathlight <pathlightproj at gmail.com>
Date: Sun, 8 Feb 2026 16:24:09 -0600
Subject: Re: Pathlight Student Team Seeking Feedback
To: buhrow at nfbcal.org
Cc: Charles Hiser <chiser at nfb.org>

Hi Brian,

Thank you so much, Charles, for the wonderful introduction! We're
incredibly grateful for your support and for connecting us with the NFBCS
community.

Lauren, we'd be thrilled to meet with you and the NFBCS Board to share more
about PATH and gather your feedback. Your expertise would be invaluable as
we continue developing this technology, and we're eager to learn from the
community. Please pick a time that works best for us both here:
https://cal.com/team/pathlight/pathlight-intro

Also, we're launching our pilot on February 20th, and the signup deadline
is February 15th. We'll be compensating all participants for their time.
Here's the interest form that you can circulate to anyone who might be
interested: https://forms.gle/Q8fPtHAPt6ybGMt27

We're really looking forward to connecting with you and the NFBCS members.
Please feel free to reach out anytime=E2=80=94we're here to listen and lear=
n.

Thanks again for your support!

Best,
Ariyan



On Fri, Feb 06, 2026 at 1:43 PM, Charles Hiser <chiser at nfb.org> wrote:

> Hello Brian and NFBCS board,
>
>
>
> I recently met with a member of the Pathlight team, a group of university
> students building an AI agent called Path that operates primarily through
> an audio interface. They are asking for blind and low vision iPhone users
> who have Gmail accounts to provide early feedback on their concept. I wou=
ld
> consider it a favor if you would extend this opportunity to NFBCS members
> who could offer their honest opinions and suggestions for improvement
> and/or collaboration to add blind people=E2=80=99s lived experiences and
> professional expertise to the project. Pathlight has been CCed on this
> email so feel free to connect at your leisure. I have also included a bio
> written by the Pathlight team below:
>
>
>
> Pathlight is a team of Yale and Stanford students building PATH, a Pretty
> Amazing Talking Helper. PATH is able to integrate into the phone apps and
> softwares you use on a daily basis and allow you to carry out actions in
> those apps entirely by voice and totally handsfree. We're getting rid of
> the frustration of Siri and enabling you to do many complex tasks all at
> once and at the call of your voice. We're launching a pilot to test the
> product of Feb. 20, and the deadline to sign up is February 15th. Please
> feel free to spread the word to anyone who might be interested. We'll be
> compensating participants for their time. Here is the interest google for=
m:
> https://forms.gle/Q8fPtHAPt6ybGMt27
>
>
>
> Also if you'd like to schedule a time to ask us more questions or provide
> comments, you can do so here: https://cal.com/team/pathlight/
> pathlight-intro
>
>
>
> As always, I am available for contact at any time. Please don=E2=80=99t h=
esitate
> to reach out with questions or comments.
>
>
>
>
>
> Thanks,
>
> Charles Hiser CPACC
>
> JAWS Certified, NVDA Certified Expert
> Accessibility Excellence Advocate, Education and Employment
> 200 East Wells Street, Baltimore, MD 21230
>
> 410-659-9314, extension 2239| chiser at nfb.org
>
>
>
>

From chong.curtis at gmail.com  Fri Feb 13 16:01:15 2026
From: chong.curtis at gmail.com (Curtis Chong)
Date: Fri, 13 Feb 2026 09:01:15 -0700
Subject: [NFBCS] Comcast Email Users Beware!!!!!
Message-ID: <009501dc9d01$fcaf5770$f60e0650$@gmail.com>

Greetings everyone:

 

If your email address is not something at comcast.net
<mailto:something at comcast.net> , feel free to disregard this email. However,
if your email is being handled by Comcast and (more importantly) you use
Microsoft Outlook to send and receive your Comcast email, then please pay
heed to this email.

 

 


Background


 

Starting in June, 2025, customers with a Comcast email address were being
"invited" to "upgrade their email account to Yahoo Mail for a better email
experience at no extra cost." (Parenthetically speaking, what this
represents is a not-so-well-hidden attempt by Comcast to reduce the number
of customers for whom it needs to handle email)

 

According to the Xfinity page
https://www.xfinity.com/support/articles/yahoo-email-migration-overview,

 

"Your comcast.net email address stays the same - and so do your messages,
folders, and contacts."

 

According to information from
https://www.xfinity.com/support/articles/yahoo-email-migration-overview,

 

"this is an upgrade we are offering customers at no cost so they can access
their email on a better platform with enhanced security, more features, and
a mobile app for easy access on the go."

 

 


The Problem


 

I have been working with individuals whose Comcast emails were (with their
permission) transferred to Yahoo. While their emails are reasonably
accessible using Yahoo's webmail interface, and while comcast.net emails
handled by Yahoo are retrievable using the native iPhone Mail program, it
has been virtually impossible to connect Microsoft Outlook to comcast.net
emails that are processed by Yahoo email servers. I am working with the
folks at Microsoft and Yahoo in an attempt to resolve this issue, but so
far, I have not had any luck solving this problem.

 

 


The Bottom Line


 

If you rely on Outlook to send and receive comcast.net emails, do not accept
Comcast's "invitation" to have your emails transferred (they say "upgraded")
to Yahoo!

 

Yours sincerely,

 

Curtis Chong

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://nfbnet.org/pipermail/nfbcs_nfbnet.org/attachments/20260213/05fcaa6f/attachment.htm>

From wbsjr at swbell.net  Fri Feb 13 16:44:57 2026
From: wbsjr at swbell.net (Bradford Snyder)
Date: Fri, 13 Feb 2026 10:44:57 -0600
Subject: [NFBCS] Comcast Email Users Beware!!!!!
In-Reply-To: <009501dc9d01$fcaf5770$f60e0650$@gmail.com>
References: <009501dc9d01$fcaf5770$f60e0650$@gmail.com>
Message-ID: <37203626-007A-4324-918A-4BAECED17EB5@swbell.net>

Setting up Comcast email with Yahoo on Microsoft's Outlook, requires either doing so with Open Authentication (OAuth), or creation of a Secure Mail Key.


To add your Comcast.net email account to Outlook, use the steps below:



Option 1: Set up your account without IMAP (OAuth)

Open Outlook.
Click Add Account.
Enter your full Comcast.net email address in the field provided (make sure to include the @comcast.net part) and then click Continue.
Enter your Comcast.net password in the field provided and then click Select provider.
Choose Yahoo from the list of mail providers.
Click Continue.
Enter your Comcast.net email account password again and then click Next.
Click Agree to allow Outlook to access your Comcast.net email account and to add functions like your Yahoo contacts and calendar.
- You'll see a success message when your emails are synced to Outlook.
Click Done.


Option 2: Set up your account using IMAP

(requires creation of a Secure Mail Key). 

Open Outlook.
Click Add Account.
Enter your full Comcast.net email address in the field provided (make sure to include the @comcast.net part) and then click Continue.
Leave the password field empty for now and instead slide the "Show more" toggle button to the right.
A list of settings will open. Use these IMAP and SMTP settings:
IMAP incoming server: imap.mail.yahoo.com
Port: 993
Secure connection type: SSL/TLS
SMTP username: Your full @comcast.net email address
SMTP outgoing server: smtp.mail.yahoo.com
Port: 587
Secure connection type: SSL/TLS


Next, you'll need to generate an app password:

Sign in to your Yahoo Account Security <https://login.yahoo.com/account/security?.lang=en-US&.intl=us&.src=yhelp> page.
Under "External connections," click the App passwords tab.
Click Create app password (find this on the right side of the screen, next to the External connections box).
Enter your app's name in the text field.
Click Generate password.
Copy the app password.
Return to Outlook and complete your IMAP setup:

Paste or enter the app password you just created into the password field.
Click Continue.
Click Continue again to sync your IMAP account to Outlook.
- You'll see a success message when your emails are synced to Outlook.
Click Done.
HTH.

- Brad -



On Feb 13, 2026, at 10:01, Curtis Chong via NFBCS <nfbcs at nfbnet.org> wrote:

Greetings everyone:
 
If your email address is not something at comcast.net <mailto:something at comcast.net>, feel free to disregard this email. However, if your email is being handled by Comcast and (more importantly) you use Microsoft Outlook to send and receive your Comcast email, then please pay heed to this email.
 
 
Background
 
Starting in June, 2025, customers with a Comcast email address were being “invited” to “upgrade their email account to Yahoo Mail for a better email experience at no extra cost.” (Parenthetically speaking, what this represents is a not-so-well-hidden attempt by Comcast to reduce the number of customers for whom it needs to handle email)
 
According to the Xfinity page https://www.xfinity.com/support/articles/yahoo-email-migration-overview,
 
“Your comcast.net <http://comcast.net/> email address stays the same — and so do your messages, folders, and contacts.”
 
According to information from https://www.xfinity.com/support/articles/yahoo-email-migration-overview,
 
“this is an upgrade we are offering customers at no cost so they can access their email on a better platform with enhanced security, more features, and a mobile app for easy access on the go.”
 
 
The Problem
 
I have been working with individuals whose Comcast emails were (with their permission) transferred to Yahoo. While their emails are reasonably accessible using Yahoo’s webmail interface, and while comcast.net <http://comcast.net/> emails handled by Yahoo are retrievable using the native iPhone Mail program, it has been virtually impossible to connect Microsoft Outlook to comcast.net <http://comcast.net/> emails that are processed by Yahoo email servers. I am working with the folks at Microsoft and Yahoo in an attempt to resolve this issue, but so far, I have not had any luck solving this problem.
 
 
The Bottom Line
 
If you rely on Outlook to send and receive comcast.net <http://comcast.net/> emails, do not accept Comcast’s “invitation” to have your emails transferred (they say “upgraded”) to Yahoo!
 
Yours sincerely,
 
Curtis Chong
 
 
_______________________________________________
NFBCS mailing list
NFBCS at nfbnet.org <mailto:NFBCS at nfbnet.org>
http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org
To unsubscribe, change your list options or get your account info for NFBCS:
http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/wbsjr%40swbell.net

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://nfbnet.org/pipermail/nfbcs_nfbnet.org/attachments/20260213/bf32f163/attachment.htm>

From rysteve at comcast.net  Fri Feb 13 17:04:01 2026
From: rysteve at comcast.net (Ryan Stevens)
Date: Fri, 13 Feb 2026 12:04:01 -0500
Subject: [NFBCS] Postman alternative
Message-ID: <006501dc9d0a$c14dfde0$43e9f9a0$@comcast.net>

Hello,

 

The phone system my company uses for our call centers has changed the way we
can pull back-end data for custom reports. They are using Data Lakehouse to
create Parquet files. However, their interface is difficult to work with, so
they suggested using Postman for the data pull. Postman's accessibility
turns out to be worse. Does anyone use a similar app that actually works?
Any advice would be appreciated.

 

Thanks,

Ryan Stevens

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://nfbnet.org/pipermail/nfbcs_nfbnet.org/attachments/20260213/f0bdc5cb/attachment.htm>

From chong.curtis at gmail.com  Fri Feb 13 17:11:26 2026
From: chong.curtis at gmail.com (Curtis Chong)
Date: Fri, 13 Feb 2026 10:11:26 -0700
Subject: [NFBCS] Comcast Email Users Beware!!!!!
In-Reply-To: <37203626-007A-4324-918A-4BAECED17EB5@swbell.net>
References: <009501dc9d01$fcaf5770$f60e0650$@gmail.com>
 <37203626-007A-4324-918A-4BAECED17EB5@swbell.net>
Message-ID: <002f01dc9d0b$ca7b46b0$5f71d410$@gmail.com>

 

 

Hello Brad:

 

I tried your first procedure without success. The Provider option was not provided in my version of Outlook, which is the latest available under my Microsoft 365 license.

 

As for your second procedure, every time I entered the yahoo.com server names, Outlook kept changing them to something at comcast.net, using the comcast.net part of the user name.

 

Your procedures are, in fact, the ones that you can read online in public posts from Comcast, but to be blunt, they are not working as advertised.

 

Kind wishes,

 

Curtis Chong

 

 

From: NFBCS <nfbcs-bounces at nfbnet.org> On Behalf Of Bradford Snyder via NFBCS
Sent: Friday, February 13, 2026 9:45 AM
To: NFB in Computer Science Mailing List <nfbcs at nfbnet.org>
Cc: Bradford Snyder <wbsjr at swbell.net>
Subject: Re: [NFBCS] Comcast Email Users Beware!!!!!
Importance: High

 

Setting up Comcast email with Yahoo on Microsoft's Outlook, requires either doing so with Open Authentication (OAuth), or creation of a Secure Mail Key.

 

 

To add your Comcast.net email account to Outlook, use the steps below:

 

Option 1: Set up your account without IMAP (OAuth)

1.	Open Outlook.
2.	Click Add Account.
3.	Enter your full Comcast.net email address in the field provided (make sure to include the @comcast.net part) and then click Continue.
4.	Enter your Comcast.net password in the field provided and then click Select provider.
5.	Choose Yahoo from the list of mail providers.
6.	Click Continue.
7.	Enter your Comcast.net email account password again and then click Next.
8.	Click Agree to allow Outlook to access your Comcast.net email account and to add functions like your Yahoo contacts and calendar.
- You'll see a success message when your emails are synced to Outlook.
9.	Click Done.

 

Option 2: Set up your account using IMAP

(requires creation of a Secure Mail Key). 

1.	Open Outlook.
2.	Click Add Account.
3.	Enter your full Comcast.net email address in the field provided (make sure to include the @comcast.net part) and then click Continue.
4.	Leave the password field empty for now and instead slide the "Show more" toggle button to the right.
5.	A list of settings will open. Use these IMAP and SMTP settings:
IMAP incoming server: imap.mail.yahoo.com
Port: 993
Secure connection type: SSL/TLS
6.	SMTP username: Your full @comcast.net email address
SMTP outgoing server: smtp.mail.yahoo.com
Port: 587
Secure connection type: SSL/TLS

 

Next, you'll need to generate an app password:

1.	Sign in to your  <https://login.yahoo.com/account/security?.lang=en-US&.intl=us&.src=yhelp> Yahoo Account Security page.
2.	Under "External connections," click the App passwords tab.
3.	Click Create app password (find this on the right side of the screen, next to the External connections box).
4.	Enter your app's name in the text field.
5.	Click Generate password.
6.	Copy the app password.

Return to Outlook and complete your IMAP setup:

1.	Paste or enter the app password you just created into the password field.
2.	Click Continue.
3.	Click Continue again to sync your IMAP account to Outlook.
- You'll see a success message when your emails are synced to Outlook.
4.	Click Done.

HTH.


- Brad -



 

On Feb 13, 2026, at 10:01, Curtis Chong via NFBCS <nfbcs at nfbnet.org <mailto:nfbcs at nfbnet.org> > wrote:

 

Greetings everyone:

 

If your email address is not  <mailto:something at comcast.net> something at comcast.net, feel free to disregard this email. However, if your email is being handled by Comcast and (more importantly) you use Microsoft Outlook to send and receive your Comcast email, then please pay heed to this email.

 

 


Background


 

Starting in June, 2025, customers with a Comcast email address were being “invited” to “upgrade their email account to Yahoo Mail for a better email experience at no extra cost.” (Parenthetically speaking, what this represents is a not-so-well-hidden attempt by Comcast to reduce the number of customers for whom it needs to handle email)

 

According to the Xfinity page  <https://www.xfinity.com/support/articles/yahoo-email-migration-overview> https://www.xfinity.com/support/articles/yahoo-email-migration-overview,

 

“Your  <http://comcast.net/> comcast.net email address stays the same — and so do your messages, folders, and contacts.”

 

According to information from  <https://www.xfinity.com/support/articles/yahoo-email-migration-overview> https://www.xfinity.com/support/articles/yahoo-email-migration-overview,

 

“this is an upgrade we are offering customers at no cost so they can access their email on a better platform with enhanced security, more features, and a mobile app for easy access on the go.”

 

 


The Problem


 

I have been working with individuals whose Comcast emails were (with their permission) transferred to Yahoo. While their emails are reasonably accessible using Yahoo’s webmail interface, and while  <http://comcast.net/> comcast.net emails handled by Yahoo are retrievable using the native iPhone Mail program, it has been virtually impossible to connect Microsoft Outlook to  <http://comcast.net/> comcast.net emails that are processed by Yahoo email servers. I am working with the folks at Microsoft and Yahoo in an attempt to resolve this issue, but so far, I have not had any luck solving this problem.

 

 


The Bottom Line


 

If you rely on Outlook to send and receive  <http://comcast.net/> comcast.net emails, do not accept Comcast’s “invitation” to have your emails transferred (they say “upgraded”) to Yahoo!

 

Yours sincerely,

 

Curtis Chong

 

 

_______________________________________________
NFBCS mailing list
 <mailto:NFBCS at nfbnet.org> NFBCS at nfbnet.org
 <http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org> http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org
To unsubscribe, change your list options or get your account info for NFBCS:
 <http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/wbsjr%40swbell.net> http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/wbsjr%40swbell.net

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://nfbnet.org/pipermail/nfbcs_nfbnet.org/attachments/20260213/ba94f9f5/attachment.htm>

From cannona at fireantproductions.com  Tue Feb 17 19:14:05 2026
From: cannona at fireantproductions.com (Aaron Cannon)
Date: Tue, 17 Feb 2026 13:14:05 -0600
Subject: [NFBCS] Postman alternative
In-Reply-To: <006501dc9d0a$c14dfde0$43e9f9a0$@comcast.net>
References: <006501dc9d0a$c14dfde0$43e9f9a0$@comcast.net>
Message-ID: 
 <CAERFoOhyOTHseUiwYrLGrRq0zdZcccM0dOrWHfxZuJq9i__C9w@mail.gmail.com>

No direct fixes for you, but I do believe that almost anything that can be
done with Postman can also be done with curl at the commandline.

Good luck.

Aaron Cannon
On Fri, Feb 13, 2026 at 11:07 Ryan Stevens via NFBCS <nfbcs at nfbnet.org>
wrote:

> Hello,
>
>
>
> The phone system my company uses for our call centers has changed the way
> we can pull back-end data for custom reports. They are using Data Lakehouse
> to create Parquet files. However, their interface is difficult to work
> with, so they suggested using Postman for the data pull. Postman’s
> accessibility turns out to be worse. Does anyone use a similar app that
> actually works? Any advice would be appreciated.
>
>
>
> Thanks,
>
> Ryan Stevens
>
>
> _______________________________________________
> NFBCS mailing list
> NFBCS at nfbnet.org
> http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org
> To unsubscribe, change your list options or get your account info for
> NFBCS:
>
> http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/cannona%40fireantproductions.com
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://nfbnet.org/pipermail/nfbcs_nfbnet.org/attachments/20260217/e52e08f1/attachment.htm>

From rysteve at comcast.net  Tue Feb 17 19:21:28 2026
From: rysteve at comcast.net (Ryan Stevens)
Date: Tue, 17 Feb 2026 14:21:28 -0500
Subject: [NFBCS] Postman alternative
In-Reply-To: 
 <CAERFoOhyOTHseUiwYrLGrRq0zdZcccM0dOrWHfxZuJq9i__C9w@mail.gmail.com>
References: <006501dc9d0a$c14dfde0$43e9f9a0$@comcast.net>
 <CAERFoOhyOTHseUiwYrLGrRq0zdZcccM0dOrWHfxZuJq9i__C9w@mail.gmail.com>
Message-ID: <02a401dca042$9e8f2820$dbad7860$@comcast.net>

Okay, I’ll try it. Thanks.

 

From: Aaron Cannon <cannona at fireantproductions.com> 
Sent: Tuesday, February 17, 2026 2:14 PM
To: NFB in Computer Science Mailing List <nfbcs at nfbnet.org>
Cc: Ryan Stevens <rysteve at comcast.net>
Subject: Re: [NFBCS] Postman alternative

 

No direct fixes for you, but I do believe that almost anything that can be done with Postman can also be done with curl at the commandline.

 

Good luck.

 

Aaron Cannon

On Fri, Feb 13, 2026 at 11:07 Ryan Stevens via NFBCS <nfbcs at nfbnet.org <mailto:nfbcs at nfbnet.org> > wrote:

Hello,

 

The phone system my company uses for our call centers has changed the way we can pull back-end data for custom reports. They are using Data Lakehouse to create Parquet files. However, their interface is difficult to work with, so they suggested using Postman for the data pull. Postman’s accessibility turns out to be worse. Does anyone use a similar app that actually works? Any advice would be appreciated.

 

Thanks,

Ryan Stevens

 

_______________________________________________
NFBCS mailing list
NFBCS at nfbnet.org <mailto:NFBCS at nfbnet.org> 
http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org
To unsubscribe, change your list options or get your account info for NFBCS:
http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/cannona%40fireantproductions.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://nfbnet.org/pipermail/nfbcs_nfbnet.org/attachments/20260217/04310860/attachment.htm>

From gene.sh.kim at gmail.com  Tue Feb 17 20:29:34 2026
From: gene.sh.kim at gmail.com (Gene Kim)
Date: Tue, 17 Feb 2026 15:29:34 -0500
Subject: [NFBCS] Postman alternative
In-Reply-To: <02a401dca042$9e8f2820$dbad7860$@comcast.net>
References: <02a401dca042$9e8f2820$dbad7860$@comcast.net>
Message-ID: <8805BE44-B84B-49C2-A9B8-56FB7BC433F9@gmail.com>

An HTML attachment was scrubbed...
URL: <http://nfbnet.org/pipermail/nfbcs_nfbnet.org/attachments/20260217/56177d53/attachment.htm>

From bhavya.shah125 at gmail.com  Wed Feb 18 02:00:04 2026
From: bhavya.shah125 at gmail.com (Bhavya shah)
Date: Tue, 17 Feb 2026 18:00:04 -0800
Subject: [NFBCS] Roommate for CSUN
Message-ID: 
 <CACHadJ2rBAcEPT8cNw+hiRiOCQBhVN=Et7M2tFaUmBNXz=EnPw@mail.gmail.com>

I’m hoping to attend the CSUN conference in March. If you - or someone you
know - is going and looking for a male roommate to split costs with, please
write to me at bhavya.shah125 at gmail.com. If we haven't met before, I’m a
blind graduate student in Computer Science at Stanford, a former NFB
scholarship finalist, and an easygoing roommate.



Warmly,

Bhavya Shah | M.S. AI & B.S. Math/CS, Stanford University

LinkedIn <https://www.linkedin.com/in/bhavyashah125/> | Instagram
<https://www.instagram.com/mynameisnotjavier> | Website
<https://bhavyashahcomedy.com/>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://nfbnet.org/pipermail/nfbcs_nfbnet.org/attachments/20260217/4d984a0d/attachment.htm>

From lewislwood at gmail.com  Wed Feb 18 03:45:37 2026
From: lewislwood at gmail.com (Lewis Wood)
Date: Tue, 17 Feb 2026 21:45:37 -0600
Subject: [NFBCS] Postman alternative
In-Reply-To: <02a401dca042$9e8f2820$dbad7860$@comcast.net>
References: <006501dc9d0a$c14dfde0$43e9f9a0$@comcast.net>
 <CAERFoOhyOTHseUiwYrLGrRq0zdZcccM0dOrWHfxZuJq9i__C9w@mail.gmail.com>
 <02a401dca042$9e8f2820$dbad7860$@comcast.net>
Message-ID: <004d01dca089$0c53e260$24fba720$@gmail.com>

I use ThunderClient and their vscode extension.  Their CLI is what I use most.

 

It is supposed to be compatible with Postman scripts.

 

Once you configure to save to workspace for thunder in the current project it will save it to a thunderclient folder.

 

All your runs/scripts are there. You can specify iterations, variables, environments, output from one api call to another. Etc…

 

It only costs $32/year.

 

I learned how to do it in the extension which was a pain. Then I use the cli from there. I even edit the files and add the variables/etc..

 

Scripts are easy to read. 

 

You can get my instructions I created for the nfbcs Dec 14th 2025 seminar.  Did not get to present all, but you can find it here.

https://nfbcs.lewislwood.com

 

Select “thunderclient” from the combobox. The just cursor down or press “h” for heading.  Readit. 

 

Hope this helps.

 

Lewis Wood

 

 

From: NFBCS <nfbcs-bounces at nfbnet.org> On Behalf Of Ryan Stevens via NFBCS
Sent: Tuesday, February 17, 2026 1:21 PM
To: 'Aaron Cannon' <cannona at fireantproductions.com>; 'NFB in Computer Science Mailing List' <nfbcs at nfbnet.org>
Cc: Ryan Stevens <rysteve at comcast.net>
Subject: Re: [NFBCS] Postman alternative

 

Okay, I’ll try it. Thanks.

 

From: Aaron Cannon <cannona at fireantproductions.com <mailto:cannona at fireantproductions.com> > 
Sent: Tuesday, February 17, 2026 2:14 PM
To: NFB in Computer Science Mailing List <nfbcs at nfbnet.org <mailto:nfbcs at nfbnet.org> >
Cc: Ryan Stevens <rysteve at comcast.net <mailto:rysteve at comcast.net> >
Subject: Re: [NFBCS] Postman alternative

 

No direct fixes for you, but I do believe that almost anything that can be done with Postman can also be done with curl at the commandline.

 

Good luck.

 

Aaron Cannon

On Fri, Feb 13, 2026 at 11:07 Ryan Stevens via NFBCS <nfbcs at nfbnet.org <mailto:nfbcs at nfbnet.org> > wrote:

Hello,

 

The phone system my company uses for our call centers has changed the way we can pull back-end data for custom reports. They are using Data Lakehouse to create Parquet files. However, their interface is difficult to work with, so they suggested using Postman for the data pull. Postman’s accessibility turns out to be worse. Does anyone use a similar app that actually works? Any advice would be appreciated.

 

Thanks,

Ryan Stevens

 

_______________________________________________
NFBCS mailing list
NFBCS at nfbnet.org <mailto:NFBCS at nfbnet.org> 
http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org
To unsubscribe, change your list options or get your account info for NFBCS:
http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/cannona%40fireantproductions.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://nfbnet.org/pipermail/nfbcs_nfbnet.org/attachments/20260217/5a35f048/attachment.htm>

From carcione at access.net  Wed Feb 18 13:46:27 2026
From: carcione at access.net (carcione at access.net)
Date: Wed, 18 Feb 2026 08:46:27 -0500
Subject: [NFBCS] Website and browser question
Message-ID: <00d601dca0dc$fb15ee40$f141cac0$@access.net>

If I go to knitpicks.com using Firefox, it loads just fine, but, if I go to
the same site using Chrome, it gives me a network error and tells me to
check the spelling. And, if I put knitpicks into Google search and click on
an ad, I get a network error again.

Why?  I thought Chrome and Firefox use the same underlying engine, so why do
I get such different results?

Just curious.

Tracy

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://nfbnet.org/pipermail/nfbcs_nfbnet.org/attachments/20260218/0ce30e6b/attachment.htm>

From kevinsisco61784 at gmail.com  Wed Feb 18 15:54:14 2026
From: kevinsisco61784 at gmail.com (kevin SiscoKevin)
Date: Wed, 18 Feb 2026 07:54:14 -0800
Subject: [NFBCS] Website and browser question
In-Reply-To: <00d601dca0dc$fb15ee40$f141cac0$@access.net>
References: <00d601dca0dc$fb15ee40$f141cac0$@access.net>
Message-ID: <755b55b8-847b-40f4-93d5-fd86b1c0cbe3@gmail.com>

They do use the same engine.  Maybe it has to do with the SSL certificate?

Kevin

https://thesiscoreport.com


On 2/18/2026 5:46 AM, Tracy Carcione via NFBCS wrote:
>
> If I go to knitpicks.com using Firefox, it loads just fine, but, if I 
> go to the same site using Chrome, it gives me a network error and 
> tells me to check the spelling. And, if I put knitpicks into Google 
> search and click on an ad, I get a network error again.
>
> Why?  I thought Chrome and Firefox use the same underlying engine, so 
> why do I get such different results?
>
> Just curious.
>
> Tracy
>
>
> _______________________________________________
> NFBCS mailing list
> NFBCS at nfbnet.org
> http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org
> To unsubscribe, change your list options or get your account info for NFBCS:
> http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/kevinsisco61784%40gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://nfbnet.org/pipermail/nfbcs_nfbnet.org/attachments/20260218/d6f9b8d4/attachment.htm>

From jbar at barcore.com  Wed Feb 18 16:54:27 2026
From: jbar at barcore.com (Jim Barbour)
Date: Wed, 18 Feb 2026 10:54:27 -0600
Subject: [NFBCS] Website and browser question
In-Reply-To: <00d601dca0dc$fb15ee40$f141cac0$@access.net>
References: <00d601dca0dc$fb15ee40$f141cac0$@access.net>
Message-ID: <aZXuwxuxxv1wz6Iz@barcore.com>

Using my chrome, I had no problem going to knitpicks.com

Do you have any chrome extensions?  Especially ad blockers or the like the get between your chrome and DNS?

Jim

On Wed, Feb 18, 2026 at 08:46:27AM -0500, Tracy Carcione via NFBCS wrote:
> If I go to knitpicks.com using Firefox, it loads just fine, but, if I
> go to the same site using Chrome, it gives me a network error and tells
> me to check the spelling. And, if I put knitpicks into Google search
> and click on an ad, I get a network error again.
> 
> Why?  I thought Chrome and Firefox use the same underlying engine, so
> why do I get such different results?
> 
> Just curious.
> 
> Tracy


From chong.curtis at gmail.com  Wed Feb 18 16:58:59 2026
From: chong.curtis at gmail.com (Curtis Chong)
Date: Wed, 18 Feb 2026 09:58:59 -0700
Subject: [NFBCS] Website and browser question
In-Reply-To: <00d601dca0dc$fb15ee40$f141cac0$@access.net>
References: <00d601dca0dc$fb15ee40$f141cac0$@access.net>
Message-ID: <00c001dca0f7$e136bf20$a3a43d60$@gmail.com>

Good morning Tracy:

 

I was able to reach the knitpicks.com site using my version of Chrome. So,
I'm not sure what is going on here.

 

Sorry.

 

Cordially,

 

Curtis Chong

 

From: NFBCS <nfbcs-bounces at nfbnet.org> On Behalf Of Tracy Carcione via NFBCS
Sent: Wednesday, February 18, 2026 6:46 AM
To: 'NFB in Computer Science Mailing List' <nfbcs at nfbnet.org>
Cc: carcione at access.net
Subject: [NFBCS] Website and browser question

 

If I go to knitpicks.com using Firefox, it loads just fine, but, if I go to
the same site using Chrome, it gives me a network error and tells me to
check the spelling. And, if I put knitpicks into Google search and click on
an ad, I get a network error again.

Why?  I thought Chrome and Firefox use the same underlying engine, so why do
I get such different results?

Just curious.

Tracy

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://nfbnet.org/pipermail/nfbcs_nfbnet.org/attachments/20260218/54a65fd8/attachment.htm>

From shellbr at runbox.com  Wed Feb 18 16:59:21 2026
From: shellbr at runbox.com (Brian Shell)
Date: Wed, 18 Feb 2026 11:59:21 -0500
Subject: [NFBCS] Website and browser question
In-Reply-To: <00d601dca0dc$fb15ee40$f141cac0$@access.net>
References: <00d601dca0dc$fb15ee40$f141cac0$@access.net>
Message-ID: <836233a0-4e89-4abc-a97c-3689e4625090@runbox.com>

I thought the opposite was true where Firefox is the only major browser 
that is not Chromium-based.  This sounds like name resolution or maybe 
it is resolving and the connection is getting blocked elsewhere.  If the 
error mentions anything like name or can't find or resolve then it's 
DNS.  If it mentions a time out or connection refused, then something 
has blocked the traffic.  Firefox has DNS-over-HTTPS enabled by default 
which could make it resolve differently.  I think they forward to 
Cloudflare to determine if the website is safe.  It could also be 
security protection on your machine blocking the site although I'd 
expect it to trigger on Chrome too.  Maybe it's Firefox address bar 
automatic search feature trying to "help" by sending to a search engine 
which you can prevent by including the https:// in front of the website 
address.

On 2/18/2026 8:46 AM, Tracy Carcione via NFBCS wrote:
>
> If I go to knitpicks.com using Firefox, it loads just fine, but, if I 
> go to the same site using Chrome, it gives me a network error and 
> tells me to check the spelling. And, if I put knitpicks into Google 
> search and click on an ad, I get a network error again.
>
> Why?  I thought Chrome and Firefox use the same underlying engine, so 
> why do I get such different results?
>
> Just curious.
>
> Tracy
>
>
> _______________________________________________
> NFBCS mailing list
> NFBCS at nfbnet.org
> http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org
> To unsubscribe, change your list options or get your account info for NFBCS:
> http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/shellbr%40runbox.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://nfbnet.org/pipermail/nfbcs_nfbnet.org/attachments/20260218/33eee1f4/attachment.htm>

From deniserob at gmail.com  Wed Feb 18 17:26:59 2026
From: deniserob at gmail.com (Dr Denise M Robinson)
Date: Wed, 18 Feb 2026 12:26:59 -0500
Subject: [NFBCS] Website and browser question
In-Reply-To: <755b55b8-847b-40f4-93d5-fd86b1c0cbe3@gmail.com>
References: <00d601dca0dc$fb15ee40$f141cac0$@access.net>
 <755b55b8-847b-40f4-93d5-fd86b1c0cbe3@gmail.com>
Message-ID: 
 <CAAxsd_4sVAk60Jud6TWoLNQnowNfx7OfaVG99EzW6jN8cqobKw@mail.gmail.com>

Hi Tracy
No firefox does not use the same engine as Edge or Chrome: Edge and Chrome
are chromium based
Firefox uses Gecko
If chrome gives you issues, used Edge and the biggest feature in Edge is
when you search you can instantly get rid of all ads etc with and f9 for a
clean reading page


*Denise M Robinson*

Denise M Robinson, Ph.D., CTVI, AT, IT, CVI Endorsement, Director/CEO
425-220-6935

YouTube Channel: @DrDeniseMRobinsontech
<https://www.youtube.com/channel/UC7YW7Ves0phCwCOtaZ3wWFw>
YOURTECHVISION.COM
Dr Denise M Robinson – Educational Services for Instruction in Access
Technology/Braille/Nemeth and other Access skills
<https://yourtechvision.com/>
Technology that gives YOU Vision....



On Wed, Feb 18, 2026 at 10:55 AM kevin SiscoKevin via NFBCS <
nfbcs at nfbnet.org> wrote:

> They do use the same engine.  Maybe it has to do with the SSL certificate?
>
> Kevin
>
> https://thesiscoreport.com
>
>
> On 2/18/2026 5:46 AM, Tracy Carcione via NFBCS wrote:
>
> If I go to knitpicks.com using Firefox, it loads just fine, but, if I go
> to the same site using Chrome, it gives me a network error and tells me to
> check the spelling. And, if I put knitpicks into Google search and click on
> an ad, I get a network error again.
>
> Why?  I thought Chrome and Firefox use the same underlying engine, so why
> do I get such different results?
>
> Just curious.
>
> Tracy
>
>
>
> _______________________________________________
> NFBCS mailing listNFBCS at nfbnet.orghttp://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org
> To unsubscribe, change your list options or get your account info for NFBCS:http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/kevinsisco61784%40gmail.com
>
> _______________________________________________
> NFBCS mailing list
> NFBCS at nfbnet.org
> http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org
> To unsubscribe, change your list options or get your account info for
> NFBCS:
> http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/deniserob%40gmail.com
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://nfbnet.org/pipermail/nfbcs_nfbnet.org/attachments/20260218/16d30ad0/attachment.htm>

From mike at straddlethebox.org  Wed Feb 18 17:57:36 2026
From: mike at straddlethebox.org (Mike Gorse)
Date: Wed, 18 Feb 2026 11:57:36 -0600 (CST)
Subject: [NFBCS] Website and browser question
In-Reply-To: 
 <CAAxsd_4sVAk60Jud6TWoLNQnowNfx7OfaVG99EzW6jN8cqobKw@mail.gmail.com>
References: <00d601dca0dc$fb15ee40$f141cac0$@access.net>
 <755b55b8-847b-40f4-93d5-fd86b1c0cbe3@gmail.com>
 <CAAxsd_4sVAk60Jud6TWoLNQnowNfx7OfaVG99EzW6jN8cqobKw@mail.gmail.com>
Message-ID: <571c1559-92fc-9076-242c-1f87124e24b2@straddlethebox.org>

I wondered when I saw the posts on here saying that Firefox is using 
Chromium's engine, but then I Googled and found a reddit thread that 
suggested that maybe it was, and I looked at the Firefox source code and 
saw a lot of references to Chrome. Looking at the Wikipedia page, it 
appears that Firefox is now using a Chromium library for its inter-process 
communication, so maybe that is where the refernces come from that I was 
seeing. Now I suspect that the people who were saying this are thinking of 
Microsoft Edge using the Chromium engine.

On Wed, 18 Feb 2026, Dr Denise M Robinson via NFBCS wrote:

> Hi Tracy
> No firefox does not use the same engine as Edge or Chrome: Edge and Chrome are chromium based
> Firefox uses Gecko
> If chrome gives you issues, used Edge and the biggest feature in Edge is when you search you can instantly get rid of all ads etc with and f9 for a clean reading page
>   
> 
> Denise M Robinson
> 
> 
> Denise M Robinson, Ph.D., CTVI, AT, IT, CVI Endorsement, Director/CEO
> 425-220-6935
> 
> YouTube Channel: @DrDeniseMRobinsontech
> YOURTECHVISION.COM
> Dr Denise M Robinson – Educational Services for Instruction in Access Technology/Braille/Nemeth and other Access skills
> Technology that gives YOU Vision....
> 
> 
> 
> On Wed, Feb 18, 2026 at 10:55 AM kevin SiscoKevin via NFBCS <nfbcs at nfbnet.org> wrote:
>
>       They do use the same engine.  Maybe it has to do with the SSL certificate?
>
>       Kevin
>
>       https://thesiscoreport.com
> 
>
>       On 2/18/2026 5:46 AM, Tracy Carcione via NFBCS wrote:
>
>       If I go to knitpicks.com using Firefox, it loads just fine, but, if I go to the same site using Chrome, it gives me a network error and tells me to check the spelling. And, if I put knitpicks into Google search and
>       click on an ad, I get a network error again.
>
>       Why?  I thought Chrome and Firefox use the same underlying engine, so why do I get such different results?
>
>       Just curious.
>
>       Tracy
>
>        
> 
> 
> _______________________________________________
> NFBCS mailing list
> NFBCS at nfbnet.org
> http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org
> To unsubscribe, change your list options or get your account info for NFBCS:
> http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/kevinsisco61784%40gmail.com
> 
> _______________________________________________
> NFBCS mailing list
> NFBCS at nfbnet.org
> http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org
> To unsubscribe, change your list options or get your account info for NFBCS:
> http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/deniserob%40gmail.com
> 
> 
>

From lewislwood at gmail.com  Wed Feb 18 18:37:17 2026
From: lewislwood at gmail.com (Lewis Wood)
Date: Wed, 18 Feb 2026 12:37:17 -0600
Subject: [NFBCS] Website and browser question
In-Reply-To: <00d601dca0dc$fb15ee40$f141cac0$@access.net>
References: <00d601dca0dc$fb15ee40$f141cac0$@access.net>
Message-ID: <005e01dca105$9c662300$d5326900$@gmail.com>

 

You may want to try and clear the chrome dns caching mechanism.

 

 

I read about this feature a few years back when I was searching for hosting.

 

Here is a link a found:

 

https://www.youtube.com/watch?v=LQk3OmxwZ-k

 

My google search was "chrome settings clear dns caching"

 

Worldwide chaching is done regional in order to get fast dns resolution.

 

I hope this helps..

Lewis Wood

 

From: NFBCS <nfbcs-bounces at nfbnet.org> On Behalf Of Tracy Carcione via NFBCS
Sent: Wednesday, February 18, 2026 7:46 AM
To: 'NFB in Computer Science Mailing List' <nfbcs at nfbnet.org>
Cc: carcione at access.net
Subject: [NFBCS] Website and browser question

 

If I go to knitpicks.com using Firefox, it loads just fine, but, if I go to
the same site using Chrome, it gives me a network error and tells me to
check the spelling. And, if I put knitpicks into Google search and click on
an ad, I get a network error again.

Why?  I thought Chrome and Firefox use the same underlying engine, so why do
I get such different results?

Just curious.

Tracy

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://nfbnet.org/pipermail/nfbcs_nfbnet.org/attachments/20260218/7441556a/attachment.htm>

From deniserob at gmail.com  Wed Feb 18 20:31:26 2026
From: deniserob at gmail.com (Dr Denise M Robinson)
Date: Wed, 18 Feb 2026 15:31:26 -0500
Subject: [NFBCS] Website and browser question-clearing up information
In-Reply-To: <571c1559-92fc-9076-242c-1f87124e24b2@straddlethebox.org>
References: <00d601dca0dc$fb15ee40$f141cac0$@access.net>
 <755b55b8-847b-40f4-93d5-fd86b1c0cbe3@gmail.com>
 <CAAxsd_4sVAk60Jud6TWoLNQnowNfx7OfaVG99EzW6jN8cqobKw@mail.gmail.com>
 <571c1559-92fc-9076-242c-1f87124e24b2@straddlethebox.org>
Message-ID: 
 <CAAxsd_62ccrtpRbzA4nCNjG+Gymckn_Ek3MCTntqOhKT1qS1=g@mail.gmail.com>

Hey people: This can be a confusing topic but since I teach this every day,
let me help.
FireFox is and has always had the engine Gecko which is created by Mozilla
hence the full name Mozilla Firefox and is VERY different than the 2
chromium based browsers most use which is Chrome and Edge. Might as well
add a side note here. Chrome is being plagued with hackers so make sure you
check your updates EVERYDAY--ALT F then e to help and enter and enter on
about and it will auto update, when done close and reopen

Edge is far more accessible as it has built in immersive reader so when you
go to a cluttered page you can press F9 and insert down arrow and smile big
as it leaves only the text you want-- F9 to go back to full page
While I am giving info: Chrome, Edge, Brave, Opera, Vivaldi, Arc, etc. have
the Blink engine and are chromium based
That is a lot of info but I will also tell you that if you are taking a
foreign language Firefox is the way to go as it conflicts with Chroium
based browsers
Hope that helps


*Denise M Robinson*

Denise M Robinson, Ph.D., CTVI, AT, IT, CVI Endorsement, Director/CEO
425-220-6935

YouTube Channel: @DrDeniseMRobinsontech
<https://www.youtube.com/channel/UC7YW7Ves0phCwCOtaZ3wWFw>
YOURTECHVISION.COM
Dr Denise M Robinson – Educational Services for Instruction in Access
Technology/Braille/Nemeth and other Access skills
<https://yourtechvision.com/>
Technology that gives YOU Vision....



On Wed, Feb 18, 2026 at 1:04 PM Mike Gorse via NFBCS <nfbcs at nfbnet.org>
wrote:

> I wondered when I saw the posts on here saying that Firefox is using
> Chromium's engine, but then I Googled and found a reddit thread that
> suggested that maybe it was, and I looked at the Firefox source code and
> saw a lot of references to Chrome. Looking at the Wikipedia page, it
> appears that Firefox is now using a Chromium library for its inter-process
> communication, so maybe that is where the refernces come from that I was
> seeing. Now I suspect that the people who were saying this are thinking of
> Microsoft Edge using the Chromium engine.
>
> On Wed, 18 Feb 2026, Dr Denise M Robinson via NFBCS wrote:
>
> > Hi Tracy
> > No firefox does not use the same engine as Edge or Chrome: Edge and
> Chrome are chromium based
> > Firefox uses Gecko
> > If chrome gives you issues, used Edge and the biggest feature in Edge is
> when you search you can instantly get rid of all ads etc with and f9 for a
> clean reading page
> >
> >
> > Denise M Robinson
> >
> >
> > Denise M Robinson, Ph.D., CTVI, AT, IT, CVI Endorsement, Director/CEO
> > 425-220-6935
> >
> > YouTube Channel: @DrDeniseMRobinsontech
> > YOURTECHVISION.COM
> > Dr Denise M Robinson – Educational Services for Instruction in Access
> Technology/Braille/Nemeth and other Access skills
> > Technology that gives YOU Vision....
> >
> >
> >
> > On Wed, Feb 18, 2026 at 10:55 AM kevin SiscoKevin via NFBCS <
> nfbcs at nfbnet.org> wrote:
> >
> >       They do use the same engine.  Maybe it has to do with the SSL
> certificate?
> >
> >       Kevin
> >
> >       https://thesiscoreport.com
> >
> >
> >       On 2/18/2026 5:46 AM, Tracy Carcione via NFBCS wrote:
> >
> >       If I go to knitpicks.com using Firefox, it loads just fine, but,
> if I go to the same site using Chrome, it gives me a network error and
> tells me to check the spelling. And, if I put knitpicks into Google search
> and
> >       click on an ad, I get a network error again.
> >
> >       Why?  I thought Chrome and Firefox use the same underlying engine,
> so why do I get such different results?
> >
> >       Just curious.
> >
> >       Tracy
> >
> >
> >
> >
> > _______________________________________________
> > NFBCS mailing list
> > NFBCS at nfbnet.org
> > http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org
> > To unsubscribe, change your list options or get your account info for
> NFBCS:
> >
> http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/kevinsisco61784%40gmail.com
> >
> > _______________________________________________
> > NFBCS mailing list
> > NFBCS at nfbnet.org
> > http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org
> > To unsubscribe, change your list options or get your account info for
> NFBCS:
> > http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/deniserob%40gmail.com
> >
> >
> >_______________________________________________
> NFBCS mailing list
> NFBCS at nfbnet.org
> http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org
> To unsubscribe, change your list options or get your account info for
> NFBCS:
> http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/deniserob%40gmail.com
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://nfbnet.org/pipermail/nfbcs_nfbnet.org/attachments/20260218/53ab63d0/attachment.htm>

From jbar at barcore.com  Wed Feb 18 21:48:14 2026
From: jbar at barcore.com (Jim Barbour)
Date: Wed, 18 Feb 2026 15:48:14 -0600
Subject: [NFBCS] Website and browser question-clearing up information
In-Reply-To: 
 <CAAxsd_62ccrtpRbzA4nCNjG+Gymckn_Ek3MCTntqOhKT1qS1=g@mail.gmail.com>
References: <00d601dca0dc$fb15ee40$f141cac0$@access.net>
 <755b55b8-847b-40f4-93d5-fd86b1c0cbe3@gmail.com>
 <CAAxsd_4sVAk60Jud6TWoLNQnowNfx7OfaVG99EzW6jN8cqobKw@mail.gmail.com>
 <571c1559-92fc-9076-242c-1f87124e24b2@straddlethebox.org>
 <CAAxsd_62ccrtpRbzA4nCNjG+Gymckn_Ek3MCTntqOhKT1qS1=g@mail.gmail.com>
Message-ID: <aZYznqtqL8HUK681@barcore.com>

Hey All,

While what Denise is saying about engines is correct, it isn't really helpful with Tracy's problem.

Quoting Tracy, "it gives me a network error and tells me to check the spelling." This is likely not an issue with how content is rendered, which would differ based on the engine, but a networking issue not being able to look up or connect to the domain knitpicks.com.

Since Tracy is able to connect to it from Firefox, I assume it isn't a problem with the host's DNS.  I'm assuming that an extension is getting between Chrome and an authoritative DNS server.  Likely extensions include DNS over HTTPS, which is designed to hide your network traffic patterns from your ISP, an ad blocker, which resolve ad serving hosts to localhost, a parental control extension, which does the same thing for adult sites, or a web based VPN.

It is possible that the reverse is true. That the system's DNS is somehow wonky, and firefox is getting around it by using an extension to talk to a valid DNS.  This seems less likely, but certainly possible.

I hope this helps Tracy debug this.

Take Care,

Jim

On Wed, Feb 18, 2026 at 03:31:26PM -0500, Dr Denise M Robinson via NFBCS wrote:
> Hey people: This can be a confusing topic but since I teach this every
> day, let me help.
> FireFox is and has always had the engine Gecko which is created by
> Mozilla hence the full name Mozilla Firefox and is VERY different than
> the 2 chromium based browsers most use which is Chrome and Edge. Might
> as well add a side note here. Chrome is being plagued with hackers so
> make sure you check your updates EVERYDAY--ALT F then e to help and
> enter and enter on about and it will auto update, when done close and
> reopen
> Edge is far more accessible as it has built in immersive reader so when
> you go to a cluttered page you can press F9 and insert down arrow and
> smile big as it leaves only the text you want-- F9 to go back to full
> page
> While I am giving info: Chrome, Edge, Brave, Opera, Vivaldi, Arc, etc.
> have the Blink engine and are chromium based
> That is a lot of info but I will also tell you that if you are taking a
> foreign language Firefox is the way to go as it conflicts with Chroium
> based browsers
> Hope that helps
> 
> 
> Denise M Robinson
> Denise M Robinson, Ph.D., CTVI, AT, IT, CVI Endorsement, Director/CEO
> 425-220-6935
> YouTube Channel: @DrDeniseMRobinsontech
> YOURTECHVISION.COM
> Dr Denise M Robinson – Educational Services for Instruction in Access
> Technology/Braille/Nemeth and other Access skills
> Technology that gives YOU Vision....
> On Wed, Feb 18, 2026 at 1:04 PM Mike Gorse via NFBCS <nfbcs at nfbnet.org>
> wrote:
> 
>   I wondered when I saw the posts on here saying that Firefox is using
>   Chromium's engine, but then I Googled and found a reddit thread that
>   suggested that maybe it was, and I looked at the Firefox source code
>   and
>   saw a lot of references to Chrome. Looking at the Wikipedia page, it
>   appears that Firefox is now using a Chromium library for its
>   inter-process
>   communication, so maybe that is where the refernces come from that I
>   was
>   seeing. Now I suspect that the people who were saying this are
>   thinking of
>   Microsoft Edge using the Chromium engine.
>   On Wed, 18 Feb 2026, Dr Denise M Robinson via NFBCS wrote:
>   > Hi Tracy
>   > No firefox does not use the same engine as Edge or Chrome: Edge
>   and Chrome are chromium based
>   > Firefox uses Gecko
>   > If chrome gives you issues, used Edge and the biggest feature in
>   Edge is when you search you can instantly get rid of all ads etc
>   with and f9 for a clean reading page
>   >
>   >
>   > Denise M Robinson
>   >
>   >
>   > Denise M Robinson, Ph.D., CTVI, AT, IT, CVI Endorsement,
>   Director/CEO
>   > 425-220-6935
>   >
>   > YouTube Channel: @DrDeniseMRobinsontech
>   > YOURTECHVISION.COM
>   > Dr Denise M Robinson – Educational Services for Instruction in
>   Access Technology/Braille/Nemeth and other Access skills
>   > Technology that gives YOU Vision....
>   >
>   >
>   >
>   > On Wed, Feb 18, 2026 at 10:55 AM kevin SiscoKevin via NFBCS
>   <nfbcs at nfbnet.org> wrote:
>   >
>   >       They do use the same engine.  Maybe it has to do with the
>   SSL certificate?
>   >
>   >       Kevin
>   >
>   >       https://thesiscoreport.com
>   >
>   >
>   >       On 2/18/2026 5:46 AM, Tracy Carcione via NFBCS wrote:
>   >
>   >       If I go to knitpicks.com using Firefox, it loads just fine,
>   but, if I go to the same site using Chrome, it gives me a network
>   error and tells me to check the spelling. And, if I put knitpicks
>   into Google search and
>   >       click on an ad, I get a network error again.
>   >
>   >       Why?  I thought Chrome and Firefox use the same underlying
>   engine, so why do I get such different results?
>   >
>   >       Just curious.
>   >
>   >       Tracy
>   >
>   >
>   >
>   >
>   > _______________________________________________
>   > NFBCS mailing list
>   > NFBCS at nfbnet.org
>   > http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org
>   > To unsubscribe, change your list options or get your account info
>   for NFBCS:
>   >
>   http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/kevinsisco61784%4
>   0gmail.com
>   >
>   > _______________________________________________
>   > NFBCS mailing list
>   > NFBCS at nfbnet.org
>   > http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org
>   > To unsubscribe, change your list options or get your account info
>   for NFBCS:
>   >
>   http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/deniserob%40gmail
>   .com
>   >
>   >
>   >_______________________________________________
>   NFBCS mailing list
>   NFBCS at nfbnet.org
>   http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org
>   To unsubscribe, change your list options or get your account info
>   for NFBCS:
>   http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/deniserob%40gmail
>   .com


From carcione at access.net  Wed Feb 18 22:20:43 2026
From: carcione at access.net (carcione at access.net)
Date: Wed, 18 Feb 2026 17:20:43 -0500
Subject: [NFBCS] Website and browser question-clearing up information
In-Reply-To: <aZYznqtqL8HUK681@barcore.com>
References: <00d601dca0dc$fb15ee40$f141cac0$@access.net>
 <755b55b8-847b-40f4-93d5-fd86b1c0cbe3@gmail.com>
 <CAAxsd_4sVAk60Jud6TWoLNQnowNfx7OfaVG99EzW6jN8cqobKw@mail.gmail.com>
 <571c1559-92fc-9076-242c-1f87124e24b2@straddlethebox.org>
 <CAAxsd_62ccrtpRbzA4nCNjG+Gymckn_Ek3MCTntqOhKT1qS1=g@mail.gmail.com>
 <aZYznqtqL8HUK681@barcore.com>
Message-ID: <025501dca124$d2a0cb40$77e261c0$@access.net>

Thanks all.  I've learned some things from the discussion.
I don't recall getting any extensions to Chrome.  Certainly not in the last couple weeks, and I'm pretty sure I've been to the knitpicks site recently.  
I haven't tried it with Edge yet, but I will.  It's useful to know I can get an ad-free version of a website with Edge, and I'll give that a try.
Meanwhile, I can get what I want with Firefox, so I'm OK.  It just seems odd.  Especially since other people, like Curtis, can get to knitpicks with Chrome.  Maybe I'll clear my history and see if that helps.
Tracy


-----Original Message-----
From: NFBCS <nfbcs-bounces at nfbnet.org> On Behalf Of Jim Barbour via NFBCS
Sent: Wednesday, February 18, 2026 4:48 PM
To: NFB in Computer Science Mailing List <nfbcs at nfbnet.org>
Cc: Jim Barbour <jbar at barcore.com>
Subject: Re: [NFBCS] Website and browser question-clearing up information

Hey All,

While what Denise is saying about engines is correct, it isn't really helpful with Tracy's problem.

Quoting Tracy, "it gives me a network error and tells me to check the spelling." This is likely not an issue with how content is rendered, which would differ based on the engine, but a networking issue not being able to look up or connect to the domain knitpicks.com.

Since Tracy is able to connect to it from Firefox, I assume it isn't a problem with the host's DNS.  I'm assuming that an extension is getting between Chrome and an authoritative DNS server.  Likely extensions include DNS over HTTPS, which is designed to hide your network traffic patterns from your ISP, an ad blocker, which resolve ad serving hosts to localhost, a parental control extension, which does the same thing for adult sites, or a web based VPN.

It is possible that the reverse is true. That the system's DNS is somehow wonky, and firefox is getting around it by using an extension to talk to a valid DNS.  This seems less likely, but certainly possible.

I hope this helps Tracy debug this.

Take Care,

Jim

On Wed, Feb 18, 2026 at 03:31:26PM -0500, Dr Denise M Robinson via NFBCS wrote:
> Hey people: This can be a confusing topic but since I teach this every 
> day, let me help.
> FireFox is and has always had the engine Gecko which is created by 
> Mozilla hence the full name Mozilla Firefox and is VERY different than 
> the 2 chromium based browsers most use which is Chrome and Edge. Might 
> as well add a side note here. Chrome is being plagued with hackers so 
> make sure you check your updates EVERYDAY--ALT F then e to help and 
> enter and enter on about and it will auto update, when done close and 
> reopen Edge is far more accessible as it has built in immersive reader 
> so when you go to a cluttered page you can press F9 and insert down 
> arrow and smile big as it leaves only the text you want-- F9 to go 
> back to full page While I am giving info: Chrome, Edge, Brave, Opera, 
> Vivaldi, Arc, etc.
> have the Blink engine and are chromium based That is a lot of info but 
> I will also tell you that if you are taking a foreign language Firefox 
> is the way to go as it conflicts with Chroium based browsers Hope that 
> helps
> 
> 
> Denise M Robinson
> Denise M Robinson, Ph.D., CTVI, AT, IT, CVI Endorsement, Director/CEO
> 425-220-6935
> YouTube Channel: @DrDeniseMRobinsontech YOURTECHVISION.COM Dr Denise M 
> Robinson – Educational Services for Instruction in Access 
> Technology/Braille/Nemeth and other Access skills Technology that 
> gives YOU Vision....
> On Wed, Feb 18, 2026 at 1:04 PM Mike Gorse via NFBCS 
> <nfbcs at nfbnet.org>
> wrote:
> 
>   I wondered when I saw the posts on here saying that Firefox is using
>   Chromium's engine, but then I Googled and found a reddit thread that
>   suggested that maybe it was, and I looked at the Firefox source code
>   and
>   saw a lot of references to Chrome. Looking at the Wikipedia page, it
>   appears that Firefox is now using a Chromium library for its
>   inter-process
>   communication, so maybe that is where the refernces come from that I
>   was
>   seeing. Now I suspect that the people who were saying this are
>   thinking of
>   Microsoft Edge using the Chromium engine.
>   On Wed, 18 Feb 2026, Dr Denise M Robinson via NFBCS wrote:
>   > Hi Tracy
>   > No firefox does not use the same engine as Edge or Chrome: Edge
>   and Chrome are chromium based
>   > Firefox uses Gecko
>   > If chrome gives you issues, used Edge and the biggest feature in
>   Edge is when you search you can instantly get rid of all ads etc
>   with and f9 for a clean reading page
>   >
>   >
>   > Denise M Robinson
>   >
>   >
>   > Denise M Robinson, Ph.D., CTVI, AT, IT, CVI Endorsement,
>   Director/CEO
>   > 425-220-6935
>   >
>   > YouTube Channel: @DrDeniseMRobinsontech
>   > YOURTECHVISION.COM
>   > Dr Denise M Robinson – Educational Services for Instruction in
>   Access Technology/Braille/Nemeth and other Access skills
>   > Technology that gives YOU Vision....
>   >
>   >
>   >
>   > On Wed, Feb 18, 2026 at 10:55 AM kevin SiscoKevin via NFBCS
>   <nfbcs at nfbnet.org> wrote:
>   >
>   >       They do use the same engine.  Maybe it has to do with the
>   SSL certificate?
>   >
>   >       Kevin
>   >
>   >       https://thesiscoreport.com
>   >
>   >
>   >       On 2/18/2026 5:46 AM, Tracy Carcione via NFBCS wrote:
>   >
>   >       If I go to knitpicks.com using Firefox, it loads just fine,
>   but, if I go to the same site using Chrome, it gives me a network
>   error and tells me to check the spelling. And, if I put knitpicks
>   into Google search and
>   >       click on an ad, I get a network error again.
>   >
>   >       Why?  I thought Chrome and Firefox use the same underlying
>   engine, so why do I get such different results?
>   >
>   >       Just curious.
>   >
>   >       Tracy
>   >
>   >
>   >
>   >
>   > _______________________________________________
>   > NFBCS mailing list
>   > NFBCS at nfbnet.org
>   > http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org
>   > To unsubscribe, change your list options or get your account info
>   for NFBCS:
>   >
>   http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/kevinsisco61784%4
>   0gmail.com
>   >
>   > _______________________________________________
>   > NFBCS mailing list
>   > NFBCS at nfbnet.org
>   > http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org
>   > To unsubscribe, change your list options or get your account info
>   for NFBCS:
>   >
>   http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/deniserob%40gmail
>   .com
>   >
>   >
>   >_______________________________________________
>   NFBCS mailing list
>   NFBCS at nfbnet.org
>   http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org
>   To unsubscribe, change your list options or get your account info
>   for NFBCS:
>   http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/deniserob%40gmail
>   .com


_______________________________________________
NFBCS mailing list
NFBCS at nfbnet.org
http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org
To unsubscribe, change your list options or get your account info for NFBCS:
http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/carcione%40access.net


From lewislwood at gmail.com  Thu Feb 19 01:13:11 2026
From: lewislwood at gmail.com (Lewis Wood)
Date: Wed, 18 Feb 2026 19:13:11 -0600
Subject: [NFBCS] Website and browser question-clearing up information
In-Reply-To: <025501dca124$d2a0cb40$77e261c0$@access.net>
References: <00d601dca0dc$fb15ee40$f141cac0$@access.net>
 <755b55b8-847b-40f4-93d5-fd86b1c0cbe3@gmail.com>
 <CAAxsd_4sVAk60Jud6TWoLNQnowNfx7OfaVG99EzW6jN8cqobKw@mail.gmail.com>
 <571c1559-92fc-9076-242c-1f87124e24b2@straddlethebox.org>
 <CAAxsd_62ccrtpRbzA4nCNjG+Gymckn_Ek3MCTntqOhKT1qS1=g@mail.gmail.com>
 <aZYznqtqL8HUK681@barcore.com> <025501dca124$d2a0cb40$77e261c0$@access.net>
Message-ID: <004601dca13c$eaf09fa0$c0d1dee0$@gmail.com>

I was curious are you able to go to the website without relying on dns resolution?

To get IP just ping http://website
It will display the address.
Now enter that in the address bar.

Lewis Wood

-----Original Message-----
From: NFBCS <nfbcs-bounces at nfbnet.org> On Behalf Of Tracy Carcione via NFBCS
Sent: Wednesday, February 18, 2026 4:21 PM
To: 'NFB in Computer Science Mailing List' <nfbcs at nfbnet.org>
Cc: carcione at access.net
Subject: Re: [NFBCS] Website and browser question-clearing up information

Thanks all.  I've learned some things from the discussion.
I don't recall getting any extensions to Chrome.  Certainly not in the last couple weeks, and I'm pretty sure I've been to the knitpicks site recently.  
I haven't tried it with Edge yet, but I will.  It's useful to know I can get an ad-free version of a website with Edge, and I'll give that a try.
Meanwhile, I can get what I want with Firefox, so I'm OK.  It just seems odd.  Especially since other people, like Curtis, can get to knitpicks with Chrome.  Maybe I'll clear my history and see if that helps.
Tracy


-----Original Message-----
From: NFBCS <nfbcs-bounces at nfbnet.org> On Behalf Of Jim Barbour via NFBCS
Sent: Wednesday, February 18, 2026 4:48 PM
To: NFB in Computer Science Mailing List <nfbcs at nfbnet.org>
Cc: Jim Barbour <jbar at barcore.com>
Subject: Re: [NFBCS] Website and browser question-clearing up information

Hey All,

While what Denise is saying about engines is correct, it isn't really helpful with Tracy's problem.

Quoting Tracy, "it gives me a network error and tells me to check the spelling." This is likely not an issue with how content is rendered, which would differ based on the engine, but a networking issue not being able to look up or connect to the domain knitpicks.com.

Since Tracy is able to connect to it from Firefox, I assume it isn't a problem with the host's DNS.  I'm assuming that an extension is getting between Chrome and an authoritative DNS server.  Likely extensions include DNS over HTTPS, which is designed to hide your network traffic patterns from your ISP, an ad blocker, which resolve ad serving hosts to localhost, a parental control extension, which does the same thing for adult sites, or a web based VPN.

It is possible that the reverse is true. That the system's DNS is somehow wonky, and firefox is getting around it by using an extension to talk to a valid DNS.  This seems less likely, but certainly possible.

I hope this helps Tracy debug this.

Take Care,

Jim

On Wed, Feb 18, 2026 at 03:31:26PM -0500, Dr Denise M Robinson via NFBCS wrote:
> Hey people: This can be a confusing topic but since I teach this every 
> day, let me help.
> FireFox is and has always had the engine Gecko which is created by 
> Mozilla hence the full name Mozilla Firefox and is VERY different than 
> the 2 chromium based browsers most use which is Chrome and Edge. Might 
> as well add a side note here. Chrome is being plagued with hackers so 
> make sure you check your updates EVERYDAY--ALT F then e to help and 
> enter and enter on about and it will auto update, when done close and 
> reopen Edge is far more accessible as it has built in immersive reader 
> so when you go to a cluttered page you can press F9 and insert down 
> arrow and smile big as it leaves only the text you want-- F9 to go 
> back to full page While I am giving info: Chrome, Edge, Brave, Opera, 
> Vivaldi, Arc, etc.
> have the Blink engine and are chromium based That is a lot of info but 
> I will also tell you that if you are taking a foreign language Firefox 
> is the way to go as it conflicts with Chroium based browsers Hope that 
> helps
> 
> 
> Denise M Robinson
> Denise M Robinson, Ph.D., CTVI, AT, IT, CVI Endorsement, Director/CEO
> 425-220-6935
> YouTube Channel: @DrDeniseMRobinsontech YOURTECHVISION.COM Dr Denise M 
> Robinson – Educational Services for Instruction in Access 
> Technology/Braille/Nemeth and other Access skills Technology that 
> gives YOU Vision....
> On Wed, Feb 18, 2026 at 1:04 PM Mike Gorse via NFBCS 
> <nfbcs at nfbnet.org>
> wrote:
> 
>   I wondered when I saw the posts on here saying that Firefox is using
>   Chromium's engine, but then I Googled and found a reddit thread that
>   suggested that maybe it was, and I looked at the Firefox source code
>   and
>   saw a lot of references to Chrome. Looking at the Wikipedia page, it
>   appears that Firefox is now using a Chromium library for its
>   inter-process
>   communication, so maybe that is where the refernces come from that I
>   was
>   seeing. Now I suspect that the people who were saying this are
>   thinking of
>   Microsoft Edge using the Chromium engine.
>   On Wed, 18 Feb 2026, Dr Denise M Robinson via NFBCS wrote:
>   > Hi Tracy
>   > No firefox does not use the same engine as Edge or Chrome: Edge
>   and Chrome are chromium based
>   > Firefox uses Gecko
>   > If chrome gives you issues, used Edge and the biggest feature in
>   Edge is when you search you can instantly get rid of all ads etc
>   with and f9 for a clean reading page
>   >
>   >
>   > Denise M Robinson
>   >
>   >
>   > Denise M Robinson, Ph.D., CTVI, AT, IT, CVI Endorsement,
>   Director/CEO
>   > 425-220-6935
>   >
>   > YouTube Channel: @DrDeniseMRobinsontech
>   > YOURTECHVISION.COM
>   > Dr Denise M Robinson – Educational Services for Instruction in
>   Access Technology/Braille/Nemeth and other Access skills
>   > Technology that gives YOU Vision....
>   >
>   >
>   >
>   > On Wed, Feb 18, 2026 at 10:55 AM kevin SiscoKevin via NFBCS
>   <nfbcs at nfbnet.org> wrote:
>   >
>   >       They do use the same engine.  Maybe it has to do with the
>   SSL certificate?
>   >
>   >       Kevin
>   >
>   >       https://thesiscoreport.com
>   >
>   >
>   >       On 2/18/2026 5:46 AM, Tracy Carcione via NFBCS wrote:
>   >
>   >       If I go to knitpicks.com using Firefox, it loads just fine,
>   but, if I go to the same site using Chrome, it gives me a network
>   error and tells me to check the spelling. And, if I put knitpicks
>   into Google search and
>   >       click on an ad, I get a network error again.
>   >
>   >       Why?  I thought Chrome and Firefox use the same underlying
>   engine, so why do I get such different results?
>   >
>   >       Just curious.
>   >
>   >       Tracy
>   >
>   >
>   >
>   >
>   > _______________________________________________
>   > NFBCS mailing list
>   > NFBCS at nfbnet.org
>   > http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org
>   > To unsubscribe, change your list options or get your account info
>   for NFBCS:
>   >
>   http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/kevinsisco61784%4
>   0gmail.com
>   >
>   > _______________________________________________
>   > NFBCS mailing list
>   > NFBCS at nfbnet.org
>   > http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org
>   > To unsubscribe, change your list options or get your account info
>   for NFBCS:
>   >
>   http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/deniserob%40gmail
>   .com
>   >
>   >
>   >_______________________________________________
>   NFBCS mailing list
>   NFBCS at nfbnet.org
>   http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org
>   To unsubscribe, change your list options or get your account info
>   for NFBCS:
>   http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/deniserob%40gmail
>   .com


_______________________________________________
NFBCS mailing list
NFBCS at nfbnet.org
http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org
To unsubscribe, change your list options or get your account info for NFBCS:
http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/carcione%40access.net


_______________________________________________
NFBCS mailing list
NFBCS at nfbnet.org
http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org
To unsubscribe, change your list options or get your account info for NFBCS:
http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/lewislwood%40gmail.com


From ljmaher03 at outlook.com  Fri Feb 20 17:36:26 2026
From: ljmaher03 at outlook.com (Louis Maher)
Date: Fri, 20 Feb 2026 17:36:26 +0000
Subject: [NFBCS] Reminder: The Science and Engineering Division and National
 Association of Blind Students Joint STEM Seminar
In-Reply-To: 
 <SJ0PR14MB5230D91E09A284CE38D834C8AA68A@SJ0PR14MB5230.namprd14.prod.outlook.com>
References: 
 <SJ0PR14MB5230D91E09A284CE38D834C8AA68A@SJ0PR14MB5230.namprd14.prod.outlook.com>
Message-ID: 
 <SJ0PR14MB523024D6155857D38FF7117BAA68A@SJ0PR14MB5230.namprd14.prod.outlook.com>

Hello,

Two divisions of the National Federation of the Blind, namely: The Science and Engineering Division (SED) and the National Association of Blind Students (NABS), are presenting a joint Zoom conference on how blind college and graduate students, and blind professionals, are succeeding in courses and careers in science, technology, engineering, and mathematics. The Zoom conference link will be the standard NABS Zoom link shown at the bottom of this message. The call will occur at 7:30 PM EST through 9 PM EST on Sunday, February 22, 2026. We will have three speakers. Each talk will be twenty minutes long with an extra five minutes for questions.

I have attached the meeting program to this message.

Join Zoom Meeting:
February 22, 2026, 7:30 PM EST

Zoom Meeting Room <https://zoom.us/j/4678833687?_x_zm_rtaid=KOKAICd1R4ihtmx1LS5OTg.1769021469326.3ccbb5b08dc1b4996eb5278c87f34feb&_x_zm_rhtaid=216%23success>

Meeting ID: 467 883 3687

One tap mobile
+13017158592,4678833687 US (Germantown)

13126266799,,4678833687# US (Chicago)

Regards
Louis Maher
Phone: 713-444-7838
Email: ljmaher03 at outlook.com<mailto:ljmaher03 at outlook.com>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://nfbnet.org/pipermail/nfbcs_nfbnet.org/attachments/20260220/8c8f31e8/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Announcement For A Zoom Conference On How The Blind Can Do STEM 2026-02-22 (1).docx
Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document
Size: 30778 bytes
Desc: Announcement For A Zoom Conference On How The Blind Can Do STEM 2026-02-22 (1).docx
URL: <http://nfbnet.org/pipermail/nfbcs_nfbnet.org/attachments/20260220/8c8f31e8/attachment.docx>

From wbsjr at swbell.net  Fri Feb 20 17:37:14 2026
From: wbsjr at swbell.net (Bradford Snyder)
Date: Fri, 20 Feb 2026 11:37:14 -0600
Subject: [NFBCS] GIT Going with Github
In-Reply-To: 
 <CYYPR02MB9901F1DB182FEDB7FD0CAACDBA68A@CYYPR02MB9901.namprd02.prod.outlook.com>
References: 
 <CYYPR02MB9901F1DB182FEDB7FD0CAACDBA68A@CYYPR02MB9901.namprd02.prod.outlook.com>
Message-ID: <55198A9B-7E82-4111-AD80-128C03220841@swbell.net>

Hello Everyone:
 
Blind Information Technology Solutions (BITS) <http://www.joinbits.org/> in partnership with Github <http://www.github.com/> are holding a two all-day workshop on Github, Visual Studio Code and agentic use <https://bits-acb.github.io/git-going-with-github/>.
 
You can find out more here:
 
https://bits-acb.github.io/git-going-with-github/
 
This is open, free and available to all blind and low vision people. No requirements accept having an interest are assumed. No coding languages will be covered other than markdown.
 
Again, please share with your friends and communities.



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://nfbnet.org/pipermail/nfbcs_nfbnet.org/attachments/20260220/258e076f/attachment.htm>

From pdonahue2 at satx.rr.com  Fri Feb 20 20:32:03 2026
From: pdonahue2 at satx.rr.com (Peter)
Date: Fri, 20 Feb 2026 14:32:03 -0600
Subject: [NFBCS] : [Touching-python] GIT Going with Github
Message-ID: <00b601dca2a7$f96ab3b0$ec401b10$@satx.rr.com>

Hello everyone,

 

Just passing this along.

 

From: 

Touching-python at groups.io <mailto:Touching-python at groups.io> 

Touching-python at groups.io <mailto:Touching-python at groups.io> 

On Behalf Of Jeff Bishop via groups.io

Sent: Friday, February 20, 2026 11:05 AM

To: 

touching-python at groups.io <mailto:touching-python at groups.io> 

Subject: [Touching-python] GIT Going with Github

 

Hello Everyone:

 

Blind Information Technology Solutions (BITS)

in partnership with 

Github

are holding a two all-day workshop on 

Github, Visual Studio Code and agentic use.

 

You can find out more here:

 

https://bits-acb.github.io/git-going-with-github/

 

This is open, free and available to all blind and low vision people. No
requirements accept having an interest are assumed. No coding languages will
be

covered other than markdown.

 

Again, please share with your friends and communities.

 

Jeff Bishop

 

_._,_._,_

----------------------------------------------------------------------------
----

 

Groups.io Links:

 

You receive all messages sent to this group. 

 

View/Reply Online (#1131)

| 

Reply to Group

| 

Reply to Sender

| 

Mute This Topic

| 

New Topic

Your Subscription

| 

Contact Group Owner

| 

Unsubscribe

[pmdonahue2 at gmail.com] 

 

_._,_._,_Peter Donahue

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://nfbnet.org/pipermail/nfbcs_nfbnet.org/attachments/20260220/3a7a3bab/attachment.htm>

From hunkinmarvin5 at gmail.com  Fri Feb 20 23:34:37 2026
From: hunkinmarvin5 at gmail.com (hunkinmarvin5 at gmail.com)
Date: Sat, 21 Feb 2026 10:04:37 +1030
Subject: [NFBCS] FW: Petition: Increased Accessibility & Functionality on
 BlindShell Classic 3
In-Reply-To: <020101dca208$ee847b10$cb8d7130$@gmail.com>
References: <01e801dca208$7ca8d630$75fa8290$@gmail.com>
 <020101dca208$ee847b10$cb8d7130$@gmail.com>
Message-ID: <013701dca2c1$7c30e800$7492b800$@gmail.com>

 

 

From: hunkinmarvin5 at gmail.com <hunkinmarvin5 at gmail.com> 
Sent: Friday, 20 February 2026 12:04 PM
To: phonesfortheblind at groups.io
Subject: FW: Petition: Increased Accessibility & Functionality on BlindShell
Classic 3

 

 

 

From: hunkinmarvin5 at gmail.com <mailto:hunkinmarvin5 at gmail.com>
<hunkinmarvin5 at gmail.com <mailto:hunkinmarvin5 at gmail.com> > 
Sent: Friday, 20 February 2026 12:00 PM
To: BlindshellClassic at groups.io <mailto:BlindshellClassic at groups.io> 
Subject: Petition: Increased Accessibility & Functionality on BlindShell
Classic 3

 

 

I'm sharing a link to a petition I created asking for increased
accessibility and functionality on the BlindShell Classic 3.

 

If you feel these improvements would benefit users, please consider signing
and sharing.

https://c.org/m42bGsJgB5

Marvin.

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://nfbnet.org/pipermail/nfbcs_nfbnet.org/attachments/20260221/4861c623/attachment.htm>

From dandrews920 at comcast.net  Sun Feb 22 20:54:13 2026
From: dandrews920 at comcast.net (dandrews920 at comcast.net)
Date: Sun, 22 Feb 2026 14:54:13 -0600
Subject: [NFBCS] From Taylor Arndt: I Got Fed Up With AI Forgetting
 Accessibility, So I Built a Team That Will Not
In-Reply-To: 
 <LV2PR19MB59598ABF816E30CEABF1C5D8EE76A@LV2PR19MB5959.namprd19.prod.outlook.com>
References: 
 <LV2PR19MB59598ABF816E30CEABF1C5D8EE76A@LV2PR19MB5959.namprd19.prod.outlook.com>
Message-ID: <3bec01dca43d$674f68d0$35ee3a70$@comcast.net>

 

Taylor’s Substack - Friday, February 20, 2026 at 8:39 PM


I Got Fed Up With AI Forgetting Accessibility, So I Built a Team That Will Not


  <https://substackcdn.com/image/fetch/$s_!RcQU!,f_auto,q_auto:best,fl_progressive:steep/https%3A%2F%2Ftaylorarndt.substack.com%2Ftwitter%2Fsubscribe-card.jpg%3Fv%3D-888026622%26version%3D9> 

It is Friday night. I had a long day at work coding with Claude, and I am talking to some friends of mine. I have had it.

AI tools do not care about accessibility. And I finally did something about it.

Taylor’s Substack is a reader-supported publication. To receive new posts and support my work, consider becoming a free or paid subscriber.


The Frustration 


I use AI coding tools every day. Claude Code is a core part of how I work. I have written about this before. AI helps me stay organized, keep context, and build things faster than my brain would allow on its own. It is genuinely one of the most important tools in my workflow.

But there is a problem. A big one.

AI tools are terrible at accessibility.

I do not mean they are bad sometimes. I mean they are consistently, reliably, predictably bad at it. Every single time I ask an AI to build a component, I have to fight for the basics. Label your inputs. Trap focus in the modal. Do not use a div when a button exists. Make sure this contrast ratio actually passes. Add a live region so the screen reader knows something changed.

These are not advanced requirements. These are the fundamentals. And AI drops them constantly.


Why This Hits Different for Me 


I am a screen reader user. When AI generates a modal without focus trapping, I am the person who gets stuck. When it skips live regions on search results, I am the person who hears nothing. When it uses a div with an onClick instead of a button, I am the person who cannot activate it with my keyboard.

I am not reviewing accessibility as an abstract checklist. I am living it. Every failure that ships is a wall I personally hit.

And the worst part is that I know better. I am an accessibility specialist. I have the knowledge to catch these issues. But I should not have to catch them every single time. The tools should know this already.


What I Tried First 


I tried the obvious things. I wrote detailed instructions in CLAUDE.md files. I created skills with accessibility rules. I added reminders to my prompts.

None of it stuck.

Skills in Claude Code activate maybe twenty percent of the time without manual intervention. Instructions in context files work at first, but as the conversation grows, they drift. The model deprioritizes them. It decides other things matter more. Accessibility gets quietly dropped from the plan.

That is the pattern. Not malicious. Not intentional. Just gone. Every time.


So I Built a Team 


I stopped trying to remind one model to care about accessibility. Instead, I built six specialized agents, each with a single focused job they cannot ignore.

There is an Accessibility Lead that orchestrates the team and decides which specialists are needed. There is an ARIA Specialist that enforces correct roles, states, and properties. There is a Modal Specialist that owns focus trapping, focus return, and escape behavior. There is a Contrast Master that checks every color combination against WCAG AA ratios. There is a Keyboard Navigator that ensures everything can be reached and operated without a mouse. And there is a Live Region Controller that bridges the gap between visual updates and screen reader awareness.

Each agent has its own context window. Its own system prompt. Its own identity. The ARIA specialist cannot forget about ARIA because ARIA is who it is. The contrast master cannot skip contrast checks because that is its entire purpose.

A hook fires on every prompt I send to Claude Code. If the task involves UI code, the Accessibility Lead activates and coordinates the right specialists. If it does not involve UI, the hook is ignored and Claude works normally.


Why Agents Instead of Everything Else 


I tried skills. They get ignored.

I tried MCP servers. They add tool calls but do not change how the model reasons about code.

I tried detailed instructions. They drift out of context.

Agents are different. They run in their own window with their own rules. The rules are not suggestions. They are the agent’s entire identity. That is the difference. A suggestion can be deprioritized. An identity cannot.


What It Covers 


The team enforces WCAG 2.1 Level AA compliance. That includes screen reader compatibility across VoiceOver, NVDA, and JAWS. Keyboard-only navigation. Focus management for single-page apps, modals, and dynamic content. Color contrast verification with actual ratio calculation. Live region implementation for toasts, search results, loading states, and form feedback. Semantic HTML enforcement. And common framework pitfalls like React conditional rendering breaking live regions and Tailwind color classes failing contrast.

That is a lot. And it should be. Because accessibility is a lot.


It Is Open Source 


I built this for the community. It is free. It is MIT licensed. Anyone using Claude Code can install it in about thirty seconds.

The installer asks if you want it at the project level or globally. It works on macOS, Linux, and Windows. It even has an auto-update system that checks GitHub daily for improvements.

Here is the repo: https://github.com/taylorarndt/a11y-agent-team


This Is a Preview 


I am still testing. I am still refining the agents. I am still finding gaps and fixing them. This is not a finished product announcement. This is a preview. I wanted to share it early because accessibility should not wait for a polished launch.

If you try it and something is missing, open an issue. If a pattern gets overlooked, tell me. If you work with a framework that has specific gotchas, contribute. This is a community project and it will get better with more eyes on it.


Why I Care This Much 


I use assistive technology every day. Accessibility is not a feature I advocate for. It is how I experience the internet. Every inaccessible component is a door that does not open for me. Every missing label is a form I cannot fill out. Every broken modal is a trap I have to escape from.

AI tools should make the web more accessible, not less. They generate code at a speed and scale that humans never could. If that code is inaccessible by default, the problem is not getting smaller. It is getting bigger. Fast.

That is why I built this. Not because it is a cool project. Because I need it. And I am not the only one.

If you want to support this, star the repo and watch it for updates. If you find gaps, open an issue. If you have ideas or framework-specific patterns to add, feel free to contribute. This is a community project. The more people involved, the better it gets.

Here is the repo one more time: https://github.com/taylorarndt/a11y-agent-team

Thank you for reading. More updates coming as the agents improve.

Taylor’s Substack is a reader-supported publication. To receive new posts and support my work, consider becoming a free or paid subscriber.

https://taylorarndt.substack.com/p/i-got-fed-up-with-ai-forgetting-accessibility

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://nfbnet.org/pipermail/nfbcs_nfbnet.org/attachments/20260222/2821c7b7/attachment.htm>

From tyler at tysdomain.com  Sun Feb 22 21:44:10 2026
From: tyler at tysdomain.com (Ty Littlefield)
Date: Sun, 22 Feb 2026 14:44:10 -0700
Subject: [NFBCS] From Taylor Arndt: I Got Fed Up With AI Forgetting
 Accessibility, So I Built a Team That Will Not
In-Reply-To: <3bec01dca43d$674f68d0$35ee3a70$@comcast.net>
References: 
 <LV2PR19MB59598ABF816E30CEABF1C5D8EE76A@LV2PR19MB5959.namprd19.prod.outlook.com>
 <3bec01dca43d$674f68d0$35ee3a70$@comcast.net>
Message-ID: <a4e32c94-207e-4bfb-a5a0-ad1d4268ab8e@tysdomain.com>

This is awesome; thank you for doing it. How much of a difference have 
you found?

My problem does tend to be context windows as you mentioned with the 
drifting, but the secondary issue is that AI was trained on a load of 
horrible data, so it tends to make terrible accessibility decisions. One 
of the more fun vibe-coded accessibility issues I'm stumbling on lately 
is adding aria-haspopup to everything.


*Ty Littlefield (he/him/his)*

  * From Bytes to Bites <https://tysdomain.com>|
  * Linkedin <https://www.linkedin.com/in/ty-lerlittlefield/>

On 2/22/2026 1:54 PM, dandrews920--- via NFBCS wrote:
>
> Taylor’s Substack - Friday, February 20, 2026 at 8:39 PM
>
>
>   I Got Fed Up With AI Forgetting Accessibility, So I Built a Team
>   That Will Not
>
> It is Friday night. I had a long day at work coding with Claude, and I 
> am talking to some friends of mine. I have had it.
>
> AI tools do not care about accessibility. And I finally did something 
> about it.
>
> Taylor’s Substack is a reader-supported publication. To receive new 
> posts and support my work, consider becoming a free or paid subscriber.
>
>
>     The Frustration
>
> I use AI coding tools every day. Claude Code is a core part of how I 
> work. I have written about this before. AI helps me stay organized, 
> keep context, and build things faster than my brain would allow on its 
> own. It is genuinely one of the most important tools in my workflow.
>
> But there is a problem. A big one.
>
> AI tools are terrible at accessibility.
>
> I do not mean they are bad sometimes. I mean they are consistently, 
> reliably, predictably bad at it. Every single time I ask an AI to 
> build a component, I have to fight for the basics. Label your inputs. 
> Trap focus in the modal. Do not use a div when a button exists. Make 
> sure this contrast ratio actually passes. Add a live region so the 
> screen reader knows something changed.
>
> These are not advanced requirements. These are the fundamentals. And 
> AI drops them constantly.
>
>
>     Why This Hits Different for Me
>
> I am a screen reader user. When AI generates a modal without focus 
> trapping, I am the person who gets stuck. When it skips live regions 
> on search results, I am the person who hears nothing. When it uses a 
> div with an onClick instead of a button, I am the person who cannot 
> activate it with my keyboard.
>
> I am not reviewing accessibility as an abstract checklist. I am living 
> it. Every failure that ships is a wall I personally hit.
>
> And the worst part is that I know better. I am an accessibility 
> specialist. I have the knowledge to catch these issues. But I should 
> not have to catch them every single time. The tools should know this 
> already.
>
>
>     What I Tried First
>
> I tried the obvious things. I wrote detailed instructions in CLAUDE.md 
> files. I created skills with accessibility rules. I added reminders to 
> my prompts.
>
> None of it stuck.
>
> Skills in Claude Code activate maybe twenty percent of the time 
> without manual intervention. Instructions in context files work at 
> first, but as the conversation grows, they drift. The model 
> deprioritizes them. It decides other things matter more. Accessibility 
> gets quietly dropped from the plan.
>
> That is the pattern. Not malicious. Not intentional. Just gone. Every 
> time.
>
>
>     So I Built a Team
>
> I stopped trying to remind one model to care about accessibility. 
> Instead, I built six specialized agents, each with a single focused 
> job they cannot ignore.
>
> There is an Accessibility Lead that orchestrates the team and decides 
> which specialists are needed. There is an ARIA Specialist that 
> enforces correct roles, states, and properties. There is a Modal 
> Specialist that owns focus trapping, focus return, and escape 
> behavior. There is a Contrast Master that checks every color 
> combination against WCAG AA ratios. There is a Keyboard Navigator that 
> ensures everything can be reached and operated without a mouse. And 
> there is a Live Region Controller that bridges the gap between visual 
> updates and screen reader awareness.
>
> Each agent has its own context window. Its own system prompt. Its own 
> identity. The ARIA specialist cannot forget about ARIA because ARIA is 
> who it is. The contrast master cannot skip contrast checks because 
> that is its entire purpose.
>
> A hook fires on every prompt I send to Claude Code. If the task 
> involves UI code, the Accessibility Lead activates and coordinates the 
> right specialists. If it does not involve UI, the hook is ignored and 
> Claude works normally.
>
>
>     Why Agents Instead of Everything Else
>
> I tried skills. They get ignored.
>
> I tried MCP servers. They add tool calls but do not change how the 
> model reasons about code.
>
> I tried detailed instructions. They drift out of context.
>
> Agents are different. They run in their own window with their own 
> rules. The rules are not suggestions. They are the agent’s entire 
> identity. That is the difference. A suggestion can be deprioritized. 
> An identity cannot.
>
>
>     What It Covers
>
> The team enforces WCAG 2.1 Level AA compliance. That includes screen 
> reader compatibility across VoiceOver, NVDA, and JAWS. Keyboard-only 
> navigation. Focus management for single-page apps, modals, and dynamic 
> content. Color contrast verification with actual ratio calculation. 
> Live region implementation for toasts, search results, loading states, 
> and form feedback. Semantic HTML enforcement. And common framework 
> pitfalls like React conditional rendering breaking live regions and 
> Tailwind color classes failing contrast.
>
> That is a lot. And it should be. Because accessibility is a lot.
>
>
>     It Is Open Source
>
> I built this for the community. It is free. It is MIT licensed. Anyone 
> using Claude Code can install it in about thirty seconds.
>
> The installer asks if you want it at the project level or globally. It 
> works on macOS, Linux, and Windows. It even has an auto-update system 
> that checks GitHub daily for improvements.
>
> Here is the repo: https://github.com/taylorarndt/a11y-agent-team
>
>
>     This Is a Preview
>
> I am still testing. I am still refining the agents. I am still finding 
> gaps and fixing them. This is not a finished product announcement. 
> This is a preview. I wanted to share it early because accessibility 
> should not wait for a polished launch.
>
> If you try it and something is missing, open an issue. If a pattern 
> gets overlooked, tell me. If you work with a framework that has 
> specific gotchas, contribute. This is a community project and it will 
> get better with more eyes on it.
>
>
>     Why I Care This Much
>
> I use assistive technology every day. Accessibility is not a feature I 
> advocate for. It is how I experience the internet. Every inaccessible 
> component is a door that does not open for me. Every missing label is 
> a form I cannot fill out. Every broken modal is a trap I have to 
> escape from.
>
> AI tools should make the web more accessible, not less. They generate 
> code at a speed and scale that humans never could. If that code is 
> inaccessible by default, the problem is not getting smaller. It is 
> getting bigger. Fast.
>
> That is why I built this. Not because it is a cool project. Because I 
> need it. And I am not the only one.
>
> If you want to support this, star the repo and watch it for updates. 
> If you find gaps, open an issue. If you have ideas or 
> framework-specific patterns to add, feel free to contribute. This is a 
> community project. The more people involved, the better it gets.
>
> Here is the repo one more time: 
> https://github.com/taylorarndt/a11y-agent-team
>
> Thank you for reading. More updates coming as the agents improve.
>
> Taylor’s Substack is a reader-supported publication. To receive new 
> posts and support my work, consider becoming a free or paid subscriber.
>
> https://taylorarndt.substack.com/p/i-got-fed-up-with-ai-forgetting-accessibility
>
>
> _______________________________________________
> NFBCS mailing list
> NFBCS at nfbnet.org
> http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org
> To unsubscribe, change your list options or get your account info for NFBCS:
> http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/tyler%40tysdomain.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://nfbnet.org/pipermail/nfbcs_nfbnet.org/attachments/20260222/dbf9707b/attachment.htm>

From Humberto_Avila.IT104 at outlook.com  Sun Feb 22 22:01:35 2026
From: Humberto_Avila.IT104 at outlook.com (Humberto Avila)
Date: Sun, 22 Feb 2026 22:01:35 +0000
Subject: [NFBCS] From Taylor Arndt: I Got Fed Up With AI Forgetting
 Accessibility, So I Built a Team That Will Not
In-Reply-To: <a4e32c94-207e-4bfb-a5a0-ad1d4268ab8e@tysdomain.com>
References: 
 <LV2PR19MB59598ABF816E30CEABF1C5D8EE76A@LV2PR19MB5959.namprd19.prod.outlook.com>
 <3bec01dca43d$674f68d0$35ee3a70$@comcast.net>
 <a4e32c94-207e-4bfb-a5a0-ad1d4268ab8e@tysdomain.com>
Message-ID: 
 <SA1P220MB103391BA4F6903E5413D8C96E876A@SA1P220MB1033.NAMP220.PROD.OUTLOOK.COM>

Thank you Taylor for sharing this!
I am wondering, will this team of agents be deployed in other AI GPTs other thanClaude?
Do you need a paid Claude account to use Code projects and these different types of agents?
I have been recently getting intofibe-coding myself, just as a hobby. And I really like it, but I run into the same problem from time to time with non-accessible code, and I have to check the stuff manually.

Thanks!
Humberto

[JAWS Certified, 2025]<https://www.freedomscientific.com/Training/Certification>

From: NFBCS <nfbcs-bounces at nfbnet.org> On Behalf Of Ty Littlefield via NFBCS
Sent: Sunday, February 22, 2026 1:44 PM
To: NFB in Computer Science Mailing List <nfbcs at nfbnet.org>
Cc: Ty Littlefield <tyler at tysdomain.com>
Subject: Re: [NFBCS] From Taylor Arndt: I Got Fed Up With AI Forgetting Accessibility, So I Built a Team That Will Not


This is awesome; thank you for doing it. How much of a difference have you found?

My problem does tend to be context windows as you mentioned with the drifting, but the secondary issue is that AI was trained on a load of horrible data, so it tends to make terrible accessibility decisions. One of the more fun vibe-coded accessibility issues I'm stumbling on lately is adding aria-haspopup to everything.



Ty Littlefield (he/him/his)

  *   From Bytes to Bites<https://tysdomain.com>|
  *   Linkedin<https://www.linkedin.com/in/ty-lerlittlefield/>
On 2/22/2026 1:54 PM, dandrews920--- via NFBCS wrote:


Taylor’s Substack - Friday, February 20, 2026 at 8:39 PM

I Got Fed Up With AI Forgetting Accessibility, So I Built a Team That Will Not
[https://substackcdn.com/image/fetch/$s_!RcQU!,f_auto,q_auto:best,fl_progressive:steep/https%3A%2F%2Ftaylorarndt.substack.com%2Ftwitter%2Fsubscribe-card.jpg%3Fv%3D-888026622%26version%3D9]

It is Friday night. I had a long day at work coding with Claude, and I am talking to some friends of mine. I have had it.

AI tools do not care about accessibility. And I finally did something about it.

Taylor’s Substack is a reader-supported publication. To receive new posts and support my work, consider becoming a free or paid subscriber.

The Frustration

I use AI coding tools every day. Claude Code is a core part of how I work. I have written about this before. AI helps me stay organized, keep context, and build things faster than my brain would allow on its own. It is genuinely one of the most important tools in my workflow.

But there is a problem. A big one.

AI tools are terrible at accessibility.

I do not mean they are bad sometimes. I mean they are consistently, reliably, predictably bad at it. Every single time I ask an AI to build a component, I have to fight for the basics. Label your inputs. Trap focus in the modal. Do not use a div when a button exists. Make sure this contrast ratio actually passes. Add a live region so the screen reader knows something changed.

These are not advanced requirements. These are the fundamentals. And AI drops them constantly.

Why This Hits Different for Me

I am a screen reader user. When AI generates a modal without focus trapping, I am the person who gets stuck. When it skips live regions on search results, I am the person who hears nothing. When it uses a div with an onClick instead of a button, I am the person who cannot activate it with my keyboard.

I am not reviewing accessibility as an abstract checklist. I am living it. Every failure that ships is a wall I personally hit.

And the worst part is that I know better. I am an accessibility specialist. I have the knowledge to catch these issues. But I should not have to catch them every single time. The tools should know this already.

What I Tried First

I tried the obvious things. I wrote detailed instructions in CLAUDE.md files. I created skills with accessibility rules. I added reminders to my prompts.

None of it stuck.

Skills in Claude Code activate maybe twenty percent of the time without manual intervention. Instructions in context files work at first, but as the conversation grows, they drift. The model deprioritizes them. It decides other things matter more. Accessibility gets quietly dropped from the plan.

That is the pattern. Not malicious. Not intentional. Just gone. Every time.

So I Built a Team

I stopped trying to remind one model to care about accessibility. Instead, I built six specialized agents, each with a single focused job they cannot ignore.

There is an Accessibility Lead that orchestrates the team and decides which specialists are needed. There is an ARIA Specialist that enforces correct roles, states, and properties. There is a Modal Specialist that owns focus trapping, focus return, and escape behavior. There is a Contrast Master that checks every color combination against WCAG AA ratios. There is a Keyboard Navigator that ensures everything can be reached and operated without a mouse. And there is a Live Region Controller that bridges the gap between visual updates and screen reader awareness.

Each agent has its own context window. Its own system prompt. Its own identity. The ARIA specialist cannot forget about ARIA because ARIA is who it is. The contrast master cannot skip contrast checks because that is its entire purpose.

A hook fires on every prompt I send to Claude Code. If the task involves UI code, the Accessibility Lead activates and coordinates the right specialists. If it does not involve UI, the hook is ignored and Claude works normally.

Why Agents Instead of Everything Else

I tried skills. They get ignored.

I tried MCP servers. They add tool calls but do not change how the model reasons about code.

I tried detailed instructions. They drift out of context.

Agents are different. They run in their own window with their own rules. The rules are not suggestions. They are the agent’s entire identity. That is the difference. A suggestion can be deprioritized. An identity cannot.

What It Covers

The team enforces WCAG 2.1 Level AA compliance. That includes screen reader compatibility across VoiceOver, NVDA, and JAWS. Keyboard-only navigation. Focus management for single-page apps, modals, and dynamic content. Color contrast verification with actual ratio calculation. Live region implementation for toasts, search results, loading states, and form feedback. Semantic HTML enforcement. And common framework pitfalls like React conditional rendering breaking live regions and Tailwind color classes failing contrast.

That is a lot. And it should be. Because accessibility is a lot.

It Is Open Source

I built this for the community. It is free. It is MIT licensed. Anyone using Claude Code can install it in about thirty seconds.

The installer asks if you want it at the project level or globally. It works on macOS, Linux, and Windows. It even has an auto-update system that checks GitHub daily for improvements.

Here is the repo: https://github.com/taylorarndt/a11y-agent-team

This Is a Preview

I am still testing. I am still refining the agents. I am still finding gaps and fixing them. This is not a finished product announcement. This is a preview. I wanted to share it early because accessibility should not wait for a polished launch.

If you try it and something is missing, open an issue. If a pattern gets overlooked, tell me. If you work with a framework that has specific gotchas, contribute. This is a community project and it will get better with more eyes on it.

Why I Care This Much

I use assistive technology every day. Accessibility is not a feature I advocate for. It is how I experience the internet. Every inaccessible component is a door that does not open for me. Every missing label is a form I cannot fill out. Every broken modal is a trap I have to escape from.

AI tools should make the web more accessible, not less. They generate code at a speed and scale that humans never could. If that code is inaccessible by default, the problem is not getting smaller. It is getting bigger. Fast.

That is why I built this. Not because it is a cool project. Because I need it. And I am not the only one.

If you want to support this, star the repo and watch it for updates. If you find gaps, open an issue. If you have ideas or framework-specific patterns to add, feel free to contribute. This is a community project. The more people involved, the better it gets.

Here is the repo one more time: https://github.com/taylorarndt/a11y-agent-team

Thank you for reading. More updates coming as the agents improve.

Taylor’s Substack is a reader-supported publication. To receive new posts and support my work, consider becoming a free or paid subscriber.

https://taylorarndt.substack.com/p/i-got-fed-up-with-ai-forgetting-accessibility





_______________________________________________

NFBCS mailing list

NFBCS at nfbnet.org<mailto:NFBCS at nfbnet.org>

http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org

To unsubscribe, change your list options or get your account info for NFBCS:

http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/tyler%40tysdomain.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://nfbnet.org/pipermail/nfbcs_nfbnet.org/attachments/20260222/09b4bf96/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 8834 bytes
Desc: image001.png
URL: <http://nfbnet.org/pipermail/nfbcs_nfbnet.org/attachments/20260222/09b4bf96/attachment.png>

From tyler at tysdomain.com  Sun Feb 22 23:59:15 2026
From: tyler at tysdomain.com (Ty Littlefield)
Date: Sun, 22 Feb 2026 16:59:15 -0700
Subject: [NFBCS] audible accessibility regressions
Message-ID: <484e9400-8fae-4705-b344-999b500334b0@tysdomain.com>

Hi all,

I'm curious if anyone has connections to anyone who can file these to be 
fixed. Audible has introduced two recent bugs that are horrible for 
accessibility: one where the miniplayer button you can activate to 
expand does not work, and another much more frustrating issue where the 
button to activate a book title in your library is treated as a popup 
button.

This has a hint of "double tap to activate the picker," and reads as 
"button popup button," but there is not a menu presented. This means 
that it's now impossible to download/play books with Voiceover on IOS.


I've reported the issue to Apple, because Voiceover shouldn't hit this 
point and present a blank screen, but I'm also concerned at how many 
issues Audible has introduced in terms of accessibility.


I'd be happy to connect with anyone, or feel free if you know of someone 
to just pass this along if that works better.


Thanks,

-- 

*Ty Littlefield (he/him/his)*

  * From Bytes to Bites <https://tysdomain.com>|
  * Linkedin <https://www.linkedin.com/in/ty-lerlittlefield/>|
  * Github <https://github.com/tlfdev>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://nfbnet.org/pipermail/nfbcs_nfbnet.org/attachments/20260222/8617a028/attachment.htm>

From jmosen at nfb.org  Mon Feb 23 00:24:39 2026
From: jmosen at nfb.org (Mosen, Jonathan)
Date: Mon, 23 Feb 2026 00:24:39 +0000
Subject: [NFBCS] audible accessibility regressions
In-Reply-To: <484e9400-8fae-4705-b344-999b500334b0@tysdomain.com>
References: <484e9400-8fae-4705-b344-999b500334b0@tysdomain.com>
Message-ID: 
 <DS1PR17MB739387679258A2EE6A6B1F9DD477A@DS1PR17MB7393.namprd17.prod.outlook.com>

Hello Ty, yes, CENA is in regular touch with Amazon on a range of issues, some of which are reported to us via the inaccessibility tracker form we offer for the purpose of bug collections.
We did raise the serious regression in the Mini Player after receiving numerous reports, and Amazon fixed it fairly quickly. The update came out a week and a half ago or so. Are you definitely running the latest build?
If you are and you are still experiencing issues, please do let me know and we’ll investigate them so we can pass on good quality data. I am no longer able to duplicate the issue personally after installing the update.

Thanks.

Jonathan Mosen
Executive Director for Accessibility Excellence
National Federation of the Blind
410-659-9314 ex 2233
jmosen at nfb.org<mailto:jmosen at nfb.org>

Reminder: Attend National Convention<https://nfb.org/convention>, July 3-8, 2026, in Austin, Texas.
“It’s the time of year where blind people are the majority.”
[National Federation of the Blind logo, Live the life you want tagline, nfb.org]<https://nfb.org/>

From: NFBCS <nfbcs-bounces at nfbnet.org> On Behalf Of Ty Littlefield via NFBCS
Sent: Sunday, February 22, 2026 6:59 PM
To: NFB in Computer Science Mailing List <nfbcs at nfbnet.org>
Cc: Ty Littlefield <tyler at tysdomain.com>
Subject: [NFBCS] audible accessibility regressions


Hi all,

I'm curious if anyone has connections to anyone who can file these to be fixed. Audible has introduced two recent bugs that are horrible for accessibility: one where the miniplayer button you can activate to expand does not work, and another much more frustrating issue where the button to activate a book title in your library is treated as a popup button.

This has a hint of "double tap to activate the picker," and reads as "button popup button," but there is not a menu presented. This means that it's now impossible to download/play books with Voiceover on IOS.



I've reported the issue to Apple, because Voiceover shouldn't hit this point and present a blank screen, but I'm also concerned at how many issues Audible has introduced in terms of accessibility.



I'd be happy to connect with anyone, or feel free if you know of someone to just pass this along if that works better.



Thanks,
--

Ty Littlefield (he/him/his)

  *   From Bytes to Bites<https://tysdomain.com>|
  *   Linkedin<https://www.linkedin.com/in/ty-lerlittlefield/>|
  *   Github<https://github.com/tlfdev>

Disclaimer

The information contained in this communication from the sender is confidential. It is intended solely for use by the recipient and others authorized to receive it. If you are not the recipient, you are hereby notified that any disclosure, copying, distribution or taking action in relation of the contents of this information is strictly prohibited and may be unlawful.

This email has been scanned for viruses and malware, and may have been automatically archived by Mimecast Ltd, an innovator in Software as a Service (SaaS) for business. Providing a safer and more useful place for your human generated data. Specializing in; Security, archiving and compliance. To find out more visit the Mimecast website.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://nfbnet.org/pipermail/nfbcs_nfbnet.org/attachments/20260223/6da5ba2b/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 49649 bytes
Desc: image001.jpg
URL: <http://nfbnet.org/pipermail/nfbcs_nfbnet.org/attachments/20260223/6da5ba2b/attachment.jpg>

From jbar at barcore.com  Mon Feb 23 00:30:03 2026
From: jbar at barcore.com (Jim Barbour)
Date: Sun, 22 Feb 2026 18:30:03 -0600
Subject: [NFBCS] audible accessibility regressions
In-Reply-To: <484e9400-8fae-4705-b344-999b500334b0@tysdomain.com>
References: <484e9400-8fae-4705-b344-999b500334b0@tysdomain.com>
Message-ID: <3D99171C-6A69-4B34-AF9F-294EB6BE8024@barcore.com>

An HTML attachment was scrubbed...
URL: <http://nfbnet.org/pipermail/nfbcs_nfbnet.org/attachments/20260222/5b1e63b5/attachment.htm>

From dandrews920 at comcast.net  Mon Feb 23 01:04:17 2026
From: dandrews920 at comcast.net (dandrews920 at comcast.net)
Date: Sun, 22 Feb 2026 19:04:17 -0600
Subject: [NFBCS] From Taylor Arndt: I Got Fed Up With AI Forgetting
 Accessibility, So I Built a Team That Will Not
In-Reply-To: 
 <SA1P220MB103391BA4F6903E5413D8C96E876A@SA1P220MB1033.NAMP220.PROD.OUTLOOK.COM>
References: 
 <LV2PR19MB59598ABF816E30CEABF1C5D8EE76A@LV2PR19MB5959.namprd19.prod.outlook.com>
 <3bec01dca43d$674f68d0$35ee3a70$@comcast.net>
 <a4e32c94-207e-4bfb-a5a0-ad1d4268ab8e@tysdomain.com>
  <SA1P220MB103391BA4F6903E5413D8C96E876A@SA1P220MB1033.NAMP220.PROD.OUTLOOK.COM>
Message-ID: <06cd01dca460$5668d9c0$033a8d40$@comcast.net>

He is not necessarily on this list – as I forwarded the message.

 

Dave

 

 

 

From: NFBCS <nfbcs-bounces at nfbnet.org> On Behalf Of Humberto Avila via NFBCS
Sent: Sunday, February 22, 2026 4:02 PM
To: NFB in Computer Science Mailing List <nfbcs at nfbnet.org>
Cc: Humberto Avila <Humberto_Avila.IT104 at outlook.com>
Subject: Re: [NFBCS] From Taylor Arndt: I Got Fed Up With AI Forgetting Accessibility, So I Built a Team That Will Not

 

Thank you Taylor for sharing this! 

I am wondering, will this team of agents be deployed in other AI GPTs other thanClaude? 

Do you need a paid Claude account to use Code projects and these different types of agents? 

I have been recently getting intofibe-coding myself, just as a hobby. And I really like it, but I run into the same problem from time to time with non-accessible code, and I have to check the stuff manually. 

 

Thanks! 

Humberto

 

 

 <https://www.freedomscientific.com/Training/Certification> 

 

From: NFBCS <nfbcs-bounces at nfbnet.org <mailto:nfbcs-bounces at nfbnet.org> > On Behalf Of Ty Littlefield via NFBCS
Sent: Sunday, February 22, 2026 1:44 PM
To: NFB in Computer Science Mailing List <nfbcs at nfbnet.org <mailto:nfbcs at nfbnet.org> >
Cc: Ty Littlefield <tyler at tysdomain.com <mailto:tyler at tysdomain.com> >
Subject: Re: [NFBCS] From Taylor Arndt: I Got Fed Up With AI Forgetting Accessibility, So I Built a Team That Will Not

 

This is awesome; thank you for doing it. How much of a difference have you found?

My problem does tend to be context windows as you mentioned with the drifting, but the secondary issue is that AI was trained on a load of horrible data, so it tends to make terrible accessibility decisions. One of the more fun vibe-coded accessibility issues I'm stumbling on lately is adding aria-haspopup to everything.

 

Ty Littlefield (he/him/his)

*	From Bytes to Bites <https://tysdomain.com> | 
*	Linkedin <https://www.linkedin.com/in/ty-lerlittlefield/> 

On 2/22/2026 1:54 PM, dandrews920--- via NFBCS wrote:

 

Taylor’s Substack - Friday, February 20, 2026 at 8:39 PM


I Got Fed Up With AI Forgetting Accessibility, So I Built a Team That Will Not


  <https://substackcdn.com/image/fetch/$s_!RcQU!,f_auto,q_auto:best,fl_progressive:steep/https%3A%2F%2Ftaylorarndt.substack.com%2Ftwitter%2Fsubscribe-card.jpg%3Fv%3D-888026622%26version%3D9> 

It is Friday night. I had a long day at work coding with Claude, and I am talking to some friends of mine. I have had it.

AI tools do not care about accessibility. And I finally did something about it.

Taylor’s Substack is a reader-supported publication. To receive new posts and support my work, consider becoming a free or paid subscriber.


The Frustration 


I use AI coding tools every day. Claude Code is a core part of how I work. I have written about this before. AI helps me stay organized, keep context, and build things faster than my brain would allow on its own. It is genuinely one of the most important tools in my workflow.

But there is a problem. A big one.

AI tools are terrible at accessibility.

I do not mean they are bad sometimes. I mean they are consistently, reliably, predictably bad at it. Every single time I ask an AI to build a component, I have to fight for the basics. Label your inputs. Trap focus in the modal. Do not use a div when a button exists. Make sure this contrast ratio actually passes. Add a live region so the screen reader knows something changed.

These are not advanced requirements. These are the fundamentals. And AI drops them constantly.


Why This Hits Different for Me 


I am a screen reader user. When AI generates a modal without focus trapping, I am the person who gets stuck. When it skips live regions on search results, I am the person who hears nothing. When it uses a div with an onClick instead of a button, I am the person who cannot activate it with my keyboard.

I am not reviewing accessibility as an abstract checklist. I am living it. Every failure that ships is a wall I personally hit.

And the worst part is that I know better. I am an accessibility specialist. I have the knowledge to catch these issues. But I should not have to catch them every single time. The tools should know this already.


What I Tried First 


I tried the obvious things. I wrote detailed instructions in CLAUDE.md files. I created skills with accessibility rules. I added reminders to my prompts.

None of it stuck.

Skills in Claude Code activate maybe twenty percent of the time without manual intervention. Instructions in context files work at first, but as the conversation grows, they drift. The model deprioritizes them. It decides other things matter more. Accessibility gets quietly dropped from the plan.

That is the pattern. Not malicious. Not intentional. Just gone. Every time.


So I Built a Team 


I stopped trying to remind one model to care about accessibility. Instead, I built six specialized agents, each with a single focused job they cannot ignore.

There is an Accessibility Lead that orchestrates the team and decides which specialists are needed. There is an ARIA Specialist that enforces correct roles, states, and properties. There is a Modal Specialist that owns focus trapping, focus return, and escape behavior. There is a Contrast Master that checks every color combination against WCAG AA ratios. There is a Keyboard Navigator that ensures everything can be reached and operated without a mouse. And there is a Live Region Controller that bridges the gap between visual updates and screen reader awareness.

Each agent has its own context window. Its own system prompt. Its own identity. The ARIA specialist cannot forget about ARIA because ARIA is who it is. The contrast master cannot skip contrast checks because that is its entire purpose.

A hook fires on every prompt I send to Claude Code. If the task involves UI code, the Accessibility Lead activates and coordinates the right specialists. If it does not involve UI, the hook is ignored and Claude works normally.


Why Agents Instead of Everything Else 


I tried skills. They get ignored.

I tried MCP servers. They add tool calls but do not change how the model reasons about code.

I tried detailed instructions. They drift out of context.

Agents are different. They run in their own window with their own rules. The rules are not suggestions. They are the agent’s entire identity. That is the difference. A suggestion can be deprioritized. An identity cannot.


What It Covers 


The team enforces WCAG 2.1 Level AA compliance. That includes screen reader compatibility across VoiceOver, NVDA, and JAWS. Keyboard-only navigation. Focus management for single-page apps, modals, and dynamic content. Color contrast verification with actual ratio calculation. Live region implementation for toasts, search results, loading states, and form feedback. Semantic HTML enforcement. And common framework pitfalls like React conditional rendering breaking live regions and Tailwind color classes failing contrast.

That is a lot. And it should be. Because accessibility is a lot.


It Is Open Source 


I built this for the community. It is free. It is MIT licensed. Anyone using Claude Code can install it in about thirty seconds.

The installer asks if you want it at the project level or globally. It works on macOS, Linux, and Windows. It even has an auto-update system that checks GitHub daily for improvements.

Here is the repo: https://github.com/taylorarndt/a11y-agent-team


This Is a Preview 


I am still testing. I am still refining the agents. I am still finding gaps and fixing them. This is not a finished product announcement. This is a preview. I wanted to share it early because accessibility should not wait for a polished launch.

If you try it and something is missing, open an issue. If a pattern gets overlooked, tell me. If you work with a framework that has specific gotchas, contribute. This is a community project and it will get better with more eyes on it.


Why I Care This Much 


I use assistive technology every day. Accessibility is not a feature I advocate for. It is how I experience the internet. Every inaccessible component is a door that does not open for me. Every missing label is a form I cannot fill out. Every broken modal is a trap I have to escape from.

AI tools should make the web more accessible, not less. They generate code at a speed and scale that humans never could. If that code is inaccessible by default, the problem is not getting smaller. It is getting bigger. Fast.

That is why I built this. Not because it is a cool project. Because I need it. And I am not the only one.

If you want to support this, star the repo and watch it for updates. If you find gaps, open an issue. If you have ideas or framework-specific patterns to add, feel free to contribute. This is a community project. The more people involved, the better it gets.

Here is the repo one more time: https://github.com/taylorarndt/a11y-agent-team

Thank you for reading. More updates coming as the agents improve.

Taylor’s Substack is a reader-supported publication. To receive new posts and support my work, consider becoming a free or paid subscriber.

https://taylorarndt.substack.com/p/i-got-fed-up-with-ai-forgetting-accessibility

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://nfbnet.org/pipermail/nfbcs_nfbnet.org/attachments/20260222/73b9b513/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 8834 bytes
Desc: not available
URL: <http://nfbnet.org/pipermail/nfbcs_nfbnet.org/attachments/20260222/73b9b513/attachment-0001.png>

From tyler at tysdomain.com  Mon Feb 23 01:06:02 2026
From: tyler at tysdomain.com (Ty Littlefield)
Date: Sun, 22 Feb 2026 18:06:02 -0700
Subject: [NFBCS] audible accessibility regressions
In-Reply-To: 
 <DS1PR17MB739387679258A2EE6A6B1F9DD477A@DS1PR17MB7393.namprd17.prod.outlook.com>
References: <484e9400-8fae-4705-b344-999b500334b0@tysdomain.com>
 <DS1PR17MB739387679258A2EE6A6B1F9DD477A@DS1PR17MB7393.namprd17.prod.outlook.com>
Message-ID: <91dddcb3-6fc0-4b14-9269-72bbabb141c8@tysdomain.com>

Hello,

I'm glad that people are on these issues. I can not test to verify the 
miniplayer issues.

I am on IOS 26.3 (not beta) and running Audible 4.64 with no updates to 
be installed.

If I navigate to my library tab, all of the books that can be played or 
downloaded that are previously given a button role still have the button 
role, but they also say "has popup button." after the button role is 
announced.

Activating any of these either does nothing, in the case of being able 
to play, or gives me a blank screen. Dragging my finger around the 
screen to explore receives no feedback. The only way I've found to get 
controls back is to close Audible in the app switcher, then open it 
again. Turning Voiceover off and back on again does not help.


Thanks,


*Ty Littlefield (he/him/his)*

  * From Bytes to Bites <https://tysdomain.com>|
  * Linkedin <https://www.linkedin.com/in/ty-lerlittlefield/>|
  * Github <https://github.com/tlfdev>

On 2/22/2026 5:24 PM, Mosen, Jonathan via NFBCS wrote:
>
> Hello Ty, yes, CENA is in regular touch with Amazon on a range of 
> issues, some of which are reported to us via the inaccessibility 
> tracker form we offer for the purpose of bug collections.
>
> We did raise the serious regression in the Mini Player after receiving 
> numerous reports, and Amazon fixed it fairly quickly. The update came 
> out a week and a half ago or so. Are you definitely running the latest 
> build?
>
> If you are and you are still experiencing issues, please do let me 
> know and we’ll investigate them so we can pass on good quality data. I 
> am no longer able to duplicate the issue personally after installing 
> the update.
>
> Thanks.
>
> Jonathan Mosen
> Executive Director for Accessibility Excellence
> National Federation of the Blind
> 410-659-9314 ex 2233
> jmosen at nfb.org <mailto:jmosen at nfb.org>
>
>
> Reminder: Attend National Convention 
> <https://nfb.org/convention>, July 3-8, 2026, in Austin, Texas.
> “It’s the time of year where blind people are the majority.”
>
> National Federation of the Blind logo, Live the life you want tagline, 
> nfb.org <https://nfb.org/>
>
> *From:*NFBCS <nfbcs-bounces at nfbnet.org> *On Behalf Of *Ty Littlefield 
> via NFBCS
> *Sent:* Sunday, February 22, 2026 6:59 PM
> *To:* NFB in Computer Science Mailing List <nfbcs at nfbnet.org>
> *Cc:* Ty Littlefield <tyler at tysdomain.com>
> *Subject:* [NFBCS] audible accessibility regressions
>
> Hi all,
>
> I'm curious if anyone has connections to anyone who can file these to 
> be fixed. Audible has introduced two recent bugs that are horrible for 
> accessibility: one where the miniplayer button you can activate to 
> expand does not work, and another much more frustrating issue where 
> the button to activate a book title in your library is treated as a 
> popup button.
>
> This has a hint of "double tap to activate the picker," and reads as 
> "button popup button," but there is not a menu presented. This means 
> that it's now impossible to download/play books with Voiceover on IOS.
>
> I've reported the issue to Apple, because Voiceover shouldn't hit this 
> point and present a blank screen, but I'm also concerned at how many 
> issues Audible has introduced in terms of accessibility.
>
> I'd be happy to connect with anyone, or feel free if you know of 
> someone to just pass this along if that works better.
>
> Thanks,
>
> -- 
>
> *Ty Littlefield (he/him/his)*
>
>   * From Bytes to Bites <https://tysdomain.com>|
>   * Linkedin <https://www.linkedin.com/in/ty-lerlittlefield/>|
>   * Github <https://github.com/tlfdev>
>
>
> _______________________________________________
> NFBCS mailing list
> NFBCS at nfbnet.org
> http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org
> To unsubscribe, change your list options or get your account info for NFBCS:
> http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/tyler%40tysdomain.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://nfbnet.org/pipermail/nfbcs_nfbnet.org/attachments/20260222/33b87f4e/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 49649 bytes
Desc: not available
URL: <http://nfbnet.org/pipermail/nfbcs_nfbnet.org/attachments/20260222/33b87f4e/attachment.jpg>

From taylorarndt99 at gmail.com  Mon Feb 23 01:07:31 2026
From: taylorarndt99 at gmail.com (Taylor Arndt)
Date: Sun, 22 Feb 2026 19:07:31 -0600
Subject: [NFBCS] From Taylor Arndt: I Got Fed Up With AI Forgetting
 Accessibility, So I Built a Team That Will Not
In-Reply-To: <06cd01dca460$5668d9c0$033a8d40$@comcast.net>
References: 
 <LV2PR19MB59598ABF816E30CEABF1C5D8EE76A@LV2PR19MB5959.namprd19.prod.outlook.com>
 <3bec01dca43d$674f68d0$35ee3a70$@comcast.net>
 <a4e32c94-207e-4bfb-a5a0-ad1d4268ab8e@tysdomain.com>
 <SA1P220MB103391BA4F6903E5413D8C96E876A@SA1P220MB1033.NAMP220.PROD.OUTLOOK.COM>
 <06cd01dca460$5668d9c0$033a8d40$@comcast.net>
Message-ID: 
 <CAFsrCh1jQ61Ey4OPBpCxqzoCcQcW7T_mwD74K5FnPfVo=o9=4w@mail.gmail.com>

I’m actually on this list and yes, we’ve got a big announcement and it’s
coming to GitHub  copilot

Taylor





On Sun, Feb 22, 2026 at 7:05 PM dandrews920--- via NFBCS <nfbcs at nfbnet.org>
wrote:

> He is not necessarily on this list – as I forwarded the message.
>
>
>
> Dave
>
>
>
>
>
>
>
> *From:* NFBCS <nfbcs-bounces at nfbnet.org> *On Behalf Of *Humberto Avila
> via NFBCS
> *Sent:* Sunday, February 22, 2026 4:02 PM
> *To:* NFB in Computer Science Mailing List <nfbcs at nfbnet.org>
> *Cc:* Humberto Avila <Humberto_Avila.IT104 at outlook.com>
> *Subject:* Re: [NFBCS] From Taylor Arndt: I Got Fed Up With AI Forgetting
> Accessibility, So I Built a Team That Will Not
>
>
>
> Thank you Taylor for sharing this!
>
> I am wondering, will this team of agents be deployed in other AI GPTs
> other thanClaude?
>
> Do you need a paid Claude account to use Code projects and these different
> types of agents?
>
> I have been recently getting intofibe-coding myself, just as a hobby. And
> I really like it, but I run into the same problem from time to time with
> non-accessible code, and I have to check the stuff manually.
>
>
>
> Thanks!
>
> Humberto
>
>
>
>
>
> [image: JAWS Certified, 2025]
> <https://www.freedomscientific.com/Training/Certification>
>
>
>
> *From:* NFBCS <nfbcs-bounces at nfbnet.org> *On Behalf Of *Ty Littlefield
> via NFBCS
> *Sent:* Sunday, February 22, 2026 1:44 PM
> *To:* NFB in Computer Science Mailing List <nfbcs at nfbnet.org>
> *Cc:* Ty Littlefield <tyler at tysdomain.com>
> *Subject:* Re: [NFBCS] From Taylor Arndt: I Got Fed Up With AI Forgetting
> Accessibility, So I Built a Team That Will Not
>
>
>
> This is awesome; thank you for doing it. How much of a difference have you
> found?
>
> My problem does tend to be context windows as you mentioned with the
> drifting, but the secondary issue is that AI was trained on a load of
> horrible data, so it tends to make terrible accessibility decisions. One of
> the more fun vibe-coded accessibility issues I'm stumbling on lately is
> adding aria-haspopup to everything.
>
>
>
> *Ty Littlefield (he/him/his)*
>
>    - From Bytes to Bites <https://tysdomain.com>|
>    - Linkedin <https://www.linkedin.com/in/ty-lerlittlefield/>
>
> On 2/22/2026 1:54 PM, dandrews920--- via NFBCS wrote:
>
>
>
> Taylor’s Substack - Friday, February 20, 2026 at 8:39 PM
> I Got Fed Up With AI Forgetting Accessibility, So I Built a Team That Will
> Not
>
> It is Friday night. I had a long day at work coding with Claude, and I am
> talking to some friends of mine. I have had it.
>
> AI tools do not care about accessibility. And I finally did something
> about it.
>
> Taylor’s Substack is a reader-supported publication. To receive new posts
> and support my work, consider becoming a free or paid subscriber.
> The Frustration
>
> I use AI coding tools every day. Claude Code is a core part of how I work.
> I have written about this before. AI helps me stay organized, keep context,
> and build things faster than my brain would allow on its own. It is
> genuinely one of the most important tools in my workflow.
>
> But there is a problem. A big one.
>
> AI tools are terrible at accessibility.
>
> I do not mean they are bad sometimes. I mean they are consistently,
> reliably, predictably bad at it. Every single time I ask an AI to build a
> component, I have to fight for the basics. Label your inputs. Trap focus in
> the modal. Do not use a div when a button exists. Make sure this contrast
> ratio actually passes. Add a live region so the screen reader knows
> something changed.
>
> These are not advanced requirements. These are the fundamentals. And AI
> drops them constantly.
> Why This Hits Different for Me
>
> I am a screen reader user. When AI generates a modal without focus
> trapping, I am the person who gets stuck. When it skips live regions on
> search results, I am the person who hears nothing. When it uses a div with
> an onClick instead of a button, I am the person who cannot activate it with
> my keyboard.
>
> I am not reviewing accessibility as an abstract checklist. I am living it.
> Every failure that ships is a wall I personally hit.
>
> And the worst part is that I know better. I am an accessibility
> specialist. I have the knowledge to catch these issues. But I should not
> have to catch them every single time. The tools should know this already.
> What I Tried First
>
> I tried the obvious things. I wrote detailed instructions in CLAUDE.md
> files. I created skills with accessibility rules. I added reminders to my
> prompts.
>
> None of it stuck.
>
> Skills in Claude Code activate maybe twenty percent of the time without
> manual intervention. Instructions in context files work at first, but as
> the conversation grows, they drift. The model deprioritizes them. It
> decides other things matter more. Accessibility gets quietly dropped from
> the plan.
>
> That is the pattern. Not malicious. Not intentional. Just gone. Every time.
> So I Built a Team
>
> I stopped trying to remind one model to care about accessibility. Instead,
> I built six specialized agents, each with a single focused job they cannot
> ignore.
>
> There is an Accessibility Lead that orchestrates the team and decides
> which specialists are needed. There is an ARIA Specialist that enforces
> correct roles, states, and properties. There is a Modal Specialist that
> owns focus trapping, focus return, and escape behavior. There is a Contrast
> Master that checks every color combination against WCAG AA ratios. There is
> a Keyboard Navigator that ensures everything can be reached and operated
> without a mouse. And there is a Live Region Controller that bridges the gap
> between visual updates and screen reader awareness.
>
> Each agent has its own context window. Its own system prompt. Its own
> identity. The ARIA specialist cannot forget about ARIA because ARIA is who
> it is. The contrast master cannot skip contrast checks because that is its
> entire purpose.
>
> A hook fires on every prompt I send to Claude Code. If the task involves
> UI code, the Accessibility Lead activates and coordinates the right
> specialists. If it does not involve UI, the hook is ignored and Claude
> works normally.
> Why Agents Instead of Everything Else
>
> I tried skills. They get ignored.
>
> I tried MCP servers. They add tool calls but do not change how the model
> reasons about code.
>
> I tried detailed instructions. They drift out of context.
>
> Agents are different. They run in their own window with their own rules.
> The rules are not suggestions. They are the agent’s entire identity. That
> is the difference. A suggestion can be deprioritized. An identity cannot.
> What It Covers
>
> The team enforces WCAG 2.1 Level AA compliance. That includes screen
> reader compatibility across VoiceOver, NVDA, and JAWS. Keyboard-only
> navigation. Focus management for single-page apps, modals, and dynamic
> content. Color contrast verification with actual ratio calculation. Live
> region implementation for toasts, search results, loading states, and form
> feedback. Semantic HTML enforcement. And common framework pitfalls like
> React conditional rendering breaking live regions and Tailwind color
> classes failing contrast.
>
> That is a lot. And it should be. Because accessibility is a lot.
> It Is Open Source
>
> I built this for the community. It is free. It is MIT licensed. Anyone
> using Claude Code can install it in about thirty seconds.
>
> The installer asks if you want it at the project level or globally. It
> works on macOS, Linux, and Windows. It even has an auto-update system that
> checks GitHub daily for improvements.
>
> Here is the repo: https://github.com/taylorarndt/a11y-agent-team
> This Is a Preview
>
> I am still testing. I am still refining the agents. I am still finding
> gaps and fixing them. This is not a finished product announcement. This is
> a preview. I wanted to share it early because accessibility should not wait
> for a polished launch.
>
> If you try it and something is missing, open an issue. If a pattern gets
> overlooked, tell me. If you work with a framework that has specific
> gotchas, contribute. This is a community project and it will get better
> with more eyes on it.
> Why I Care This Much
>
> I use assistive technology every day. Accessibility is not a feature I
> advocate for. It is how I experience the internet. Every inaccessible
> component is a door that does not open for me. Every missing label is a
> form I cannot fill out. Every broken modal is a trap I have to escape from.
>
> AI tools should make the web more accessible, not less. They generate code
> at a speed and scale that humans never could. If that code is inaccessible
> by default, the problem is not getting smaller. It is getting bigger. Fast.
>
> That is why I built this. Not because it is a cool project. Because I need
> it. And I am not the only one.
>
> If you want to support this, star the repo and watch it for updates. If
> you find gaps, open an issue. If you have ideas or framework-specific
> patterns to add, feel free to contribute. This is a community project. The
> more people involved, the better it gets.
>
> Here is the repo one more time:
> https://github.com/taylorarndt/a11y-agent-team
>
> Thank you for reading. More updates coming as the agents improve.
>
> Taylor’s Substack is a reader-supported publication. To receive new posts
> and support my work, consider becoming a free or paid subscriber.
>
>
> https://taylorarndt.substack.com/p/i-got-fed-up-with-ai-forgetting-accessibility
>
>
>
> _______________________________________________
> NFBCS mailing list
> NFBCS at nfbnet.org
> http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org
> To unsubscribe, change your list options or get your account info for
> NFBCS:
>
> http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/taylorarndt99%40gmail.com
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://nfbnet.org/pipermail/nfbcs_nfbnet.org/attachments/20260222/e94cdc10/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 8834 bytes
Desc: not available
URL: <http://nfbnet.org/pipermail/nfbcs_nfbnet.org/attachments/20260222/e94cdc10/attachment.png>

From pdonahue2 at satx.rr.com  Mon Feb 23 01:09:43 2026
From: pdonahue2 at satx.rr.com (Peter)
Date: Sun, 22 Feb 2026 19:09:43 -0600
Subject: [NFBCS] From Taylor Arndt: I Got Fed Up With AI Forgetting
 Accessibility, So I Built a Team That Will Not
In-Reply-To: <06cd01dca460$5668d9c0$033a8d40$@comcast.net>
References: 
 <LV2PR19MB59598ABF816E30CEABF1C5D8EE76A@LV2PR19MB5959.namprd19.prod.outlook.com>
 <3bec01dca43d$674f68d0$35ee3a70$@comcast.net>
 <a4e32c94-207e-4bfb-a5a0-ad1d4268ab8e@tysdomain.com>
  <SA1P220MB103391BA4F6903E5413D8C96E876A@SA1P220MB1033.NAMP220.PROD.OUTLOOK.COM>
 <06cd01dca460$5668d9c0$033a8d40$@comcast.net>
Message-ID: <01c601dca461$1825b6a0$487123e0$@satx.rr.com>

Hello David and everyone,

 

Taylor is a girl not a guy

 

Peter Donahue

 

.

 

From: NFBCS <nfbcs-bounces at nfbnet.org> On Behalf Of dandrews920--- via NFBCS
Sent: Sunday, February 22, 2026 7:04 PM
To: 'NFB in Computer Science Mailing List' <nfbcs at nfbnet.org>
Cc: dandrews920 at comcast.net
Subject: Re: [NFBCS] From Taylor Arndt: I Got Fed Up With AI Forgetting Accessibility, So I Built a Team That Will Not

 

He is not necessarily on this list – as I forwarded the message.

 

Dave

 

 

 

From: NFBCS <nfbcs-bounces at nfbnet.org <mailto:nfbcs-bounces at nfbnet.org> > On Behalf Of Humberto Avila via NFBCS
Sent: Sunday, February 22, 2026 4:02 PM
To: NFB in Computer Science Mailing List <nfbcs at nfbnet.org <mailto:nfbcs at nfbnet.org> >
Cc: Humberto Avila <Humberto_Avila.IT104 at outlook.com <mailto:Humberto_Avila.IT104 at outlook.com> >
Subject: Re: [NFBCS] From Taylor Arndt: I Got Fed Up With AI Forgetting Accessibility, So I Built a Team That Will Not

 

Thank you Taylor for sharing this! 

I am wondering, will this team of agents be deployed in other AI GPTs other thanClaude? 

Do you need a paid Claude account to use Code projects and these different types of agents? 

I have been recently getting intofibe-coding myself, just as a hobby. And I really like it, but I run into the same problem from time to time with non-accessible code, and I have to check the stuff manually. 

 

Thanks! 

Humberto

 

 

 <https://www.freedomscientific.com/Training/Certification> 

 

From: NFBCS <nfbcs-bounces at nfbnet.org <mailto:nfbcs-bounces at nfbnet.org> > On Behalf Of Ty Littlefield via NFBCS
Sent: Sunday, February 22, 2026 1:44 PM
To: NFB in Computer Science Mailing List <nfbcs at nfbnet.org <mailto:nfbcs at nfbnet.org> >
Cc: Ty Littlefield <tyler at tysdomain.com <mailto:tyler at tysdomain.com> >
Subject: Re: [NFBCS] From Taylor Arndt: I Got Fed Up With AI Forgetting Accessibility, So I Built a Team That Will Not

 

This is awesome; thank you for doing it. How much of a difference have you found?

My problem does tend to be context windows as you mentioned with the drifting, but the secondary issue is that AI was trained on a load of horrible data, so it tends to make terrible accessibility decisions. One of the more fun vibe-coded accessibility issues I'm stumbling on lately is adding aria-haspopup to everything.

 

Ty Littlefield (he/him/his)

*	From Bytes to Bites <https://tysdomain.com> | 
*	Linkedin <https://www.linkedin.com/in/ty-lerlittlefield/> 

On 2/22/2026 1:54 PM, dandrews920--- via NFBCS wrote:

 

Taylor’s Substack - Friday, February 20, 2026 at 8:39 PM


I Got Fed Up With AI Forgetting Accessibility, So I Built a Team That Will Not


  <https://substackcdn.com/image/fetch/$s_!RcQU!,f_auto,q_auto:best,fl_progressive:steep/https%3A%2F%2Ftaylorarndt.substack.com%2Ftwitter%2Fsubscribe-card.jpg%3Fv%3D-888026622%26version%3D9> 

It is Friday night. I had a long day at work coding with Claude, and I am talking to some friends of mine. I have had it.

AI tools do not care about accessibility. And I finally did something about it.

Taylor’s Substack is a reader-supported publication. To receive new posts and support my work, consider becoming a free or paid subscriber.


The Frustration 


I use AI coding tools every day. Claude Code is a core part of how I work. I have written about this before. AI helps me stay organized, keep context, and build things faster than my brain would allow on its own. It is genuinely one of the most important tools in my workflow.

But there is a problem. A big one.

AI tools are terrible at accessibility.

I do not mean they are bad sometimes. I mean they are consistently, reliably, predictably bad at it. Every single time I ask an AI to build a component, I have to fight for the basics. Label your inputs. Trap focus in the modal. Do not use a div when a button exists. Make sure this contrast ratio actually passes. Add a live region so the screen reader knows something changed.

These are not advanced requirements. These are the fundamentals. And AI drops them constantly.


Why This Hits Different for Me 


I am a screen reader user. When AI generates a modal without focus trapping, I am the person who gets stuck. When it skips live regions on search results, I am the person who hears nothing. When it uses a div with an onClick instead of a button, I am the person who cannot activate it with my keyboard.

I am not reviewing accessibility as an abstract checklist. I am living it. Every failure that ships is a wall I personally hit.

And the worst part is that I know better. I am an accessibility specialist. I have the knowledge to catch these issues. But I should not have to catch them every single time. The tools should know this already.


What I Tried First 


I tried the obvious things. I wrote detailed instructions in CLAUDE.md files. I created skills with accessibility rules. I added reminders to my prompts.

None of it stuck.

Skills in Claude Code activate maybe twenty percent of the time without manual intervention. Instructions in context files work at first, but as the conversation grows, they drift. The model deprioritizes them. It decides other things matter more. Accessibility gets quietly dropped from the plan.

That is the pattern. Not malicious. Not intentional. Just gone. Every time.


So I Built a Team 


I stopped trying to remind one model to care about accessibility. Instead, I built six specialized agents, each with a single focused job they cannot ignore.

There is an Accessibility Lead that orchestrates the team and decides which specialists are needed. There is an ARIA Specialist that enforces correct roles, states, and properties. There is a Modal Specialist that owns focus trapping, focus return, and escape behavior. There is a Contrast Master that checks every color combination against WCAG AA ratios. There is a Keyboard Navigator that ensures everything can be reached and operated without a mouse. And there is a Live Region Controller that bridges the gap between visual updates and screen reader awareness.

Each agent has its own context window. Its own system prompt. Its own identity. The ARIA specialist cannot forget about ARIA because ARIA is who it is. The contrast master cannot skip contrast checks because that is its entire purpose.

A hook fires on every prompt I send to Claude Code. If the task involves UI code, the Accessibility Lead activates and coordinates the right specialists. If it does not involve UI, the hook is ignored and Claude works normally.


Why Agents Instead of Everything Else 


I tried skills. They get ignored.

I tried MCP servers. They add tool calls but do not change how the model reasons about code.

I tried detailed instructions. They drift out of context.

Agents are different. They run in their own window with their own rules. The rules are not suggestions. They are the agent’s entire identity. That is the difference. A suggestion can be deprioritized. An identity cannot.


What It Covers 


The team enforces WCAG 2.1 Level AA compliance. That includes screen reader compatibility across VoiceOver, NVDA, and JAWS. Keyboard-only navigation. Focus management for single-page apps, modals, and dynamic content. Color contrast verification with actual ratio calculation. Live region implementation for toasts, search results, loading states, and form feedback. Semantic HTML enforcement. And common framework pitfalls like React conditional rendering breaking live regions and Tailwind color classes failing contrast.

That is a lot. And it should be. Because accessibility is a lot.


It Is Open Source 


I built this for the community. It is free. It is MIT licensed. Anyone using Claude Code can install it in about thirty seconds.

The installer asks if you want it at the project level or globally. It works on macOS, Linux, and Windows. It even has an auto-update system that checks GitHub daily for improvements.

Here is the repo: https://github.com/taylorarndt/a11y-agent-team


This Is a Preview 


I am still testing. I am still refining the agents. I am still finding gaps and fixing them. This is not a finished product announcement. This is a preview. I wanted to share it early because accessibility should not wait for a polished launch.

If you try it and something is missing, open an issue. If a pattern gets overlooked, tell me. If you work with a framework that has specific gotchas, contribute. This is a community project and it will get better with more eyes on it.


Why I Care This Much 


I use assistive technology every day. Accessibility is not a feature I advocate for. It is how I experience the internet. Every inaccessible component is a door that does not open for me. Every missing label is a form I cannot fill out. Every broken modal is a trap I have to escape from.

AI tools should make the web more accessible, not less. They generate code at a speed and scale that humans never could. If that code is inaccessible by default, the problem is not getting smaller. It is getting bigger. Fast.

That is why I built this. Not because it is a cool project. Because I need it. And I am not the only one.

If you want to support this, star the repo and watch it for updates. If you find gaps, open an issue. If you have ideas or framework-specific patterns to add, feel free to contribute. This is a community project. The more people involved, the better it gets.

Here is the repo one more time: https://github.com/taylorarndt/a11y-agent-team

Thank you for reading. More updates coming as the agents improve.

Taylor’s Substack is a reader-supported publication. To receive new posts and support my work, consider becoming a free or paid subscriber.

https://taylorarndt.substack.com/p/i-got-fed-up-with-ai-forgetting-accessibility

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://nfbnet.org/pipermail/nfbcs_nfbnet.org/attachments/20260222/9d6a1d47/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 8834 bytes
Desc: not available
URL: <http://nfbnet.org/pipermail/nfbcs_nfbnet.org/attachments/20260222/9d6a1d47/attachment.png>

From taylorarndt99 at gmail.com  Mon Feb 23 01:12:57 2026
From: taylorarndt99 at gmail.com (Taylor Arndt)
Date: Sun, 22 Feb 2026 19:12:57 -0600
Subject: [NFBCS] From Taylor Arndt: I Got Fed Up With AI Forgetting
 Accessibility, So I Built a Team That Will Not
In-Reply-To: <01c601dca461$1825b6a0$487123e0$@satx.rr.com>
References: 
 <LV2PR19MB59598ABF816E30CEABF1C5D8EE76A@LV2PR19MB5959.namprd19.prod.outlook.com>
 <3bec01dca43d$674f68d0$35ee3a70$@comcast.net>
 <a4e32c94-207e-4bfb-a5a0-ad1d4268ab8e@tysdomain.com>
 <SA1P220MB103391BA4F6903E5413D8C96E876A@SA1P220MB1033.NAMP220.PROD.OUTLOOK.COM>
 <06cd01dca460$5668d9c0$033a8d40$@comcast.net>
 <01c601dca461$1825b6a0$487123e0$@satx.rr.com>
Message-ID: 
 <CAFsrCh32=krgjqVJ=XTn5u6RmPan8-p_kvkJsZL2h9zT22=5ZQ@mail.gmail.com>

Thank you for correcting that

Taylor





On Sun, Feb 22, 2026 at 7:11 PM Peter via NFBCS <nfbcs at nfbnet.org> wrote:

> Hello David and everyone,
>
>
>
> Taylor is a girl not a guy
>
>
>
> Peter Donahue
>
>
>
> .
>
>
>
> *From:* NFBCS <nfbcs-bounces at nfbnet.org> *On Behalf Of *dandrews920---
> via NFBCS
> *Sent:* Sunday, February 22, 2026 7:04 PM
> *To:* 'NFB in Computer Science Mailing List' <nfbcs at nfbnet.org>
> *Cc:* dandrews920 at comcast.net
> *Subject:* Re: [NFBCS] From Taylor Arndt: I Got Fed Up With AI Forgetting
> Accessibility, So I Built a Team That Will Not
>
>
>
> He is not necessarily on this list – as I forwarded the message.
>
>
>
> Dave
>
>
>
>
>
>
>
> *From:* NFBCS <nfbcs-bounces at nfbnet.org> *On Behalf Of *Humberto Avila
> via NFBCS
> *Sent:* Sunday, February 22, 2026 4:02 PM
> *To:* NFB in Computer Science Mailing List <nfbcs at nfbnet.org>
> *Cc:* Humberto Avila <Humberto_Avila.IT104 at outlook.com>
> *Subject:* Re: [NFBCS] From Taylor Arndt: I Got Fed Up With AI Forgetting
> Accessibility, So I Built a Team That Will Not
>
>
>
> Thank you Taylor for sharing this!
>
> I am wondering, will this team of agents be deployed in other AI GPTs
> other thanClaude?
>
> Do you need a paid Claude account to use Code projects and these different
> types of agents?
>
> I have been recently getting intofibe-coding myself, just as a hobby. And
> I really like it, but I run into the same problem from time to time with
> non-accessible code, and I have to check the stuff manually.
>
>
>
> Thanks!
>
> Humberto
>
>
>
>
>
> [image: JAWS Certified, 2025]
> <https://www.freedomscientific.com/Training/Certification>
>
>
>
> *From:* NFBCS <nfbcs-bounces at nfbnet.org> *On Behalf Of *Ty Littlefield
> via NFBCS
> *Sent:* Sunday, February 22, 2026 1:44 PM
> *To:* NFB in Computer Science Mailing List <nfbcs at nfbnet.org>
> *Cc:* Ty Littlefield <tyler at tysdomain.com>
> *Subject:* Re: [NFBCS] From Taylor Arndt: I Got Fed Up With AI Forgetting
> Accessibility, So I Built a Team That Will Not
>
>
>
> This is awesome; thank you for doing it. How much of a difference have you
> found?
>
> My problem does tend to be context windows as you mentioned with the
> drifting, but the secondary issue is that AI was trained on a load of
> horrible data, so it tends to make terrible accessibility decisions. One of
> the more fun vibe-coded accessibility issues I'm stumbling on lately is
> adding aria-haspopup to everything.
>
>
>
> *Ty Littlefield (he/him/his)*
>
>    - From Bytes to Bites <https://tysdomain.com>|
>    - Linkedin <https://www.linkedin.com/in/ty-lerlittlefield/>
>
> On 2/22/2026 1:54 PM, dandrews920--- via NFBCS wrote:
>
>
>
> Taylor’s Substack - Friday, February 20, 2026 at 8:39 PM
> I Got Fed Up With AI Forgetting Accessibility, So I Built a Team That Will
> Not
>
> It is Friday night. I had a long day at work coding with Claude, and I am
> talking to some friends of mine. I have had it.
>
> AI tools do not care about accessibility. And I finally did something
> about it.
>
> Taylor’s Substack is a reader-supported publication. To receive new posts
> and support my work, consider becoming a free or paid subscriber.
> The Frustration
>
> I use AI coding tools every day. Claude Code is a core part of how I work.
> I have written about this before. AI helps me stay organized, keep context,
> and build things faster than my brain would allow on its own. It is
> genuinely one of the most important tools in my workflow.
>
> But there is a problem. A big one.
>
> AI tools are terrible at accessibility.
>
> I do not mean they are bad sometimes. I mean they are consistently,
> reliably, predictably bad at it. Every single time I ask an AI to build a
> component, I have to fight for the basics. Label your inputs. Trap focus in
> the modal. Do not use a div when a button exists. Make sure this contrast
> ratio actually passes. Add a live region so the screen reader knows
> something changed.
>
> These are not advanced requirements. These are the fundamentals. And AI
> drops them constantly.
> Why This Hits Different for Me
>
> I am a screen reader user. When AI generates a modal without focus
> trapping, I am the person who gets stuck. When it skips live regions on
> search results, I am the person who hears nothing. When it uses a div with
> an onClick instead of a button, I am the person who cannot activate it with
> my keyboard.
>
> I am not reviewing accessibility as an abstract checklist. I am living it.
> Every failure that ships is a wall I personally hit.
>
> And the worst part is that I know better. I am an accessibility
> specialist. I have the knowledge to catch these issues. But I should not
> have to catch them every single time. The tools should know this already.
> What I Tried First
>
> I tried the obvious things. I wrote detailed instructions in CLAUDE.md
> files. I created skills with accessibility rules. I added reminders to my
> prompts.
>
> None of it stuck.
>
> Skills in Claude Code activate maybe twenty percent of the time without
> manual intervention. Instructions in context files work at first, but as
> the conversation grows, they drift. The model deprioritizes them. It
> decides other things matter more. Accessibility gets quietly dropped from
> the plan.
>
> That is the pattern. Not malicious. Not intentional. Just gone. Every time.
> So I Built a Team
>
> I stopped trying to remind one model to care about accessibility. Instead,
> I built six specialized agents, each with a single focused job they cannot
> ignore.
>
> There is an Accessibility Lead that orchestrates the team and decides
> which specialists are needed. There is an ARIA Specialist that enforces
> correct roles, states, and properties. There is a Modal Specialist that
> owns focus trapping, focus return, and escape behavior. There is a Contrast
> Master that checks every color combination against WCAG AA ratios. There is
> a Keyboard Navigator that ensures everything can be reached and operated
> without a mouse. And there is a Live Region Controller that bridges the gap
> between visual updates and screen reader awareness.
>
> Each agent has its own context window. Its own system prompt. Its own
> identity. The ARIA specialist cannot forget about ARIA because ARIA is who
> it is. The contrast master cannot skip contrast checks because that is its
> entire purpose.
>
> A hook fires on every prompt I send to Claude Code. If the task involves
> UI code, the Accessibility Lead activates and coordinates the right
> specialists. If it does not involve UI, the hook is ignored and Claude
> works normally.
> Why Agents Instead of Everything Else
>
> I tried skills. They get ignored.
>
> I tried MCP servers. They add tool calls but do not change how the model
> reasons about code.
>
> I tried detailed instructions. They drift out of context.
>
> Agents are different. They run in their own window with their own rules.
> The rules are not suggestions. They are the agent’s entire identity. That
> is the difference. A suggestion can be deprioritized. An identity cannot.
> What It Covers
>
> The team enforces WCAG 2.1 Level AA compliance. That includes screen
> reader compatibility across VoiceOver, NVDA, and JAWS. Keyboard-only
> navigation. Focus management for single-page apps, modals, and dynamic
> content. Color contrast verification with actual ratio calculation. Live
> region implementation for toasts, search results, loading states, and form
> feedback. Semantic HTML enforcement. And common framework pitfalls like
> React conditional rendering breaking live regions and Tailwind color
> classes failing contrast.
>
> That is a lot. And it should be. Because accessibility is a lot.
> It Is Open Source
>
> I built this for the community. It is free. It is MIT licensed. Anyone
> using Claude Code can install it in about thirty seconds.
>
> The installer asks if you want it at the project level or globally. It
> works on macOS, Linux, and Windows. It even has an auto-update system that
> checks GitHub daily for improvements.
>
> Here is the repo: https://github.com/taylorarndt/a11y-agent-team
> This Is a Preview
>
> I am still testing. I am still refining the agents. I am still finding
> gaps and fixing them. This is not a finished product announcement. This is
> a preview. I wanted to share it early because accessibility should not wait
> for a polished launch.
>
> If you try it and something is missing, open an issue. If a pattern gets
> overlooked, tell me. If you work with a framework that has specific
> gotchas, contribute. This is a community project and it will get better
> with more eyes on it.
> Why I Care This Much
>
> I use assistive technology every day. Accessibility is not a feature I
> advocate for. It is how I experience the internet. Every inaccessible
> component is a door that does not open for me. Every missing label is a
> form I cannot fill out. Every broken modal is a trap I have to escape from.
>
> AI tools should make the web more accessible, not less. They generate code
> at a speed and scale that humans never could. If that code is inaccessible
> by default, the problem is not getting smaller. It is getting bigger. Fast.
>
> That is why I built this. Not because it is a cool project. Because I need
> it. And I am not the only one.
>
> If you want to support this, star the repo and watch it for updates. If
> you find gaps, open an issue. If you have ideas or framework-specific
> patterns to add, feel free to contribute. This is a community project. The
> more people involved, the better it gets.
>
> Here is the repo one more time:
> https://github.com/taylorarndt/a11y-agent-team
>
> Thank you for reading. More updates coming as the agents improve.
>
> Taylor’s Substack is a reader-supported publication. To receive new posts
> and support my work, consider becoming a free or paid subscriber.
>
>
> https://taylorarndt.substack.com/p/i-got-fed-up-with-ai-forgetting-accessibility
>
>
>
> _______________________________________________
> NFBCS mailing list
> NFBCS at nfbnet.org
> http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org
> To unsubscribe, change your list options or get your account info for
> NFBCS:
>
> http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/taylorarndt99%40gmail.com
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://nfbnet.org/pipermail/nfbcs_nfbnet.org/attachments/20260222/b1bc5d3c/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 8834 bytes
Desc: not available
URL: <http://nfbnet.org/pipermail/nfbcs_nfbnet.org/attachments/20260222/b1bc5d3c/attachment.png>

From nancy.l.coffman at gmail.com  Mon Feb 23 02:18:18 2026
From: nancy.l.coffman at gmail.com (Nancy Coffman)
Date: Sun, 22 Feb 2026 20:18:18 -0600
Subject: [NFBCS] audible accessibility regressions
In-Reply-To: <91dddcb3-6fc0-4b14-9269-72bbabb141c8@tysdomain.com>
References: <91dddcb3-6fc0-4b14-9269-72bbabb141c8@tysdomain.com>
Message-ID: <32C1BEEF-AB07-43B8-994F-BAD11B926744@gmail.com>

An HTML attachment was scrubbed...
URL: <http://nfbnet.org/pipermail/nfbcs_nfbnet.org/attachments/20260222/8c138c30/attachment.htm>

From deniserob at gmail.com  Mon Feb 23 11:18:14 2026
From: deniserob at gmail.com (Dr Denise M Robinson)
Date: Mon, 23 Feb 2026 06:18:14 -0500
Subject: [NFBCS] From Taylor Arndt: I Got Fed Up With AI Forgetting
 Accessibility, So I Built a Team That Will Not
In-Reply-To: <01c601dca461$1825b6a0$487123e0$@satx.rr.com>
References: 
 <LV2PR19MB59598ABF816E30CEABF1C5D8EE76A@LV2PR19MB5959.namprd19.prod.outlook.com>
 <3bec01dca43d$674f68d0$35ee3a70$@comcast.net>
 <a4e32c94-207e-4bfb-a5a0-ad1d4268ab8e@tysdomain.com>
 <SA1P220MB103391BA4F6903E5413D8C96E876A@SA1P220MB1033.NAMP220.PROD.OUTLOOK.COM>
 <06cd01dca460$5668d9c0$033a8d40$@comcast.net>
 <01c601dca461$1825b6a0$487123e0$@satx.rr.com>
Message-ID: 
 <CAAxsd_6W=jamYX+nd+UdmYg4mPecQVmSGDtoOGQEg3t-dFoybQ@mail.gmail.com>

AI definitely has huge issues along with also giving old commands. I create
a video and document for full and easy access with LinkedIn but not the
other: Keeping in mind I did this for Jaws but NVDA and narrator work great
also as long as you have the command knowledge and isn't that true of
everything--
- LinkedIn with JAWS Commands for total Access
<https://yourtechvision.com/2026/02/19/linkedin-with-jaws-commands-2/>
-
<https://yourtechvision.com/2026/01/17/cant-log-in-fix-password-and-login-problems-fast/>


*Denise M Robinson*

Denise M Robinson, Ph.D., CTVI, AT, IT, CVI Endorsement, Director/CEO
425-220-6935

YouTube Channel: @DrDeniseMRobinsontech
<https://www.youtube.com/channel/UC7YW7Ves0phCwCOtaZ3wWFw>
YOURTECHVISION.COM
Dr Denise M Robinson – Educational Services for Instruction in Access
Technology/Braille/Nemeth and other Access skills
<https://yourtechvision.com/>
Technology that gives YOU Vision....



On Sun, Feb 22, 2026 at 8:12 PM Peter via NFBCS <nfbcs at nfbnet.org> wrote:

> Hello David and everyone,
>
>
>
> Taylor is a girl not a guy
>
>
>
> Peter Donahue
>
>
>
> .
>
>
>
> *From:* NFBCS <nfbcs-bounces at nfbnet.org> *On Behalf Of *dandrews920---
> via NFBCS
> *Sent:* Sunday, February 22, 2026 7:04 PM
> *To:* 'NFB in Computer Science Mailing List' <nfbcs at nfbnet.org>
> *Cc:* dandrews920 at comcast.net
> *Subject:* Re: [NFBCS] From Taylor Arndt: I Got Fed Up With AI Forgetting
> Accessibility, So I Built a Team That Will Not
>
>
>
> He is not necessarily on this list – as I forwarded the message.
>
>
>
> Dave
>
>
>
>
>
>
>
> *From:* NFBCS <nfbcs-bounces at nfbnet.org> *On Behalf Of *Humberto Avila
> via NFBCS
> *Sent:* Sunday, February 22, 2026 4:02 PM
> *To:* NFB in Computer Science Mailing List <nfbcs at nfbnet.org>
> *Cc:* Humberto Avila <Humberto_Avila.IT104 at outlook.com>
> *Subject:* Re: [NFBCS] From Taylor Arndt: I Got Fed Up With AI Forgetting
> Accessibility, So I Built a Team That Will Not
>
>
>
> Thank you Taylor for sharing this!
>
> I am wondering, will this team of agents be deployed in other AI GPTs
> other thanClaude?
>
> Do you need a paid Claude account to use Code projects and these different
> types of agents?
>
> I have been recently getting intofibe-coding myself, just as a hobby. And
> I really like it, but I run into the same problem from time to time with
> non-accessible code, and I have to check the stuff manually.
>
>
>
> Thanks!
>
> Humberto
>
>
>
>
>
> [image: JAWS Certified, 2025]
> <https://www.freedomscientific.com/Training/Certification>
>
>
>
> *From:* NFBCS <nfbcs-bounces at nfbnet.org> *On Behalf Of *Ty Littlefield
> via NFBCS
> *Sent:* Sunday, February 22, 2026 1:44 PM
> *To:* NFB in Computer Science Mailing List <nfbcs at nfbnet.org>
> *Cc:* Ty Littlefield <tyler at tysdomain.com>
> *Subject:* Re: [NFBCS] From Taylor Arndt: I Got Fed Up With AI Forgetting
> Accessibility, So I Built a Team That Will Not
>
>
>
> This is awesome; thank you for doing it. How much of a difference have you
> found?
>
> My problem does tend to be context windows as you mentioned with the
> drifting, but the secondary issue is that AI was trained on a load of
> horrible data, so it tends to make terrible accessibility decisions. One of
> the more fun vibe-coded accessibility issues I'm stumbling on lately is
> adding aria-haspopup to everything.
>
>
>
> *Ty Littlefield (he/him/his)*
>
>    - From Bytes to Bites <https://tysdomain.com>|
>    - Linkedin <https://www.linkedin.com/in/ty-lerlittlefield/>
>
> On 2/22/2026 1:54 PM, dandrews920--- via NFBCS wrote:
>
>
>
> Taylor’s Substack - Friday, February 20, 2026 at 8:39 PM
> I Got Fed Up With AI Forgetting Accessibility, So I Built a Team That Will
> Not
>
> It is Friday night. I had a long day at work coding with Claude, and I am
> talking to some friends of mine. I have had it.
>
> AI tools do not care about accessibility. And I finally did something
> about it.
>
> Taylor’s Substack is a reader-supported publication. To receive new posts
> and support my work, consider becoming a free or paid subscriber.
> The Frustration
>
> I use AI coding tools every day. Claude Code is a core part of how I work.
> I have written about this before. AI helps me stay organized, keep context,
> and build things faster than my brain would allow on its own. It is
> genuinely one of the most important tools in my workflow.
>
> But there is a problem. A big one.
>
> AI tools are terrible at accessibility.
>
> I do not mean they are bad sometimes. I mean they are consistently,
> reliably, predictably bad at it. Every single time I ask an AI to build a
> component, I have to fight for the basics. Label your inputs. Trap focus in
> the modal. Do not use a div when a button exists. Make sure this contrast
> ratio actually passes. Add a live region so the screen reader knows
> something changed.
>
> These are not advanced requirements. These are the fundamentals. And AI
> drops them constantly.
> Why This Hits Different for Me
>
> I am a screen reader user. When AI generates a modal without focus
> trapping, I am the person who gets stuck. When it skips live regions on
> search results, I am the person who hears nothing. When it uses a div with
> an onClick instead of a button, I am the person who cannot activate it with
> my keyboard.
>
> I am not reviewing accessibility as an abstract checklist. I am living it.
> Every failure that ships is a wall I personally hit.
>
> And the worst part is that I know better. I am an accessibility
> specialist. I have the knowledge to catch these issues. But I should not
> have to catch them every single time. The tools should know this already.
> What I Tried First
>
> I tried the obvious things. I wrote detailed instructions in CLAUDE.md
> files. I created skills with accessibility rules. I added reminders to my
> prompts.
>
> None of it stuck.
>
> Skills in Claude Code activate maybe twenty percent of the time without
> manual intervention. Instructions in context files work at first, but as
> the conversation grows, they drift. The model deprioritizes them. It
> decides other things matter more. Accessibility gets quietly dropped from
> the plan.
>
> That is the pattern. Not malicious. Not intentional. Just gone. Every time.
> So I Built a Team
>
> I stopped trying to remind one model to care about accessibility. Instead,
> I built six specialized agents, each with a single focused job they cannot
> ignore.
>
> There is an Accessibility Lead that orchestrates the team and decides
> which specialists are needed. There is an ARIA Specialist that enforces
> correct roles, states, and properties. There is a Modal Specialist that
> owns focus trapping, focus return, and escape behavior. There is a Contrast
> Master that checks every color combination against WCAG AA ratios. There is
> a Keyboard Navigator that ensures everything can be reached and operated
> without a mouse. And there is a Live Region Controller that bridges the gap
> between visual updates and screen reader awareness.
>
> Each agent has its own context window. Its own system prompt. Its own
> identity. The ARIA specialist cannot forget about ARIA because ARIA is who
> it is. The contrast master cannot skip contrast checks because that is its
> entire purpose.
>
> A hook fires on every prompt I send to Claude Code. If the task involves
> UI code, the Accessibility Lead activates and coordinates the right
> specialists. If it does not involve UI, the hook is ignored and Claude
> works normally.
> Why Agents Instead of Everything Else
>
> I tried skills. They get ignored.
>
> I tried MCP servers. They add tool calls but do not change how the model
> reasons about code.
>
> I tried detailed instructions. They drift out of context.
>
> Agents are different. They run in their own window with their own rules.
> The rules are not suggestions. They are the agent’s entire identity. That
> is the difference. A suggestion can be deprioritized. An identity cannot.
> What It Covers
>
> The team enforces WCAG 2.1 Level AA compliance. That includes screen
> reader compatibility across VoiceOver, NVDA, and JAWS. Keyboard-only
> navigation. Focus management for single-page apps, modals, and dynamic
> content. Color contrast verification with actual ratio calculation. Live
> region implementation for toasts, search results, loading states, and form
> feedback. Semantic HTML enforcement. And common framework pitfalls like
> React conditional rendering breaking live regions and Tailwind color
> classes failing contrast.
>
> That is a lot. And it should be. Because accessibility is a lot.
> It Is Open Source
>
> I built this for the community. It is free. It is MIT licensed. Anyone
> using Claude Code can install it in about thirty seconds.
>
> The installer asks if you want it at the project level or globally. It
> works on macOS, Linux, and Windows. It even has an auto-update system that
> checks GitHub daily for improvements.
>
> Here is the repo: https://github.com/taylorarndt/a11y-agent-team
> This Is a Preview
>
> I am still testing. I am still refining the agents. I am still finding
> gaps and fixing them. This is not a finished product announcement. This is
> a preview. I wanted to share it early because accessibility should not wait
> for a polished launch.
>
> If you try it and something is missing, open an issue. If a pattern gets
> overlooked, tell me. If you work with a framework that has specific
> gotchas, contribute. This is a community project and it will get better
> with more eyes on it.
> Why I Care This Much
>
> I use assistive technology every day. Accessibility is not a feature I
> advocate for. It is how I experience the internet. Every inaccessible
> component is a door that does not open for me. Every missing label is a
> form I cannot fill out. Every broken modal is a trap I have to escape from.
>
> AI tools should make the web more accessible, not less. They generate code
> at a speed and scale that humans never could. If that code is inaccessible
> by default, the problem is not getting smaller. It is getting bigger. Fast.
>
> That is why I built this. Not because it is a cool project. Because I need
> it. And I am not the only one.
>
> If you want to support this, star the repo and watch it for updates. If
> you find gaps, open an issue. If you have ideas or framework-specific
> patterns to add, feel free to contribute. This is a community project. The
> more people involved, the better it gets.
>
> Here is the repo one more time:
> https://github.com/taylorarndt/a11y-agent-team
>
> Thank you for reading. More updates coming as the agents improve.
>
> Taylor’s Substack is a reader-supported publication. To receive new posts
> and support my work, consider becoming a free or paid subscriber.
>
>
> https://taylorarndt.substack.com/p/i-got-fed-up-with-ai-forgetting-accessibility
>
>
>
> _______________________________________________
> NFBCS mailing list
> NFBCS at nfbnet.org
> http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org
> To unsubscribe, change your list options or get your account info for
> NFBCS:
> http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/deniserob%40gmail.com
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://nfbnet.org/pipermail/nfbcs_nfbnet.org/attachments/20260223/d642c2fe/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 8834 bytes
Desc: not available
URL: <http://nfbnet.org/pipermail/nfbcs_nfbnet.org/attachments/20260223/d642c2fe/attachment-0001.png>

From dandrews920 at comcast.net  Tue Feb 24 05:14:07 2026
From: dandrews920 at comcast.net (dandrews920 at comcast.net)
Date: Mon, 23 Feb 2026 23:14:07 -0600
Subject: [NFBCS] From Taylor Arndt: I Got Fed Up With AI Forgetting
 Accessibility, So I Built a Team That Will Not
In-Reply-To: 
 <CAFsrCh32=krgjqVJ=XTn5u6RmPan8-p_kvkJsZL2h9zT22=5ZQ@mail.gmail.com>
References: 
 <LV2PR19MB59598ABF816E30CEABF1C5D8EE76A@LV2PR19MB5959.namprd19.prod.outlook.com>
 <3bec01dca43d$674f68d0$35ee3a70$@comcast.net>
 <a4e32c94-207e-4bfb-a5a0-ad1d4268ab8e@tysdomain.com>
 <SA1P220MB103391BA4F6903E5413D8C96E876A@SA1P220MB1033.NAMP220.PROD.OUTLOOK.COM>
 <06cd01dca460$5668d9c0$033a8d40$@comcast.net>
 <01c601dca461$1825b6a0$487123e0$@satx.rr.com>
  <CAFsrCh32=krgjqVJ=XTn5u6RmPan8-p_kvkJsZL2h9zT22=5ZQ@mail.gmail.com>
Message-ID: <64a101dca54c$67d19c00$3774d400$@comcast.net>

Sorry!

 

Dave

 

 

 

From: NFBCS <nfbcs-bounces at nfbnet.org> On Behalf Of Taylor Arndt via NFBCS
Sent: Sunday, February 22, 2026 7:13 PM
To: NFB in Computer Science Mailing List <nfbcs at nfbnet.org>
Cc: Taylor Arndt <taylorarndt99 at gmail.com>
Subject: Re: [NFBCS] From Taylor Arndt: I Got Fed Up With AI Forgetting Accessibility, So I Built a Team That Will Not

 

Thank you for correcting that



Taylor  




 

 

On Sun, Feb 22, 2026 at 7:11 PM Peter via NFBCS <nfbcs at nfbnet.org <mailto:nfbcs at nfbnet.org> > wrote:

Hello David and everyone,

 

Taylor is a girl not a guy

 

Peter Donahue

 

.

 

From: NFBCS <nfbcs-bounces at nfbnet.org <mailto:nfbcs-bounces at nfbnet.org> > On Behalf Of dandrews920--- via NFBCS
Sent: Sunday, February 22, 2026 7:04 PM
To: 'NFB in Computer Science Mailing List' <nfbcs at nfbnet.org <mailto:nfbcs at nfbnet.org> >
Cc: dandrews920 at comcast.net <mailto:dandrews920 at comcast.net> 
Subject: Re: [NFBCS] From Taylor Arndt: I Got Fed Up With AI Forgetting Accessibility, So I Built a Team That Will Not

 

He is not necessarily on this list – as I forwarded the message.

 

Dave

 

 

 

From: NFBCS <nfbcs-bounces at nfbnet.org <mailto:nfbcs-bounces at nfbnet.org> > On Behalf Of Humberto Avila via NFBCS
Sent: Sunday, February 22, 2026 4:02 PM
To: NFB in Computer Science Mailing List <nfbcs at nfbnet.org <mailto:nfbcs at nfbnet.org> >
Cc: Humberto Avila <Humberto_Avila.IT104 at outlook.com <mailto:Humberto_Avila.IT104 at outlook.com> >
Subject: Re: [NFBCS] From Taylor Arndt: I Got Fed Up With AI Forgetting Accessibility, So I Built a Team That Will Not

 

Thank you Taylor for sharing this! 

I am wondering, will this team of agents be deployed in other AI GPTs other thanClaude? 

Do you need a paid Claude account to use Code projects and these different types of agents? 

I have been recently getting intofibe-coding myself, just as a hobby. And I really like it, but I run into the same problem from time to time with non-accessible code, and I have to check the stuff manually. 

 

Thanks! 

Humberto

 

 

 <https://www.freedomscientific.com/Training/Certification> 

 

From: NFBCS <nfbcs-bounces at nfbnet.org <mailto:nfbcs-bounces at nfbnet.org> > On Behalf Of Ty Littlefield via NFBCS
Sent: Sunday, February 22, 2026 1:44 PM
To: NFB in Computer Science Mailing List <nfbcs at nfbnet.org <mailto:nfbcs at nfbnet.org> >
Cc: Ty Littlefield <tyler at tysdomain.com <mailto:tyler at tysdomain.com> >
Subject: Re: [NFBCS] From Taylor Arndt: I Got Fed Up With AI Forgetting Accessibility, So I Built a Team That Will Not

 

This is awesome; thank you for doing it. How much of a difference have you found?

My problem does tend to be context windows as you mentioned with the drifting, but the secondary issue is that AI was trained on a load of horrible data, so it tends to make terrible accessibility decisions. One of the more fun vibe-coded accessibility issues I'm stumbling on lately is adding aria-haspopup to everything.

 

Ty Littlefield (he/him/his)

*	From Bytes to Bites <https://tysdomain.com> | 
*	Linkedin <https://www.linkedin.com/in/ty-lerlittlefield/> 

On 2/22/2026 1:54 PM, dandrews920--- via NFBCS wrote:

 

Taylor’s Substack - Friday, February 20, 2026 at 8:39 PM


I Got Fed Up With AI Forgetting Accessibility, So I Built a Team That Will Not


  <https://substackcdn.com/image/fetch/$s_!RcQU!,f_auto,q_auto:best,fl_progressive:steep/https%3A%2F%2Ftaylorarndt.substack.com%2Ftwitter%2Fsubscribe-card.jpg%3Fv%3D-888026622%26version%3D9> 

It is Friday night. I had a long day at work coding with Claude, and I am talking to some friends of mine. I have had it.

AI tools do not care about accessibility. And I finally did something about it.

Taylor’s Substack is a reader-supported publication. To receive new posts and support my work, consider becoming a free or paid subscriber.


The Frustration 


I use AI coding tools every day. Claude Code is a core part of how I work. I have written about this before. AI helps me stay organized, keep context, and build things faster than my brain would allow on its own. It is genuinely one of the most important tools in my workflow.

But there is a problem. A big one.

AI tools are terrible at accessibility.

I do not mean they are bad sometimes. I mean they are consistently, reliably, predictably bad at it. Every single time I ask an AI to build a component, I have to fight for the basics. Label your inputs. Trap focus in the modal. Do not use a div when a button exists. Make sure this contrast ratio actually passes. Add a live region so the screen reader knows something changed.

These are not advanced requirements. These are the fundamentals. And AI drops them constantly.


Why This Hits Different for Me 


I am a screen reader user. When AI generates a modal without focus trapping, I am the person who gets stuck. When it skips live regions on search results, I am the person who hears nothing. When it uses a div with an onClick instead of a button, I am the person who cannot activate it with my keyboard.

I am not reviewing accessibility as an abstract checklist. I am living it. Every failure that ships is a wall I personally hit.

And the worst part is that I know better. I am an accessibility specialist. I have the knowledge to catch these issues. But I should not have to catch them every single time. The tools should know this already.


What I Tried First 


I tried the obvious things. I wrote detailed instructions in CLAUDE.md files. I created skills with accessibility rules. I added reminders to my prompts.

None of it stuck.

Skills in Claude Code activate maybe twenty percent of the time without manual intervention. Instructions in context files work at first, but as the conversation grows, they drift. The model deprioritizes them. It decides other things matter more. Accessibility gets quietly dropped from the plan.

That is the pattern. Not malicious. Not intentional. Just gone. Every time.


So I Built a Team 


I stopped trying to remind one model to care about accessibility. Instead, I built six specialized agents, each with a single focused job they cannot ignore.

There is an Accessibility Lead that orchestrates the team and decides which specialists are needed. There is an ARIA Specialist that enforces correct roles, states, and properties. There is a Modal Specialist that owns focus trapping, focus return, and escape behavior. There is a Contrast Master that checks every color combination against WCAG AA ratios. There is a Keyboard Navigator that ensures everything can be reached and operated without a mouse. And there is a Live Region Controller that bridges the gap between visual updates and screen reader awareness.

Each agent has its own context window. Its own system prompt. Its own identity. The ARIA specialist cannot forget about ARIA because ARIA is who it is. The contrast master cannot skip contrast checks because that is its entire purpose.

A hook fires on every prompt I send to Claude Code. If the task involves UI code, the Accessibility Lead activates and coordinates the right specialists. If it does not involve UI, the hook is ignored and Claude works normally.


Why Agents Instead of Everything Else 


I tried skills. They get ignored.

I tried MCP servers. They add tool calls but do not change how the model reasons about code.

I tried detailed instructions. They drift out of context.

Agents are different. They run in their own window with their own rules. The rules are not suggestions. They are the agent’s entire identity. That is the difference. A suggestion can be deprioritized. An identity cannot.


What It Covers 


The team enforces WCAG 2.1 Level AA compliance. That includes screen reader compatibility across VoiceOver, NVDA, and JAWS. Keyboard-only navigation. Focus management for single-page apps, modals, and dynamic content. Color contrast verification with actual ratio calculation. Live region implementation for toasts, search results, loading states, and form feedback. Semantic HTML enforcement. And common framework pitfalls like React conditional rendering breaking live regions and Tailwind color classes failing contrast.

That is a lot. And it should be. Because accessibility is a lot.


It Is Open Source 


I built this for the community. It is free. It is MIT licensed. Anyone using Claude Code can install it in about thirty seconds.

The installer asks if you want it at the project level or globally. It works on macOS, Linux, and Windows. It even has an auto-update system that checks GitHub daily for improvements.

Here is the repo: https://github.com/taylorarndt/a11y-agent-team


This Is a Preview 


I am still testing. I am still refining the agents. I am still finding gaps and fixing them. This is not a finished product announcement. This is a preview. I wanted to share it early because accessibility should not wait for a polished launch.

If you try it and something is missing, open an issue. If a pattern gets overlooked, tell me. If you work with a framework that has specific gotchas, contribute. This is a community project and it will get better with more eyes on it.


Why I Care This Much 


I use assistive technology every day. Accessibility is not a feature I advocate for. It is how I experience the internet. Every inaccessible component is a door that does not open for me. Every missing label is a form I cannot fill out. Every broken modal is a trap I have to escape from.

AI tools should make the web more accessible, not less. They generate code at a speed and scale that humans never could. If that code is inaccessible by default, the problem is not getting smaller. It is getting bigger. Fast.

That is why I built this. Not because it is a cool project. Because I need it. And I am not the only one.

If you want to support this, star the repo and watch it for updates. If you find gaps, open an issue. If you have ideas or framework-specific patterns to add, feel free to contribute. This is a community project. The more people involved, the better it gets.

Here is the repo one more time: https://github.com/taylorarndt/a11y-agent-team

Thank you for reading. More updates coming as the agents improve.

Taylor’s Substack is a reader-supported publication. To receive new posts and support my work, consider becoming a free or paid subscriber.

https://taylorarndt.substack.com/p/i-got-fed-up-with-ai-forgetting-accessibility

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://nfbnet.org/pipermail/nfbcs_nfbnet.org/attachments/20260223/ffbf4c70/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 8834 bytes
Desc: not available
URL: <http://nfbnet.org/pipermail/nfbcs_nfbnet.org/attachments/20260223/ffbf4c70/attachment.png>

From dan.tevelde at comcast.net  Tue Feb 24 16:04:04 2026
From: dan.tevelde at comcast.net (dan.tevelde at comcast.net)
Date: Tue, 24 Feb 2026 10:04:04 -0600
Subject: [NFBCS] audible accessibility regressions
In-Reply-To: <32C1BEEF-AB07-43B8-994F-BAD11B926744@gmail.com>
References: <91dddcb3-6fc0-4b14-9269-72bbabb141c8@tysdomain.com>
 <32C1BEEF-AB07-43B8-994F-BAD11B926744@gmail.com>
Message-ID: <033a01dca5a7$34491b00$9cdb5100$@comcast.net>

I used to like the Audible iOS application but recently I have been disappointed with its unpredictability. If I navigate to the library tab, sometimes the screen goes completely blank and VoiceOver announces, ‘dynamic island empty’ and executing swipe gestures doesn’t do anything. I end up either closing the app or if I navigate to the library tab, I select the lists tab and then select audiobooks. I find using the player inconsistent. The player worked for me until a recent update which broke it. There was another update which fixed it. I don’t like the cluttered Audible interface and the fact that it seems to turn on screen recognition even though I have it turned off in VoiceOver settings.

 

I’m finding that Meta integration is broken. If I open the Meta app, say ‘hey Meta play’ and then the name of the book followed by ‘on Audible’ Audible opens but the book doesn’t play. When I got my Meta classes Audible integration worked once I enabled the service in the Meta application settings. I don’t know where the breakdown is happening but it is a serious problem. Using the Audible application used to be a pleasant experience. Now it is a nightmare.

 

Dan

 

From: NFBCS <nfbcs-bounces at nfbnet.org> On Behalf Of Nancy Coffman via NFBCS
Sent: Sunday, February 22, 2026 8:18 PM
To: nfbcs at nfbnet.org
Cc: Nancy Coffman <nancy.l.coffman at gmail.com>
Subject: Re: [NFBCS] audible accessibility regressions

 

This issue should also be reported to Amazon as they own Audible.

Nancy Coffman





On Feb 22, 2026, at 7:07 PM, Ty Littlefield via NFBCS <nfbcs at nfbnet.org <mailto:nfbcs at nfbnet.org> > wrote:

﻿ 

Hello,

I'm glad that people are on these issues. I can not test to verify the miniplayer issues.

I am on IOS 26.3 (not beta) and running Audible 4.64 with no updates to be installed.

If I navigate to my library tab, all of the books that can be played or downloaded that are previously given a button role still have the button role, but they also say "has popup button." after the button role is announced.

Activating any of these either does nothing, in the case of being able to play, or gives me a blank screen. Dragging my finger around the screen to explore receives no feedback. The only way I've found to get controls back is to close Audible in the app switcher, then open it again. Turning Voiceover off and back on again does not help.

 

Thanks,

 

Ty Littlefield (he/him/his)

*	From Bytes to Bites <https://tysdomain.com> | 
*	Linkedin <https://www.linkedin.com/in/ty-lerlittlefield/> |
*	Github <https://github.com/tlfdev> 

On 2/22/2026 5:24 PM, Mosen, Jonathan via NFBCS wrote:

Hello Ty, yes, CENA is in regular touch with Amazon on a range of issues, some of which are reported to us via the inaccessibility tracker form we offer for the purpose of bug collections.

We did raise the serious regression in the Mini Player after receiving numerous reports, and Amazon fixed it fairly quickly. The update came out a week and a half ago or so. Are you definitely running the latest build?

If you are and you are still experiencing issues, please do let me know and we’ll investigate them so we can pass on good quality data. I am no longer able to duplicate the issue personally after installing the update.

 

Thanks.

 

Jonathan Mosen
Executive Director for Accessibility Excellence
National Federation of the Blind 
410-659-9314 ex 2233   
 <mailto:jmosen at nfb.org> jmosen at nfb.org


Reminder: Attend  <https://nfb.org/convention> National Convention, July 3-8, 2026, in Austin, Texas.
“It’s the time of year where blind people are the majority.”

 <https://nfb.org/> 

 <https://nfb.org/> <image001.jpg>

 

 

From: NFBCS  <mailto:nfbcs-bounces at nfbnet.org> <nfbcs-bounces at nfbnet.org> On Behalf Of Ty Littlefield via NFBCS
Sent: Sunday, February 22, 2026 6:59 PM
To: NFB in Computer Science Mailing List  <mailto:nfbcs at nfbnet.org> <nfbcs at nfbnet.org>
Cc: Ty Littlefield  <mailto:tyler at tysdomain.com> <tyler at tysdomain.com>
Subject: [NFBCS] audible accessibility regressions

 

Hi all,

I'm curious if anyone has connections to anyone who can file these to be fixed. Audible has introduced two recent bugs that are horrible for accessibility: one where the miniplayer button you can activate to expand does not work, and another much more frustrating issue where the button to activate a book title in your library is treated as a popup button.

This has a hint of "double tap to activate the picker," and reads as "button popup button," but there is not a menu presented. This means that it's now impossible to download/play books with Voiceover on IOS.

 

I've reported the issue to Apple, because Voiceover shouldn't hit this point and present a blank screen, but I'm also concerned at how many issues Audible has introduced in terms of accessibility.

 

I'd be happy to connect with anyone, or feel free if you know of someone to just pass this along if that works better.

 

Thanks,

-- 

Ty Littlefield (he/him/his)

1.	From Bytes to Bites <https://tysdomain.com> | 
2.	Linkedin <https://www.linkedin.com/in/ty-lerlittlefield/> |
3.	Github <https://github.com/tlfdev> 





_______________________________________________
NFBCS mailing list
NFBCS at nfbnet.org <mailto:NFBCS at nfbnet.org> 
http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org
To unsubscribe, change your list options or get your account info for NFBCS:
http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/tyler%40tysdomain.com

_______________________________________________
NFBCS mailing list
NFBCS at nfbnet.org <mailto:NFBCS at nfbnet.org> 
http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org
To unsubscribe, change your list options or get your account info for NFBCS:
http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/nancy.l.coffman%40gmail.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://nfbnet.org/pipermail/nfbcs_nfbnet.org/attachments/20260224/9e76b844/attachment.htm>

From oscarjmontiel37 at gmail.com  Wed Feb 25 14:11:16 2026
From: oscarjmontiel37 at gmail.com (Real talk with Oscar Josue Montiel)
Date: Wed, 25 Feb 2026 09:11:16 -0500
Subject: [NFBCS] Informational Interview: For those who studied Business With
 Concentration In Management Information Systems
Message-ID: <62CC2EAB-D257-4EF4-B3A9-3973FDD9447A@gmail.com>

Hello:

I hope this email finds you well. I am reaching out to anyone who studied Business and concentrated in Management Information systems and now is a professional in this field. I have to complete an informational  interview for a class assignment due this weekend. If interested please email me at oscarjmontiel37 at gmail.com. I look forward to hearing from you soon.

Thanks,



Oscar Montiel
Sent from my iPhone

From jeff at jeffbishop.com  Wed Feb 25 19:50:41 2026
From: jeff at jeffbishop.com (Jeff Bishop)
Date: Wed, 25 Feb 2026 19:50:41 +0000
Subject: [NFBCS] 6 Agents on Friday. 47 by Monday
In-Reply-To: 
 <CYYPR02MB9901C9B543A7776D7D8150E5BA75A@CYYPR02MB9901.namprd02.prod.outlook.com>
References: <post-189168941@substack.com>
 <20260225183924.3.35f8d6578a430bc7@mg-d1.substack.com>
 <CYYPR02MB9901C9B543A7776D7D8150E5BA75A@CYYPR02MB9901.namprd02.prod.outlook.com>
Message-ID: 
 <CYYPR02MB9901175A68AA353241D2A90CBA75A@CYYPR02MB9901.namprd02.prod.outlook.com>

Hello NFBCS Members,

Taylor and I are so excited about what this project has turned out to be … Visit the community site on Github, learn about the GIT Going with Github course that is happening on March 7th and 8th and get involved. We would love your input, engagement and most importantly your contributions.

Jeff Bishop

It is early Wednesday morning. February 26th. Something went so right over the past five days that my brain will not stop replaying it.
Let me take you back to Friday night.

How a Frustrated Friday Night Became a Movement

Friday Night on Discord
I was working on a project. I do not even remember what it was. Something with Claude Code, like most of my nights. And I was on a Discord call with some friends, just talking while I worked.
Then something happened in the code that just set me off.
ARIA roles placed wherever the model felt like putting them. No logic. No structure. Just ARIA sprayed across the page like decoration. Inputs without labels. Modals with no focus trapping. Divs pretending to be buttons. The same failures I have been correcting for months. Every single session.
I had enough.
I had enough of fixing ARIA by hand. I had enough of inaccessible code shipping as the default. I had enough of correcting these AIs over and over and getting the same broken output the next time I asked. You know the feeling. It is too much. At some point you stop asking nicely and you start building.
So that is what I did. I decided to build a team of AI agents. Not one model trying to remember everything. A team. Specialists. Each one responsible for one piece of accessibility that it cannot forget, because that is the only thing it knows.
I had no idea what I was getting into.
I was just trying to solve a problem for myself. I wanted Claude to actually write accessible code without me having to babysit every line. That is it. I did not set out to build a forty-seven agent system across three platforms with a GitHub organization and a website and a press release. I was just frustrated on a Friday night.
Of course, I tried other things first. I tried skills in Claude Code. They activate maybe 10 percent of the time without manual intervention. I tried writing detailed instructions in CLAUDE.md files. They work at first, but as the conversation grows, they drift. The model deprioritizes them. It decides other things matter more. Accessibility gets quietly dropped from the plan. Every time.
So, I built agents instead. Six of them. I published a preview post that night, shared the repo, and went to bed.
By Saturday morning, this thing had already outgrown what I imagined. And it did not stop there.

This Is Not Just Me

I need to say this up front because it matters more than anything else in this post.
This is not my project anymore. It never should have been just mine. The moment it stopped being one person yelling into the void and became a team of people building together, everything changed. The scope changed. The quality changed. The ambition changed. The whole thing became something I could not have built alone. And that is the point.
Accessibility has always been a community fight. One person cannot cover every screen reader, every browser, every framework, every assistive technology, every lived experience. That is why the project moved to a GitHub organization called Community Access. That is why it is MIT licensed. That is why it costs nothing. Because the more people who touch this, the better it gets for the people who need it.

Jeff

Jeff Bishop and I were talking on Friday night. That is how this started. I was venting about AI tools forgetting accessibility, and Jeff was right there with me. We were already in the same conversation when I published the preview post and shared the repo.
By Saturday morning, Jeff was not just talking anymore. He was building. I did not expect what happened next.
Jeff did not open an issue or send a message saying nice work. He started pushing code. Within hours he was deep in the codebase, moving faster than I could keep up. By the end of Saturday, he had more commits than I did.
That is not an exaggeration. Look at the git log. Forty-three commits from Jeff in five days. He saw what I was trying to do. He saw where it needed to go. And he went there.
Jeff is blind. Like me, he uses assistive technology every day. He is not reviewing accessibility as an abstract checklist. He is living it. When he builds an agent that enforces focus trapping in modals, it is because he has been trapped in modals. When he writes rules for screen reader announcements, it is because he has sat in silence waiting for an announcement that never came.
That shared experience is what made this work. We did not have to convince each other that accessibility matters. We just had to build.

The Hooks Problem

Now let me explain hooks, because if you read my preview post on Friday, I made hooks sound like the answer to everything. They were not.
A hook in Claude Code is a script that fires every time you send a prompt. Think of it like a checkpoint. Before the AI starts working, the hook looks at what you asked and decides if extra rules should apply. If the task involves UI code, the accessibility agents activate. If it does not, they stay out of the way. That was the idea. And on Friday night, it worked.
The problem arose when we tried to make hooks work for everyone. Not just me on my Mac. Everyone. On every platform and different Claude Code version.
Hooks are fragile. They break across platforms. The JSON schema kept changing. PowerShell on Windows handled them differently than bash on Mac and Linux. Some hooks fired when they should not have. Others did not fire when they should have. We spent hours debugging output formats, timeout issues, and schema mismatches.
Jeff and I merged pull requests fixing hooks. A pull request is how you propose a change to code on GitHub. Someone reviews it, approves it, and it gets merged into the main project. We merged pull requests fixing hooks. Then more pull requests fixing the fixes. Then more fixing those. It was a cycle. Every time we thought we had it, something else broke.
On Tuesday, Jeff made a decision I did not expect. He removed all of them. Every hook. Every hook file. Every hook reference in every documentation file. Gone.
He replaced them with something better. Instead of hooks intercepting prompts, orchestrator agents now coordinate the team through explicit contracts. Each agent returns structured output with confidence levels so the next agent knows exactly what it is getting. Nothing gets lost between steps because the contracts define exactly what goes in and what comes out.
It is cleaner. It is more reliable. And it works on every platform without platform-specific debugging.
That is the kind of decision that only happens when someone is deep enough in the code to see the real problem. Jeff was deep enough by Saturday afternoon.

What It Was

On Friday, Accessibility Agents was six agents in a personal GitHub repo under my name. An accessibility lead, an ARIA specialist, a modal specialist, a contrast master, a keyboard navigator, and a live region controller. It supported Claude Code. That was it.

What It Is Now

Forty-seven agents across four teams. Three platforms. Fourteen shared knowledge modules. Fifty-two pre-built prompts. A GitHub organization. A dedicated website. One command to install.
The web accessibility team alone has sixteen agents. ARIA, modals, contrast, keyboard navigation, live regions, forms, alt text and headings, data tables, link text, cognitive accessibility, mobile accessibility, design systems, guided audits, testing guidance, and WCAG reference.
There is a document scanning team that covers Word, Excel, PowerPoint, PDF, and EPUB files. Forty-six built-in rules for Office documents. Fifty-six for PDFs. It generates VPAT compliance reports. It exports findings to CSV with links to help documentation so people know exactly how to fix what it finds.
There is a markdown documentation team that scans files across nine accessibility domains.
There is a GitHub workflow team with eleven agents for PR review, issue triage, daily briefings, analytics, and repository management.
It runs on Claude Code, GitHub Copilot, and Claude Desktop. It installs with one command on macOS, Linux, and Windows. It is free. It is MIT licensed. It costs nothing.

Before Anyone Asks, No, This Is Not an Overlay

I can already see the comment. Someone is going to read this post, see forty-seven AI agents and the word accessibility in the same sentence, and think: great, another magic fix. Another overlay. Another tool that claims to solve accessibility so developers do not have to think about it.
No. Absolutely not. If you have read my writing before, you know how I feel about overlays. One of them literally broke my rent portal so badly that I could not pay rent until the landlord removed it. I have written an entire post about why overlays are harmful. I am not about to build one.
Let me be crystal clear about what Accessibility Agents is and what it is not.
This is a developer tool. It runs inside your code editor while you are writing code. It helps the AI write more accessible code from the start. That is it. It does not touch your website. It does not add a widget. It does not inject JavaScript into your pages. It does not promise compliance. There is no toolbar. There is no badge. There is no fee.
And here is the part I really need you to hear. This does not replace testing with real assistive technology. It does not replace VoiceOver. It does not replace NVDA. It does not replace JAWS. It does not replace a human being navigating your site with a keyboard and a screen reader and telling you what is broken.
What it does is raise the floor. Code that comes out of an AI tool with these agents active is going to be more accessible than code that comes out without them. Labels will be there. Focus trapping will be there. ARIA roles will make sense instead of being scattered like confetti. Contrast ratios will be checked before you ship, not after someone files a complaint.
That is not a magic fix. That is a better starting point. You still need to test. You still need real users. You still need to care. But at least you are not starting from zero every single time.
If anyone tries to sell you a tool that replaces accessibility testing, run. This is not that tool. This is the tool that makes the code better before testing even begins.

It Moved

The project does not live under my personal GitHub account anymore. It is at the Community Access organization now.
That was deliberate. This is not my project. It is not Jeff’s project. It is a community project. The more perspectives and lived experiences that go into these agents, the better they serve the people who need them.

Thirty Pull Requests in Five Days

I keep coming back to this number because it tells the story better than anything else I can say.
Thirty pull requests merged in five days. That means thirty separate changes were proposed, reviewed, and added to the project. Three hundred and sixty files changed. Seventy-three thousand lines of code added. Thirty-four security vulnerabilities identified and resolved. Path traversal prevention. Injection protection. ZIP bomb limits. Input validation at every call site.
This was not a casual weekend project. This was a sprint. Jeff and I were building in parallel, reviewing each other’s code, catching issues, pushing fixes. The velocity was unlike anything I have experienced on an open source project.
And it happened because people who need accessible software decided to stop waiting for someone else to build it.

Why This Matters

AI coding tools generate code at a speed and scale that humans never could. If that code is inaccessible by default, the problem is not getting smaller. It is getting bigger. Fast.
Ninety-five point nine percent of the top one million websites already have detectable accessibility failures. That number has barely moved in years. AI tools risk making it worse by automating the same mistakes at a scale no human team could match.
I am a screen reader user. When AI generates a modal without focus trapping, I am the person who gets stuck. When it skips live regions on search results, I am the person who hears nothing. When it uses a div with an onClick instead of a button, I am the person who cannot activate it with my keyboard.
But here is what I have learned over the past five days. I am not the only one who feels this way. Jeff feels it. The people who starred the repo and opened issues feel it. This is not one person’s frustration. It is a shared experience across an entire community that has been dealing with inaccessible software for decades.
That is why this is not just me. That is why it cannot be just me. One person’s agents catch one person’s blind spots. A community’s agents catch the patterns that none of us would find alone.

Version 2.0

On Tuesday, Jeff and I got on a call and decided it was time. We were going to release version 2.0.
Five days earlier I had six agents and a personal repo. Now we had forty-seven agents, three platforms, a GitHub organization, a website, and a community. It was not a preview anymore. It was a release.
We published the official announcement yesterday. You can read the full press release on the Community Access website:

https://community-access.github.io/news.html#post/accessibility-agents-v2-launch

I am sharing it here because this community has followed this journey from the beginning. You read the preview post on Friday. You saw the Swift agent team launch. You have been here for the frustration and the building and the breakthroughs. You deserve to see how it landed.
Forty-seven agents. Three platforms. One command to install. Zero cost. That is the headline. But the real story is that a community built this in five days because the tools we depend on every day were not building it for us.

Be Part of This

So now I am promoting it. And I am hoping you will try it out.
I want to make this as easy as possible. You do not need to be a developer to help. You do not need to write code. You do not need to know what ARIA stands for. If you care about accessible software, there is something you can do right now.
Talk about it. Share the project with someone who builds software. Post about it. Mention it in a conversation. The biggest thing holding accessibility back is that not enough people know it is a problem. Every time someone new hears about this project, that changes a little.
Try it. Install it with one command. Use it on your next project. See what it catches. See what it misses.
If you find a bug, file it. Go to the GitHub repo, open an issue, and describe what happened. What you expected. What you got instead. That is it. A good bug report is one of the most valuable contributions anyone can make. It does not take expertise. It takes honesty.
If you want to contribute code, the agents are plain markdown files. You do not need special tooling. You do not need permission. Fork it, make a change, open a pull request. Jeff did exactly that on Saturday morning and look where we are now.

Website: https://community-access.github.io/
GitHub: https://github.com/Community-Access/accessibility-agents

Thank You

To Jeff, for picking this up on Saturday morning and not putting it down. For removing the hooks when I was still trying to fix them. For writing forty-three commits in five days. For caring about this as much as I do.
To every contributor who showed up, opened a PR, filed an issue, or starred the repo. You turned a frustrated Friday night into something real.
And to everyone reading this. If you build software, you have the power to make it accessible. These agents are one way to start. But they are not the finish line. They are the starting block.
This is how it starts. Not with a company. Not with funding. With people who got tired of fighting the same fight every day and decided to build something that fights back.
That is not just me. That is all of us.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://nfbnet.org/pipermail/nfbcs_nfbnet.org/attachments/20260225/516f6108/attachment.htm>

From tyler at tysdomain.com  Wed Feb 25 21:44:54 2026
From: tyler at tysdomain.com (Ty Littlefield)
Date: Wed, 25 Feb 2026 14:44:54 -0700
Subject: [NFBCS] 6 Agents on Friday. 47 by Monday
In-Reply-To: 
 <CYYPR02MB9901175A68AA353241D2A90CBA75A@CYYPR02MB9901.namprd02.prod.outlook.com>
References: <post-189168941@substack.com>
 <20260225183924.3.35f8d6578a430bc7@mg-d1.substack.com>
 <CYYPR02MB9901C9B543A7776D7D8150E5BA75A@CYYPR02MB9901.namprd02.prod.outlook.com>
 <CYYPR02MB9901175A68AA353241D2A90CBA75A@CYYPR02MB9901.namprd02.prod.outlook.com>
Message-ID: <4c047723-a2ff-4c66-94ed-09dd7a11a78b@tysdomain.com>

This is a lot of agents, but my question from the other day still exists.

When Aria issues exist from AI code, it's not generally a context window 
issue for me. It's the fact that AI is outright incorrect about 
accessibility solutions. So, for example it might add an aria label of 
"main navigation" to a region with the nav tag, meaning that a screen 
reader will read "main navigation navigation region."

I'm curious how this is being tackled. We can throw all the agents we 
like at accessibility, and in the case of context windows this will be 
helpful, as it is in any type of code work--not just accessibility--but, 
my problem is less that the context windows slip and more that the 
information provided is incorrect.


How has this project been tested, and of those tests, how does more 
agents with context windows change the output?

Thanks,



*Ty Littlefield (he/him/his)*

  * From Bytes to Bites <https://tysdomain.com>|
  * Linkedin <https://www.linkedin.com/in/ty-lerlittlefield/>|
  * Github <https://github.com/tlfdev>

On 2/25/2026 12:50 PM, Jeff Bishop via NFBCS wrote:
> 6 Agents on Friday. 47 by Monday
>
> Hello NFBCS Members,
>
> Taylor and I are so excited about what this project has turned out to 
> be … Visit the community site on Github, learn about the GIT Going 
> with Github course that is happening on March 7^th and 8^th and get 
> involved. We would love your input, engagement and most importantly 
> your contributions.
>
> Jeff Bishop
>
> It is early Wednesday morning. February 26th. Something went so right 
> over the past five days that my brain will not stop replaying it.
>
> Let me take you back to Friday night.
>
> How a Frustrated Friday Night Became a Movement
>
> Friday Night on Discord
>
> I was working on a project. I do not even remember what it was. 
> Something with Claude Code, like most of my nights. And I was on a 
> Discord call with some friends, just talking while I worked.
>
> Then something happened in the code that just set me off.
>
> ARIA roles placed wherever the model felt like putting them. No logic. 
> No structure. Just ARIA sprayed across the page like decoration. 
> Inputs without labels. Modals with no focus trapping. Divs pretending 
> to be buttons. The same failures I have been correcting for months. 
> Every single session.
>
> I had enough.
>
> I had enough of fixing ARIA by hand. I had enough of inaccessible code 
> shipping as the default. I had enough of correcting these AIs over and 
> over and getting the same broken output the next time I asked. You 
> know the feeling. It is too much. At some point you stop asking nicely 
> and you start building.
>
> So that is what I did. I decided to build a team of AI agents. Not one 
> model trying to remember everything. A team. Specialists. Each one 
> responsible for one piece of accessibility that it cannot forget, 
> because that is the only thing it knows.
>
> I had no idea what I was getting into.
>
> I was just trying to solve a problem for myself. I wanted Claude to 
> actually write accessible code without me having to babysit every 
> line. That is it. I did not set out to build a forty-seven agent 
> system across three platforms with a GitHub organization and a website 
> and a press release. I was just frustrated on a Friday night.
>
> Of course, I tried other things first. I tried skills in Claude Code. 
> They activate maybe 10 percent of the time without manual 
> intervention. I tried writing detailed instructions in CLAUDE.md 
> files. They work at first, but as the conversation grows, they drift. 
> The model deprioritizes them. It decides other things matter more. 
> Accessibility gets quietly dropped from the plan. Every time.
>
> So, I built agents instead. Six of them. I published a preview post 
> that night, shared the repo, and went to bed.
>
> By Saturday morning, this thing had already outgrown what I imagined. 
> And it did not stop there.
>
> This Is Not Just Me
>
> I need to say this up front because it matters more than anything else 
> in this post.
>
> This is not my project anymore. It never should have been just mine. 
> The moment it stopped being one person yelling into the void and 
> became a team of people building together, everything changed. The 
> scope changed. The quality changed. The ambition changed. The whole 
> thing became something I could not have built alone. And that is the 
> point.
>
> Accessibility has always been a community fight. One person cannot 
> cover every screen reader, every browser, every framework, every 
> assistive technology, every lived experience. That is why the project 
> moved to a GitHub organization called Community Access. That is why it 
> is MIT licensed. That is why it costs nothing. Because the more people 
> who touch this, the better it gets for the people who need it.
>
> Jeff
>
> Jeff Bishop and I were talking on Friday night. That is how this 
> started. I was venting about AI tools forgetting accessibility, and 
> Jeff was right there with me. We were already in the same conversation 
> when I published the preview post and shared the repo.
>
> By Saturday morning, Jeff was not just talking anymore. He was 
> building. I did not expect what happened next.
>
> Jeff did not open an issue or send a message saying nice work. He 
> started pushing code. Within hours he was deep in the codebase, moving 
> faster than I could keep up. By the end of Saturday, he had more 
> commits than I did.
>
> That is not an exaggeration. Look at the git log. Forty-three commits 
> from Jeff in five days. He saw what I was trying to do. He saw where 
> it needed to go. And he went there.
>
> Jeff is blind. Like me, he uses assistive technology every day. He is 
> not reviewing accessibility as an abstract checklist. He is living it. 
> When he builds an agent that enforces focus trapping in modals, it is 
> because he has been trapped in modals. When he writes rules for screen 
> reader announcements, it is because he has sat in silence waiting for 
> an announcement that never came.
>
> That shared experience is what made this work. We did not have to 
> convince each other that accessibility matters. We just had to build.
>
> The Hooks Problem
>
> Now let me explain hooks, because if you read my preview post on 
> Friday, I made hooks sound like the answer to everything. They were not.
>
> A hook in Claude Code is a script that fires every time you send a 
> prompt. Think of it like a checkpoint. Before the AI starts working, 
> the hook looks at what you asked and decides if extra rules should 
> apply. If the task involves UI code, the accessibility agents 
> activate. If it does not, they stay out of the way. That was the idea. 
> And on Friday night, it worked.
>
> The problem arose when we tried to make hooks work for everyone. Not 
> just me on my Mac. Everyone. On every platform and different Claude 
> Code version.
>
> Hooks are fragile. They break across platforms. The JSON schema kept 
> changing. PowerShell on Windows handled them differently than bash on 
> Mac and Linux. Some hooks fired when they should not have. Others did 
> not fire when they should have. We spent hours debugging output 
> formats, timeout issues, and schema mismatches.
>
> Jeff and I merged pull requests fixing hooks. A pull request is how 
> you propose a change to code on GitHub. Someone reviews it, approves 
> it, and it gets merged into the main project. We merged pull requests 
> fixing hooks. Then more pull requests fixing the fixes. Then more 
> fixing those. It was a cycle. Every time we thought we had it, 
> something else broke.
>
> On Tuesday, Jeff made a decision I did not expect. He removed all of 
> them. Every hook. Every hook file. Every hook reference in every 
> documentation file. Gone.
>
> He replaced them with something better. Instead of hooks intercepting 
> prompts, orchestrator agents now coordinate the team through explicit 
> contracts. Each agent returns structured output with confidence levels 
> so the next agent knows exactly what it is getting. Nothing gets lost 
> between steps because the contracts define exactly what goes in and 
> what comes out.
>
> It is cleaner. It is more reliable. And it works on every platform 
> without platform-specific debugging.
>
> That is the kind of decision that only happens when someone is deep 
> enough in the code to see the real problem. Jeff was deep enough by 
> Saturday afternoon.
>
> What It Was
>
> On Friday, Accessibility Agents was six agents in a personal GitHub 
> repo under my name. An accessibility lead, an ARIA specialist, a modal 
> specialist, a contrast master, a keyboard navigator, and a live region 
> controller. It supported Claude Code. That was it.
>
> What It Is Now
>
> Forty-seven agents across four teams. Three platforms. Fourteen shared 
> knowledge modules. Fifty-two pre-built prompts. A GitHub organization. 
> A dedicated website. One command to install.
>
> The web accessibility team alone has sixteen agents. ARIA, modals, 
> contrast, keyboard navigation, live regions, forms, alt text and 
> headings, data tables, link text, cognitive accessibility, mobile 
> accessibility, design systems, guided audits, testing guidance, and 
> WCAG reference.
>
> There is a document scanning team that covers Word, Excel, PowerPoint, 
> PDF, and EPUB files. Forty-six built-in rules for Office documents. 
> Fifty-six for PDFs. It generates VPAT compliance reports. It exports 
> findings to CSV with links to help documentation so people know 
> exactly how to fix what it finds.
>
> There is a markdown documentation team that scans files across nine 
> accessibility domains.
>
> There is a GitHub workflow team with eleven agents for PR review, 
> issue triage, daily briefings, analytics, and repository management.
>
> It runs on Claude Code, GitHub Copilot, and Claude Desktop. It 
> installs with one command on macOS, Linux, and Windows. It is free. It 
> is MIT licensed. It costs nothing.
>
> Before Anyone Asks, No, This Is Not an Overlay
>
> I can already see the comment. Someone is going to read this post, see 
> forty-seven AI agents and the word accessibility in the same sentence, 
> and think: great, another magic fix. Another overlay. Another tool 
> that claims to solve accessibility so developers do not have to think 
> about it.
>
> No. Absolutely not. If you have read my writing before, you know how I 
> feel about overlays. One of them literally broke my rent portal so 
> badly that I could not pay rent until the landlord removed it. I have 
> written an entire post about why overlays are harmful. I am not about 
> to build one.
>
> Let me be crystal clear about what Accessibility Agents is and what it 
> is not.
>
> This is a developer tool. It runs inside your code editor while you 
> are writing code. It helps the AI write more accessible code from the 
> start. That is it. It does not touch your website. It does not add a 
> widget. It does not inject JavaScript into your pages. It does not 
> promise compliance. There is no toolbar. There is no badge. There is 
> no fee.
>
> And here is the part I really need you to hear. This does not replace 
> testing with real assistive technology. It does not replace VoiceOver. 
> It does not replace NVDA. It does not replace JAWS. It does not 
> replace a human being navigating your site with a keyboard and a 
> screen reader and telling you what is broken.
>
> What it does is raise the floor. Code that comes out of an AI tool 
> with these agents active is going to be more accessible than code that 
> comes out without them. Labels will be there. Focus trapping will be 
> there. ARIA roles will make sense instead of being scattered like 
> confetti. Contrast ratios will be checked before you ship, not after 
> someone files a complaint.
>
> That is not a magic fix. That is a better starting point. You still 
> need to test. You still need real users. You still need to care. But 
> at least you are not starting from zero every single time.
>
> If anyone tries to sell you a tool that replaces accessibility 
> testing, run. This is not that tool. This is the tool that makes the 
> code better before testing even begins.
>
> It Moved
>
> The project does not live under my personal GitHub account anymore. It 
> is at the Community Access organization now.
>
> That was deliberate. This is not my project. It is not Jeff’s project. 
> It is a community project. The more perspectives and lived experiences 
> that go into these agents, the better they serve the people who need them.
>
> Thirty Pull Requests in Five Days
>
> I keep coming back to this number because it tells the story better 
> than anything else I can say.
>
> Thirty pull requests merged in five days. That means thirty separate 
> changes were proposed, reviewed, and added to the project. Three 
> hundred and sixty files changed. Seventy-three thousand lines of code 
> added. Thirty-four security vulnerabilities identified and resolved. 
> Path traversal prevention. Injection protection. ZIP bomb limits. 
> Input validation at every call site.
>
> This was not a casual weekend project. This was a sprint. Jeff and I 
> were building in parallel, reviewing each other’s code, catching 
> issues, pushing fixes. The velocity was unlike anything I have 
> experienced on an open source project.
>
> And it happened because people who need accessible software decided to 
> stop waiting for someone else to build it.
>
> Why This Matters
>
> AI coding tools generate code at a speed and scale that humans never 
> could. If that code is inaccessible by default, the problem is not 
> getting smaller. It is getting bigger. Fast.
>
> Ninety-five point nine percent of the top one million websites already 
> have detectable accessibility failures. That number has barely moved 
> in years. AI tools risk making it worse by automating the same 
> mistakes at a scale no human team could match.
>
> I am a screen reader user. When AI generates a modal without focus 
> trapping, I am the person who gets stuck. When it skips live regions 
> on search results, I am the person who hears nothing. When it uses a 
> div with an onClick instead of a button, I am the person who cannot 
> activate it with my keyboard.
>
> But here is what I have learned over the past five days. I am not the 
> only one who feels this way. Jeff feels it. The people who starred the 
> repo and opened issues feel it. This is not one person’s frustration. 
> It is a shared experience across an entire community that has been 
> dealing with inaccessible software for decades.
>
> That is why this is not just me. That is why it cannot be just me. One 
> person’s agents catch one person’s blind spots. A community’s agents 
> catch the patterns that none of us would find alone.
>
> Version 2.0
>
> On Tuesday, Jeff and I got on a call and decided it was time. We were 
> going to release version 2.0.
>
> Five days earlier I had six agents and a personal repo. Now we had 
> forty-seven agents, three platforms, a GitHub organization, a website, 
> and a community. It was not a preview anymore. It was a release.
>
> We published the official announcement yesterday. You can read the 
> full press release on the Community Access website:
>
> https://community-access.github.io/news.html#post/accessibility-agents-v2-launch
>
> I am sharing it here because this community has followed this journey 
> from the beginning. You read the preview post on Friday. You saw the 
> Swift agent team launch. You have been here for the frustration and 
> the building and the breakthroughs. You deserve to see how it landed.
>
> Forty-seven agents. Three platforms. One command to install. Zero 
> cost. That is the headline. But the real story is that a community 
> built this in five days because the tools we depend on every day were 
> not building it for us.
>
> Be Part of This
>
> So now I am promoting it. And I am hoping you will try it out.
>
> I want to make this as easy as possible. You do not need to be a 
> developer to help. You do not need to write code. You do not need to 
> know what ARIA stands for. If you care about accessible software, 
> there is something you can do right now.
>
> Talk about it. Share the project with someone who builds software. 
> Post about it. Mention it in a conversation. The biggest thing holding 
> accessibility back is that not enough people know it is a problem. 
> Every time someone new hears about this project, that changes a little.
>
> Try it. Install it with one command. Use it on your next project. See 
> what it catches. See what it misses.
>
> If you find a bug, file it. Go to the GitHub repo, open an issue, and 
> describe what happened. What you expected. What you got instead. That 
> is it. A good bug report is one of the most valuable contributions 
> anyone can make. It does not take expertise. It takes honesty.
>
> If you want to contribute code, the agents are plain markdown files. 
> You do not need special tooling. You do not need permission. Fork it, 
> make a change, open a pull request. Jeff did exactly that on Saturday 
> morning and look where we are now.
>
> Website: https://community-access.github.io/
>
> GitHub: https://github.com/Community-Access/accessibility-agents
>
> Thank You
>
> To Jeff, for picking this up on Saturday morning and not putting it 
> down. For removing the hooks when I was still trying to fix them. For 
> writing forty-three commits in five days. For caring about this as 
> much as I do.
>
> To every contributor who showed up, opened a PR, filed an issue, or 
> starred the repo. You turned a frustrated Friday night into something 
> real.
>
> And to everyone reading this. If you build software, you have the 
> power to make it accessible. These agents are one way to start. But 
> they are not the finish line. They are the starting block.
>
> This is how it starts. Not with a company. Not with funding. With 
> people who got tired of fighting the same fight every day and decided 
> to build something that fights back.
>
> That is not just me. That is all of us.
>
>
> _______________________________________________
> NFBCS mailing list
> NFBCS at nfbnet.org
> http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org
> To unsubscribe, change your list options or get your account info for NFBCS:
> http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/tyler%40tysdomain.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://nfbnet.org/pipermail/nfbcs_nfbnet.org/attachments/20260225/24abba33/attachment.htm>

From lewislwood at gmail.com  Wed Feb 25 22:28:15 2026
From: lewislwood at gmail.com (Lewis Wood)
Date: Wed, 25 Feb 2026 16:28:15 -0600
Subject: [NFBCS] 6 Agents on Friday. 47 by Monday
In-Reply-To: <4c047723-a2ff-4c66-94ed-09dd7a11a78b@tysdomain.com>
References: <post-189168941@substack.com>
 <20260225183924.3.35f8d6578a430bc7@mg-d1.substack.com>
 <CYYPR02MB9901C9B543A7776D7D8150E5BA75A@CYYPR02MB9901.namprd02.prod.outlook.com>
 <CYYPR02MB9901175A68AA353241D2A90CBA75A@CYYPR02MB9901.namprd02.prod.outlook.com>
 <4c047723-a2ff-4c66-94ed-09dd7a11a78b@tysdomain.com>
Message-ID: <00fb01dca6a6$0972c250$1c5846f0$@gmail.com>

Not sure but I think these are skills and some agents.

 

I watched a video a few days ago, where claude moving to skills vs agaents.

 

MCP servers and some skills associated and accessible by other mcp/agents.  Seems like a great dream.

 

Here is the talk: (15 minutes)

https://www.youtube.com/watch?v=CEvIs9y1uog

 

 

Lewis Wood

 

 

 

From: NFBCS <nfbcs-bounces at nfbnet.org> On Behalf Of Ty Littlefield via NFBCS
Sent: Wednesday, February 25, 2026 3:45 PM
To: NFB in Computer Science Mailing List <nfbcs at nfbnet.org>
Cc: Ty Littlefield <tyler at tysdomain.com>
Subject: Re: [NFBCS] 6 Agents on Friday. 47 by Monday

 

This is a lot of agents, but my question from the other day still exists.

When Aria issues exist from AI code, it's not generally a context window issue for me. It's the fact that AI is outright incorrect about accessibility solutions. So, for example it might add an aria label of "main navigation" to a region with the nav tag, meaning that a screen reader will read "main navigation navigation region."

I'm curious how this is being tackled. We can throw all the agents we like at accessibility, and in the case of context windows this will be helpful, as it is in any type of code work--not just accessibility--but, my problem is less that the context windows slip and more that the information provided is incorrect.

 

How has this project been tested, and of those tests, how does more agents with context windows change the output?

Thanks,

 

 

Ty Littlefield (he/him/his)

*	From Bytes to Bites <https://tysdomain.com> | 
*	Linkedin <https://www.linkedin.com/in/ty-lerlittlefield/> |
*	Github <https://github.com/tlfdev> 

On 2/25/2026 12:50 PM, Jeff Bishop via NFBCS wrote:

Hello NFBCS Members,

 

Taylor and I are so excited about what this project has turned out to be … Visit the community site on Github, learn about the GIT Going with Github course that is happening on March 7th and 8th and get involved. We would love your input, engagement and most importantly your contributions.

 

Jeff Bishop

 

It is early Wednesday morning. February 26th. Something went so right over the past five days that my brain will not stop replaying it.

Let me take you back to Friday night.

 

How a Frustrated Friday Night Became a Movement

 

Friday Night on Discord

I was working on a project. I do not even remember what it was. Something with Claude Code, like most of my nights. And I was on a Discord call with some friends, just talking while I worked.

Then something happened in the code that just set me off.

ARIA roles placed wherever the model felt like putting them. No logic. No structure. Just ARIA sprayed across the page like decoration. Inputs without labels. Modals with no focus trapping. Divs pretending to be buttons. The same failures I have been correcting for months. Every single session.

I had enough.

I had enough of fixing ARIA by hand. I had enough of inaccessible code shipping as the default. I had enough of correcting these AIs over and over and getting the same broken output the next time I asked. You know the feeling. It is too much. At some point you stop asking nicely and you start building.

So that is what I did. I decided to build a team of AI agents. Not one model trying to remember everything. A team. Specialists. Each one responsible for one piece of accessibility that it cannot forget, because that is the only thing it knows.

I had no idea what I was getting into.

I was just trying to solve a problem for myself. I wanted Claude to actually write accessible code without me having to babysit every line. That is it. I did not set out to build a forty-seven agent system across three platforms with a GitHub organization and a website and a press release. I was just frustrated on a Friday night.

Of course, I tried other things first. I tried skills in Claude Code. They activate maybe 10 percent of the time without manual intervention. I tried writing detailed instructions in CLAUDE.md files. They work at first, but as the conversation grows, they drift. The model deprioritizes them. It decides other things matter more. Accessibility gets quietly dropped from the plan. Every time.

So, I built agents instead. Six of them. I published a preview post that night, shared the repo, and went to bed.

By Saturday morning, this thing had already outgrown what I imagined. And it did not stop there.

 

This Is Not Just Me

 

I need to say this up front because it matters more than anything else in this post.

This is not my project anymore. It never should have been just mine. The moment it stopped being one person yelling into the void and became a team of people building together, everything changed. The scope changed. The quality changed. The ambition changed. The whole thing became something I could not have built alone. And that is the point.

Accessibility has always been a community fight. One person cannot cover every screen reader, every browser, every framework, every assistive technology, every lived experience. That is why the project moved to a GitHub organization called Community Access. That is why it is MIT licensed. That is why it costs nothing. Because the more people who touch this, the better it gets for the people who need it.

 

Jeff

 

Jeff Bishop and I were talking on Friday night. That is how this started. I was venting about AI tools forgetting accessibility, and Jeff was right there with me. We were already in the same conversation when I published the preview post and shared the repo.

By Saturday morning, Jeff was not just talking anymore. He was building. I did not expect what happened next.

Jeff did not open an issue or send a message saying nice work. He started pushing code. Within hours he was deep in the codebase, moving faster than I could keep up. By the end of Saturday, he had more commits than I did.

That is not an exaggeration. Look at the git log. Forty-three commits from Jeff in five days. He saw what I was trying to do. He saw where it needed to go. And he went there.

Jeff is blind. Like me, he uses assistive technology every day. He is not reviewing accessibility as an abstract checklist. He is living it. When he builds an agent that enforces focus trapping in modals, it is because he has been trapped in modals. When he writes rules for screen reader announcements, it is because he has sat in silence waiting for an announcement that never came.

That shared experience is what made this work. We did not have to convince each other that accessibility matters. We just had to build.

 

The Hooks Problem

 

Now let me explain hooks, because if you read my preview post on Friday, I made hooks sound like the answer to everything. They were not.

A hook in Claude Code is a script that fires every time you send a prompt. Think of it like a checkpoint. Before the AI starts working, the hook looks at what you asked and decides if extra rules should apply. If the task involves UI code, the accessibility agents activate. If it does not, they stay out of the way. That was the idea. And on Friday night, it worked.

The problem arose when we tried to make hooks work for everyone. Not just me on my Mac. Everyone. On every platform and different Claude Code version.

Hooks are fragile. They break across platforms. The JSON schema kept changing. PowerShell on Windows handled them differently than bash on Mac and Linux. Some hooks fired when they should not have. Others did not fire when they should have. We spent hours debugging output formats, timeout issues, and schema mismatches.

Jeff and I merged pull requests fixing hooks. A pull request is how you propose a change to code on GitHub. Someone reviews it, approves it, and it gets merged into the main project. We merged pull requests fixing hooks. Then more pull requests fixing the fixes. Then more fixing those. It was a cycle. Every time we thought we had it, something else broke.

On Tuesday, Jeff made a decision I did not expect. He removed all of them. Every hook. Every hook file. Every hook reference in every documentation file. Gone.

He replaced them with something better. Instead of hooks intercepting prompts, orchestrator agents now coordinate the team through explicit contracts. Each agent returns structured output with confidence levels so the next agent knows exactly what it is getting. Nothing gets lost between steps because the contracts define exactly what goes in and what comes out.

It is cleaner. It is more reliable. And it works on every platform without platform-specific debugging.

That is the kind of decision that only happens when someone is deep enough in the code to see the real problem. Jeff was deep enough by Saturday afternoon.

 

What It Was

 

On Friday, Accessibility Agents was six agents in a personal GitHub repo under my name. An accessibility lead, an ARIA specialist, a modal specialist, a contrast master, a keyboard navigator, and a live region controller. It supported Claude Code. That was it.

 

What It Is Now

 

Forty-seven agents across four teams. Three platforms. Fourteen shared knowledge modules. Fifty-two pre-built prompts. A GitHub organization. A dedicated website. One command to install.

The web accessibility team alone has sixteen agents. ARIA, modals, contrast, keyboard navigation, live regions, forms, alt text and headings, data tables, link text, cognitive accessibility, mobile accessibility, design systems, guided audits, testing guidance, and WCAG reference.

There is a document scanning team that covers Word, Excel, PowerPoint, PDF, and EPUB files. Forty-six built-in rules for Office documents. Fifty-six for PDFs. It generates VPAT compliance reports. It exports findings to CSV with links to help documentation so people know exactly how to fix what it finds.

There is a markdown documentation team that scans files across nine accessibility domains.

There is a GitHub workflow team with eleven agents for PR review, issue triage, daily briefings, analytics, and repository management.

It runs on Claude Code, GitHub Copilot, and Claude Desktop. It installs with one command on macOS, Linux, and Windows. It is free. It is MIT licensed. It costs nothing.

 

Before Anyone Asks, No, This Is Not an Overlay

 

I can already see the comment. Someone is going to read this post, see forty-seven AI agents and the word accessibility in the same sentence, and think: great, another magic fix. Another overlay. Another tool that claims to solve accessibility so developers do not have to think about it.

No. Absolutely not. If you have read my writing before, you know how I feel about overlays. One of them literally broke my rent portal so badly that I could not pay rent until the landlord removed it. I have written an entire post about why overlays are harmful. I am not about to build one.

Let me be crystal clear about what Accessibility Agents is and what it is not.

This is a developer tool. It runs inside your code editor while you are writing code. It helps the AI write more accessible code from the start. That is it. It does not touch your website. It does not add a widget. It does not inject JavaScript into your pages. It does not promise compliance. There is no toolbar. There is no badge. There is no fee.

And here is the part I really need you to hear. This does not replace testing with real assistive technology. It does not replace VoiceOver. It does not replace NVDA. It does not replace JAWS. It does not replace a human being navigating your site with a keyboard and a screen reader and telling you what is broken.

What it does is raise the floor. Code that comes out of an AI tool with these agents active is going to be more accessible than code that comes out without them. Labels will be there. Focus trapping will be there. ARIA roles will make sense instead of being scattered like confetti. Contrast ratios will be checked before you ship, not after someone files a complaint.

That is not a magic fix. That is a better starting point. You still need to test. You still need real users. You still need to care. But at least you are not starting from zero every single time.

If anyone tries to sell you a tool that replaces accessibility testing, run. This is not that tool. This is the tool that makes the code better before testing even begins.

 

It Moved

 

The project does not live under my personal GitHub account anymore. It is at the Community Access organization now.

That was deliberate. This is not my project. It is not Jeff’s project. It is a community project. The more perspectives and lived experiences that go into these agents, the better they serve the people who need them.

 

Thirty Pull Requests in Five Days

 

I keep coming back to this number because it tells the story better than anything else I can say.

Thirty pull requests merged in five days. That means thirty separate changes were proposed, reviewed, and added to the project. Three hundred and sixty files changed. Seventy-three thousand lines of code added. Thirty-four security vulnerabilities identified and resolved. Path traversal prevention. Injection protection. ZIP bomb limits. Input validation at every call site.

This was not a casual weekend project. This was a sprint. Jeff and I were building in parallel, reviewing each other’s code, catching issues, pushing fixes. The velocity was unlike anything I have experienced on an open source project.

And it happened because people who need accessible software decided to stop waiting for someone else to build it.

 

Why This Matters

 

AI coding tools generate code at a speed and scale that humans never could. If that code is inaccessible by default, the problem is not getting smaller. It is getting bigger. Fast.

Ninety-five point nine percent of the top one million websites already have detectable accessibility failures. That number has barely moved in years. AI tools risk making it worse by automating the same mistakes at a scale no human team could match.

I am a screen reader user. When AI generates a modal without focus trapping, I am the person who gets stuck. When it skips live regions on search results, I am the person who hears nothing. When it uses a div with an onClick instead of a button, I am the person who cannot activate it with my keyboard.

But here is what I have learned over the past five days. I am not the only one who feels this way. Jeff feels it. The people who starred the repo and opened issues feel it. This is not one person’s frustration. It is a shared experience across an entire community that has been dealing with inaccessible software for decades.

That is why this is not just me. That is why it cannot be just me. One person’s agents catch one person’s blind spots. A community’s agents catch the patterns that none of us would find alone.

 

Version 2.0

 

On Tuesday, Jeff and I got on a call and decided it was time. We were going to release version 2.0.

Five days earlier I had six agents and a personal repo. Now we had forty-seven agents, three platforms, a GitHub organization, a website, and a community. It was not a preview anymore. It was a release.

We published the official announcement yesterday. You can read the full press release on the Community Access website:

 

https://community-access.github.io/news.html#post/accessibility-agents-v2-launch

 

I am sharing it here because this community has followed this journey from the beginning. You read the preview post on Friday. You saw the Swift agent team launch. You have been here for the frustration and the building and the breakthroughs. You deserve to see how it landed.

Forty-seven agents. Three platforms. One command to install. Zero cost. That is the headline. But the real story is that a community built this in five days because the tools we depend on every day were not building it for us.

 

Be Part of This

 

So now I am promoting it. And I am hoping you will try it out.

I want to make this as easy as possible. You do not need to be a developer to help. You do not need to write code. You do not need to know what ARIA stands for. If you care about accessible software, there is something you can do right now.

Talk about it. Share the project with someone who builds software. Post about it. Mention it in a conversation. The biggest thing holding accessibility back is that not enough people know it is a problem. Every time someone new hears about this project, that changes a little.

Try it. Install it with one command. Use it on your next project. See what it catches. See what it misses.

If you find a bug, file it. Go to the GitHub repo, open an issue, and describe what happened. What you expected. What you got instead. That is it. A good bug report is one of the most valuable contributions anyone can make. It does not take expertise. It takes honesty.

If you want to contribute code, the agents are plain markdown files. You do not need special tooling. You do not need permission. Fork it, make a change, open a pull request. Jeff did exactly that on Saturday morning and look where we are now.

 

Website: https://community-access.github.io/

GitHub: https://github.com/Community-Access/accessibility-agents

 

Thank You

 

To Jeff, for picking this up on Saturday morning and not putting it down. For removing the hooks when I was still trying to fix them. For writing forty-three commits in five days. For caring about this as much as I do.

To every contributor who showed up, opened a PR, filed an issue, or starred the repo. You turned a frustrated Friday night into something real.

And to everyone reading this. If you build software, you have the power to make it accessible. These agents are one way to start. But they are not the finish line. They are the starting block.

This is how it starts. Not with a company. Not with funding. With people who got tired of fighting the same fight every day and decided to build something that fights back.

That is not just me. That is all of us.

 

 





_______________________________________________
NFBCS mailing list
NFBCS at nfbnet.org <mailto:NFBCS at nfbnet.org> 
http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org
To unsubscribe, change your list options or get your account info for NFBCS:
http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/tyler%40tysdomain.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://nfbnet.org/pipermail/nfbcs_nfbnet.org/attachments/20260225/a3a90868/attachment.htm>

From jeff at jeffbishop.com  Wed Feb 25 22:31:17 2026
From: jeff at jeffbishop.com (Jeff Bishop)
Date: Wed, 25 Feb 2026 22:31:17 +0000
Subject: [NFBCS] 6 Agents on Friday. 47 by Monday
In-Reply-To: <4c047723-a2ff-4c66-94ed-09dd7a11a78b@tysdomain.com>
References: <post-189168941@substack.com>
 <20260225183924.3.35f8d6578a430bc7@mg-d1.substack.com>
 <CYYPR02MB9901C9B543A7776D7D8150E5BA75A@CYYPR02MB9901.namprd02.prod.outlook.com>
 <CYYPR02MB9901175A68AA353241D2A90CBA75A@CYYPR02MB9901.namprd02.prod.outlook.com>
 <4c047723-a2ff-4c66-94ed-09dd7a11a78b@tysdomain.com>
Message-ID: 
 <CYYPR02MB990124FCBF905B22B829D4E2BA75A@CYYPR02MB9901.namprd02.prod.outlook.com>

It is a journey … We are building and learning together as a community. We are utilizing the latest information on agentic knowledge to ensure that we have good orchestration across the agents and subagents. This was purposeful in the design. We are still testing, learning and evolving. Please consider joining us to make a difference. For example, we are already making a difference based on direct feedback from issue contributors and pull requests.

We know that automated technology is not always accurate and we make no claims in it being 100% accurate, in fact, we talk a lot about the human factor … Humans are always involved and drive with purpose. It is about additional detail and to give information as another data source. Tools like AXECore, Github Accessibility Scanner, Lighthouse and more are being utilized.

Jeff Bishop


From: Ty Littlefield <tyler at tysdomain.com>
Sent: Wednesday, February 25, 2026 2:45 PM
To: NFB in Computer Science Mailing List <nfbcs at nfbnet.org>
Cc: Jeff Bishop <jeff at jeffbishop.com>
Subject: Re: [NFBCS] 6 Agents on Friday. 47 by Monday


This is a lot of agents, but my question from the other day still exists.

When Aria issues exist from AI code, it's not generally a context window issue for me. It's the fact that AI is outright incorrect about accessibility solutions. So, for example it might add an aria label of "main navigation" to a region with the nav tag, meaning that a screen reader will read "main navigation navigation region."

I'm curious how this is being tackled. We can throw all the agents we like at accessibility, and in the case of context windows this will be helpful, as it is in any type of code work--not just accessibility--but, my problem is less that the context windows slip and more that the information provided is incorrect.



How has this project been tested, and of those tests, how does more agents with context windows change the output?

Thanks,





Ty Littlefield (he/him/his)

  *   From Bytes to Bites<https://tysdomain.com>|
  *   Linkedin<https://www.linkedin.com/in/ty-lerlittlefield/>|
  *   Github<https://github.com/tlfdev>
On 2/25/2026 12:50 PM, Jeff Bishop via NFBCS wrote:
Hello NFBCS Members,

Taylor and I are so excited about what this project has turned out to be … Visit the community site on Github, learn about the GIT Going with Github course that is happening on March 7th and 8th and get involved. We would love your input, engagement and most importantly your contributions.

Jeff Bishop

It is early Wednesday morning. February 26th. Something went so right over the past five days that my brain will not stop replaying it.
Let me take you back to Friday night.

How a Frustrated Friday Night Became a Movement

Friday Night on Discord
I was working on a project. I do not even remember what it was. Something with Claude Code, like most of my nights. And I was on a Discord call with some friends, just talking while I worked.
Then something happened in the code that just set me off.
ARIA roles placed wherever the model felt like putting them. No logic. No structure. Just ARIA sprayed across the page like decoration. Inputs without labels. Modals with no focus trapping. Divs pretending to be buttons. The same failures I have been correcting for months. Every single session.
I had enough.
I had enough of fixing ARIA by hand. I had enough of inaccessible code shipping as the default. I had enough of correcting these AIs over and over and getting the same broken output the next time I asked. You know the feeling. It is too much. At some point you stop asking nicely and you start building.
So that is what I did. I decided to build a team of AI agents. Not one model trying to remember everything. A team. Specialists. Each one responsible for one piece of accessibility that it cannot forget, because that is the only thing it knows.
I had no idea what I was getting into.
I was just trying to solve a problem for myself. I wanted Claude to actually write accessible code without me having to babysit every line. That is it. I did not set out to build a forty-seven agent system across three platforms with a GitHub organization and a website and a press release. I was just frustrated on a Friday night.
Of course, I tried other things first. I tried skills in Claude Code. They activate maybe 10 percent of the time without manual intervention. I tried writing detailed instructions in CLAUDE.md files. They work at first, but as the conversation grows, they drift. The model deprioritizes them. It decides other things matter more. Accessibility gets quietly dropped from the plan. Every time.
So, I built agents instead. Six of them. I published a preview post that night, shared the repo, and went to bed.
By Saturday morning, this thing had already outgrown what I imagined. And it did not stop there.

This Is Not Just Me

I need to say this up front because it matters more than anything else in this post.
This is not my project anymore. It never should have been just mine. The moment it stopped being one person yelling into the void and became a team of people building together, everything changed. The scope changed. The quality changed. The ambition changed. The whole thing became something I could not have built alone. And that is the point.
Accessibility has always been a community fight. One person cannot cover every screen reader, every browser, every framework, every assistive technology, every lived experience. That is why the project moved to a GitHub organization called Community Access. That is why it is MIT licensed. That is why it costs nothing. Because the more people who touch this, the better it gets for the people who need it.

Jeff

Jeff Bishop and I were talking on Friday night. That is how this started. I was venting about AI tools forgetting accessibility, and Jeff was right there with me. We were already in the same conversation when I published the preview post and shared the repo.
By Saturday morning, Jeff was not just talking anymore. He was building. I did not expect what happened next.
Jeff did not open an issue or send a message saying nice work. He started pushing code. Within hours he was deep in the codebase, moving faster than I could keep up. By the end of Saturday, he had more commits than I did.
That is not an exaggeration. Look at the git log. Forty-three commits from Jeff in five days. He saw what I was trying to do. He saw where it needed to go. And he went there.
Jeff is blind. Like me, he uses assistive technology every day. He is not reviewing accessibility as an abstract checklist. He is living it. When he builds an agent that enforces focus trapping in modals, it is because he has been trapped in modals. When he writes rules for screen reader announcements, it is because he has sat in silence waiting for an announcement that never came.
That shared experience is what made this work. We did not have to convince each other that accessibility matters. We just had to build.

The Hooks Problem

Now let me explain hooks, because if you read my preview post on Friday, I made hooks sound like the answer to everything. They were not.
A hook in Claude Code is a script that fires every time you send a prompt. Think of it like a checkpoint. Before the AI starts working, the hook looks at what you asked and decides if extra rules should apply. If the task involves UI code, the accessibility agents activate. If it does not, they stay out of the way. That was the idea. And on Friday night, it worked.
The problem arose when we tried to make hooks work for everyone. Not just me on my Mac. Everyone. On every platform and different Claude Code version.
Hooks are fragile. They break across platforms. The JSON schema kept changing. PowerShell on Windows handled them differently than bash on Mac and Linux. Some hooks fired when they should not have. Others did not fire when they should have. We spent hours debugging output formats, timeout issues, and schema mismatches.
Jeff and I merged pull requests fixing hooks. A pull request is how you propose a change to code on GitHub. Someone reviews it, approves it, and it gets merged into the main project. We merged pull requests fixing hooks. Then more pull requests fixing the fixes. Then more fixing those. It was a cycle. Every time we thought we had it, something else broke.
On Tuesday, Jeff made a decision I did not expect. He removed all of them. Every hook. Every hook file. Every hook reference in every documentation file. Gone.
He replaced them with something better. Instead of hooks intercepting prompts, orchestrator agents now coordinate the team through explicit contracts. Each agent returns structured output with confidence levels so the next agent knows exactly what it is getting. Nothing gets lost between steps because the contracts define exactly what goes in and what comes out.
It is cleaner. It is more reliable. And it works on every platform without platform-specific debugging.
That is the kind of decision that only happens when someone is deep enough in the code to see the real problem. Jeff was deep enough by Saturday afternoon.

What It Was

On Friday, Accessibility Agents was six agents in a personal GitHub repo under my name. An accessibility lead, an ARIA specialist, a modal specialist, a contrast master, a keyboard navigator, and a live region controller. It supported Claude Code. That was it.

What It Is Now

Forty-seven agents across four teams. Three platforms. Fourteen shared knowledge modules. Fifty-two pre-built prompts. A GitHub organization. A dedicated website. One command to install.
The web accessibility team alone has sixteen agents. ARIA, modals, contrast, keyboard navigation, live regions, forms, alt text and headings, data tables, link text, cognitive accessibility, mobile accessibility, design systems, guided audits, testing guidance, and WCAG reference.
There is a document scanning team that covers Word, Excel, PowerPoint, PDF, and EPUB files. Forty-six built-in rules for Office documents. Fifty-six for PDFs. It generates VPAT compliance reports. It exports findings to CSV with links to help documentation so people know exactly how to fix what it finds.
There is a markdown documentation team that scans files across nine accessibility domains.
There is a GitHub workflow team with eleven agents for PR review, issue triage, daily briefings, analytics, and repository management.
It runs on Claude Code, GitHub Copilot, and Claude Desktop. It installs with one command on macOS, Linux, and Windows. It is free. It is MIT licensed. It costs nothing.

Before Anyone Asks, No, This Is Not an Overlay

I can already see the comment. Someone is going to read this post, see forty-seven AI agents and the word accessibility in the same sentence, and think: great, another magic fix. Another overlay. Another tool that claims to solve accessibility so developers do not have to think about it.
No. Absolutely not. If you have read my writing before, you know how I feel about overlays. One of them literally broke my rent portal so badly that I could not pay rent until the landlord removed it. I have written an entire post about why overlays are harmful. I am not about to build one.
Let me be crystal clear about what Accessibility Agents is and what it is not.
This is a developer tool. It runs inside your code editor while you are writing code. It helps the AI write more accessible code from the start. That is it. It does not touch your website. It does not add a widget. It does not inject JavaScript into your pages. It does not promise compliance. There is no toolbar. There is no badge. There is no fee.
And here is the part I really need you to hear. This does not replace testing with real assistive technology. It does not replace VoiceOver. It does not replace NVDA. It does not replace JAWS. It does not replace a human being navigating your site with a keyboard and a screen reader and telling you what is broken.
What it does is raise the floor. Code that comes out of an AI tool with these agents active is going to be more accessible than code that comes out without them. Labels will be there. Focus trapping will be there. ARIA roles will make sense instead of being scattered like confetti. Contrast ratios will be checked before you ship, not after someone files a complaint.
That is not a magic fix. That is a better starting point. You still need to test. You still need real users. You still need to care. But at least you are not starting from zero every single time.
If anyone tries to sell you a tool that replaces accessibility testing, run. This is not that tool. This is the tool that makes the code better before testing even begins.

It Moved

The project does not live under my personal GitHub account anymore. It is at the Community Access organization now.
That was deliberate. This is not my project. It is not Jeff’s project. It is a community project. The more perspectives and lived experiences that go into these agents, the better they serve the people who need them.

Thirty Pull Requests in Five Days

I keep coming back to this number because it tells the story better than anything else I can say.
Thirty pull requests merged in five days. That means thirty separate changes were proposed, reviewed, and added to the project. Three hundred and sixty files changed. Seventy-three thousand lines of code added. Thirty-four security vulnerabilities identified and resolved. Path traversal prevention. Injection protection. ZIP bomb limits. Input validation at every call site.
This was not a casual weekend project. This was a sprint. Jeff and I were building in parallel, reviewing each other’s code, catching issues, pushing fixes. The velocity was unlike anything I have experienced on an open source project.
And it happened because people who need accessible software decided to stop waiting for someone else to build it.

Why This Matters

AI coding tools generate code at a speed and scale that humans never could. If that code is inaccessible by default, the problem is not getting smaller. It is getting bigger. Fast.
Ninety-five point nine percent of the top one million websites already have detectable accessibility failures. That number has barely moved in years. AI tools risk making it worse by automating the same mistakes at a scale no human team could match.
I am a screen reader user. When AI generates a modal without focus trapping, I am the person who gets stuck. When it skips live regions on search results, I am the person who hears nothing. When it uses a div with an onClick instead of a button, I am the person who cannot activate it with my keyboard.
But here is what I have learned over the past five days. I am not the only one who feels this way. Jeff feels it. The people who starred the repo and opened issues feel it. This is not one person’s frustration. It is a shared experience across an entire community that has been dealing with inaccessible software for decades.
That is why this is not just me. That is why it cannot be just me. One person’s agents catch one person’s blind spots. A community’s agents catch the patterns that none of us would find alone.

Version 2.0

On Tuesday, Jeff and I got on a call and decided it was time. We were going to release version 2.0.
Five days earlier I had six agents and a personal repo. Now we had forty-seven agents, three platforms, a GitHub organization, a website, and a community. It was not a preview anymore. It was a release.
We published the official announcement yesterday. You can read the full press release on the Community Access website:

https://community-access.github.io/news.html#post/accessibility-agents-v2-launch

I am sharing it here because this community has followed this journey from the beginning. You read the preview post on Friday. You saw the Swift agent team launch. You have been here for the frustration and the building and the breakthroughs. You deserve to see how it landed.
Forty-seven agents. Three platforms. One command to install. Zero cost. That is the headline. But the real story is that a community built this in five days because the tools we depend on every day were not building it for us.

Be Part of This

So now I am promoting it. And I am hoping you will try it out.
I want to make this as easy as possible. You do not need to be a developer to help. You do not need to write code. You do not need to know what ARIA stands for. If you care about accessible software, there is something you can do right now.
Talk about it. Share the project with someone who builds software. Post about it. Mention it in a conversation. The biggest thing holding accessibility back is that not enough people know it is a problem. Every time someone new hears about this project, that changes a little.
Try it. Install it with one command. Use it on your next project. See what it catches. See what it misses.
If you find a bug, file it. Go to the GitHub repo, open an issue, and describe what happened. What you expected. What you got instead. That is it. A good bug report is one of the most valuable contributions anyone can make. It does not take expertise. It takes honesty.
If you want to contribute code, the agents are plain markdown files. You do not need special tooling. You do not need permission. Fork it, make a change, open a pull request. Jeff did exactly that on Saturday morning and look where we are now.

Website: https://community-access.github.io/
GitHub: https://github.com/Community-Access/accessibility-agents

Thank You

To Jeff, for picking this up on Saturday morning and not putting it down. For removing the hooks when I was still trying to fix them. For writing forty-three commits in five days. For caring about this as much as I do.
To every contributor who showed up, opened a PR, filed an issue, or starred the repo. You turned a frustrated Friday night into something real.
And to everyone reading this. If you build software, you have the power to make it accessible. These agents are one way to start. But they are not the finish line. They are the starting block.
This is how it starts. Not with a company. Not with funding. With people who got tired of fighting the same fight every day and decided to build something that fights back.
That is not just me. That is all of us.





_______________________________________________

NFBCS mailing list

NFBCS at nfbnet.org<mailto:NFBCS at nfbnet.org>

http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org

To unsubscribe, change your list options or get your account info for NFBCS:

http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/tyler%40tysdomain.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://nfbnet.org/pipermail/nfbcs_nfbnet.org/attachments/20260225/f18825d0/attachment-0001.htm>

From ntcarver at outlook.com  Wed Feb 25 22:38:20 2026
From: ntcarver at outlook.com (Noah Tobias Carver)
Date: Wed, 25 Feb 2026 22:38:20 +0000
Subject: [NFBCS] 6 Agents on Friday. 47 by Monday
In-Reply-To: 
 <CYYPR02MB9901175A68AA353241D2A90CBA75A@CYYPR02MB9901.namprd02.prod.outlook.com>
References: <post-189168941@substack.com>
 <20260225183924.3.35f8d6578a430bc7@mg-d1.substack.com>
 <CYYPR02MB9901C9B543A7776D7D8150E5BA75A@CYYPR02MB9901.namprd02.prod.outlook.com>
 <CYYPR02MB9901175A68AA353241D2A90CBA75A@CYYPR02MB9901.namprd02.prod.outlook.com>
Message-ID: 
 <PH0PR20MB994646413EE052FE21E89B45F3D775A@PH0PR20MB994646.namprd20.prod.outlook.com>

Hi all,

I respect the idea behind this, as an end user, I have to say that I don’t feel comfortable with the idea that AI is Now intruding into accessibility testing. I've tried vibe coded projects and I can't say I've been impressed. A human with actual subject matter experience outperforms a regurgitation  machine every time, and this project does not sit well with me.

Respectfully,
Noah

Noah Tobias Carver (He/Him)
Candidate, B.M. '27, Applied Music (Performance) -- Voice
Eastman School of Music, University of Rochester
President, Empire Chapter, National Federation of the Blind of New York State
For National Federation of the Blind Related Matters: +1 (207) 205-7303<tel:+12072057303>
For All Other Matters: +1 (207) 557-9143<file:///private/var/mobile/Containers/Shared/AppGroup/815878B4-D150-4C5D-B023-146CB53769B9/File%20Provider%20Storage/item%7C2%7C16D65D1039F08C40%2521s71c1eb40cd8b4d46aede957091f62174/+12075579143>
ntcarver at outlook.com<mailto:ntcarver at outlook.com>

On Feb 25, 2026, at 14:51, Jeff Bishop via NFBCS <nfbcs at nfbnet.org> wrote:

﻿
Hello NFBCS Members,

Taylor and I are so excited about what this project has turned out to be … Visit the community site on Github, learn about the GIT Going with Github course that is happening on March 7th and 8th and get involved. We would love your input, engagement and most importantly your contributions.

Jeff Bishop

It is early Wednesday morning. February 26th. Something went so right over the past five days that my brain will not stop replaying it.
Let me take you back to Friday night.

How a Frustrated Friday Night Became a Movement

Friday Night on Discord
I was working on a project. I do not even remember what it was. Something with Claude Code, like most of my nights. And I was on a Discord call with some friends, just talking while I worked.
Then something happened in the code that just set me off.
ARIA roles placed wherever the model felt like putting them. No logic. No structure. Just ARIA sprayed across the page like decoration. Inputs without labels. Modals with no focus trapping. Divs pretending to be buttons. The same failures I have been correcting for months. Every single session.
I had enough.
I had enough of fixing ARIA by hand. I had enough of inaccessible code shipping as the default. I had enough of correcting these AIs over and over and getting the same broken output the next time I asked. You know the feeling. It is too much. At some point you stop asking nicely and you start building.
So that is what I did. I decided to build a team of AI agents. Not one model trying to remember everything. A team. Specialists. Each one responsible for one piece of accessibility that it cannot forget, because that is the only thing it knows.
I had no idea what I was getting into.
I was just trying to solve a problem for myself. I wanted Claude to actually write accessible code without me having to babysit every line. That is it. I did not set out to build a forty-seven agent system across three platforms with a GitHub organization and a website and a press release. I was just frustrated on a Friday night.
Of course, I tried other things first. I tried skills in Claude Code. They activate maybe 10 percent of the time without manual intervention. I tried writing detailed instructions in CLAUDE.md files. They work at first, but as the conversation grows, they drift. The model deprioritizes them. It decides other things matter more. Accessibility gets quietly dropped from the plan. Every time.
So, I built agents instead. Six of them. I published a preview post that night, shared the repo, and went to bed.
By Saturday morning, this thing had already outgrown what I imagined. And it did not stop there.

This Is Not Just Me

I need to say this up front because it matters more than anything else in this post.
This is not my project anymore. It never should have been just mine. The moment it stopped being one person yelling into the void and became a team of people building together, everything changed. The scope changed. The quality changed. The ambition changed. The whole thing became something I could not have built alone. And that is the point.
Accessibility has always been a community fight. One person cannot cover every screen reader, every browser, every framework, every assistive technology, every lived experience. That is why the project moved to a GitHub organization called Community Access. That is why it is MIT licensed. That is why it costs nothing. Because the more people who touch this, the better it gets for the people who need it.

Jeff

Jeff Bishop and I were talking on Friday night. That is how this started. I was venting about AI tools forgetting accessibility, and Jeff was right there with me. We were already in the same conversation when I published the preview post and shared the repo.
By Saturday morning, Jeff was not just talking anymore. He was building. I did not expect what happened next.
Jeff did not open an issue or send a message saying nice work. He started pushing code. Within hours he was deep in the codebase, moving faster than I could keep up. By the end of Saturday, he had more commits than I did.
That is not an exaggeration. Look at the git log. Forty-three commits from Jeff in five days. He saw what I was trying to do. He saw where it needed to go. And he went there.
Jeff is blind. Like me, he uses assistive technology every day. He is not reviewing accessibility as an abstract checklist. He is living it. When he builds an agent that enforces focus trapping in modals, it is because he has been trapped in modals. When he writes rules for screen reader announcements, it is because he has sat in silence waiting for an announcement that never came.
That shared experience is what made this work. We did not have to convince each other that accessibility matters. We just had to build.

The Hooks Problem

Now let me explain hooks, because if you read my preview post on Friday, I made hooks sound like the answer to everything. They were not.
A hook in Claude Code is a script that fires every time you send a prompt. Think of it like a checkpoint. Before the AI starts working, the hook looks at what you asked and decides if extra rules should apply. If the task involves UI code, the accessibility agents activate. If it does not, they stay out of the way. That was the idea. And on Friday night, it worked.
The problem arose when we tried to make hooks work for everyone. Not just me on my Mac. Everyone. On every platform and different Claude Code version.
Hooks are fragile. They break across platforms. The JSON schema kept changing. PowerShell on Windows handled them differently than bash on Mac and Linux. Some hooks fired when they should not have. Others did not fire when they should have. We spent hours debugging output formats, timeout issues, and schema mismatches.
Jeff and I merged pull requests fixing hooks. A pull request is how you propose a change to code on GitHub. Someone reviews it, approves it, and it gets merged into the main project. We merged pull requests fixing hooks. Then more pull requests fixing the fixes. Then more fixing those. It was a cycle. Every time we thought we had it, something else broke.
On Tuesday, Jeff made a decision I did not expect. He removed all of them. Every hook. Every hook file. Every hook reference in every documentation file. Gone.
He replaced them with something better. Instead of hooks intercepting prompts, orchestrator agents now coordinate the team through explicit contracts. Each agent returns structured output with confidence levels so the next agent knows exactly what it is getting. Nothing gets lost between steps because the contracts define exactly what goes in and what comes out.
It is cleaner. It is more reliable. And it works on every platform without platform-specific debugging.
That is the kind of decision that only happens when someone is deep enough in the code to see the real problem. Jeff was deep enough by Saturday afternoon.

What It Was

On Friday, Accessibility Agents was six agents in a personal GitHub repo under my name. An accessibility lead, an ARIA specialist, a modal specialist, a contrast master, a keyboard navigator, and a live region controller. It supported Claude Code. That was it.

What It Is Now

Forty-seven agents across four teams. Three platforms. Fourteen shared knowledge modules. Fifty-two pre-built prompts. A GitHub organization. A dedicated website. One command to install.
The web accessibility team alone has sixteen agents. ARIA, modals, contrast, keyboard navigation, live regions, forms, alt text and headings, data tables, link text, cognitive accessibility, mobile accessibility, design systems, guided audits, testing guidance, and WCAG reference.
There is a document scanning team that covers Word, Excel, PowerPoint, PDF, and EPUB files. Forty-six built-in rules for Office documents. Fifty-six for PDFs. It generates VPAT compliance reports. It exports findings to CSV with links to help documentation so people know exactly how to fix what it finds.
There is a markdown documentation team that scans files across nine accessibility domains.
There is a GitHub workflow team with eleven agents for PR review, issue triage, daily briefings, analytics, and repository management.
It runs on Claude Code, GitHub Copilot, and Claude Desktop. It installs with one command on macOS, Linux, and Windows. It is free. It is MIT licensed. It costs nothing.

Before Anyone Asks, No, This Is Not an Overlay

I can already see the comment. Someone is going to read this post, see forty-seven AI agents and the word accessibility in the same sentence, and think: great, another magic fix. Another overlay. Another tool that claims to solve accessibility so developers do not have to think about it.
No. Absolutely not. If you have read my writing before, you know how I feel about overlays. One of them literally broke my rent portal so badly that I could not pay rent until the landlord removed it. I have written an entire post about why overlays are harmful. I am not about to build one.
Let me be crystal clear about what Accessibility Agents is and what it is not.
This is a developer tool. It runs inside your code editor while you are writing code. It helps the AI write more accessible code from the start. That is it. It does not touch your website. It does not add a widget. It does not inject JavaScript into your pages. It does not promise compliance. There is no toolbar. There is no badge. There is no fee.
And here is the part I really need you to hear. This does not replace testing with real assistive technology. It does not replace VoiceOver. It does not replace NVDA. It does not replace JAWS. It does not replace a human being navigating your site with a keyboard and a screen reader and telling you what is broken.
What it does is raise the floor. Code that comes out of an AI tool with these agents active is going to be more accessible than code that comes out without them. Labels will be there. Focus trapping will be there. ARIA roles will make sense instead of being scattered like confetti. Contrast ratios will be checked before you ship, not after someone files a complaint.
That is not a magic fix. That is a better starting point. You still need to test. You still need real users. You still need to care. But at least you are not starting from zero every single time.
If anyone tries to sell you a tool that replaces accessibility testing, run. This is not that tool. This is the tool that makes the code better before testing even begins.

It Moved

The project does not live under my personal GitHub account anymore. It is at the Community Access organization now.
That was deliberate. This is not my project. It is not Jeff’s project. It is a community project. The more perspectives and lived experiences that go into these agents, the better they serve the people who need them.

Thirty Pull Requests in Five Days

I keep coming back to this number because it tells the story better than anything else I can say.
Thirty pull requests merged in five days. That means thirty separate changes were proposed, reviewed, and added to the project. Three hundred and sixty files changed. Seventy-three thousand lines of code added. Thirty-four security vulnerabilities identified and resolved. Path traversal prevention. Injection protection. ZIP bomb limits. Input validation at every call site.
This was not a casual weekend project. This was a sprint. Jeff and I were building in parallel, reviewing each other’s code, catching issues, pushing fixes. The velocity was unlike anything I have experienced on an open source project.
And it happened because people who need accessible software decided to stop waiting for someone else to build it.

Why This Matters

AI coding tools generate code at a speed and scale that humans never could. If that code is inaccessible by default, the problem is not getting smaller. It is getting bigger. Fast.
Ninety-five point nine percent of the top one million websites already have detectable accessibility failures. That number has barely moved in years. AI tools risk making it worse by automating the same mistakes at a scale no human team could match.
I am a screen reader user. When AI generates a modal without focus trapping, I am the person who gets stuck. When it skips live regions on search results, I am the person who hears nothing. When it uses a div with an onClick instead of a button, I am the person who cannot activate it with my keyboard.
But here is what I have learned over the past five days. I am not the only one who feels this way. Jeff feels it. The people who starred the repo and opened issues feel it. This is not one person’s frustration. It is a shared experience across an entire community that has been dealing with inaccessible software for decades.
That is why this is not just me. That is why it cannot be just me. One person’s agents catch one person’s blind spots. A community’s agents catch the patterns that none of us would find alone.

Version 2.0

On Tuesday, Jeff and I got on a call and decided it was time. We were going to release version 2.0.
Five days earlier I had six agents and a personal repo. Now we had forty-seven agents, three platforms, a GitHub organization, a website, and a community. It was not a preview anymore. It was a release.
We published the official announcement yesterday. You can read the full press release on the Community Access website:

https://community-access.github.io/news.html#post/accessibility-agents-v2-launch

I am sharing it here because this community has followed this journey from the beginning. You read the preview post on Friday. You saw the Swift agent team launch. You have been here for the frustration and the building and the breakthroughs. You deserve to see how it landed.
Forty-seven agents. Three platforms. One command to install. Zero cost. That is the headline. But the real story is that a community built this in five days because the tools we depend on every day were not building it for us.

Be Part of This

So now I am promoting it. And I am hoping you will try it out.
I want to make this as easy as possible. You do not need to be a developer to help. You do not need to write code. You do not need to know what ARIA stands for. If you care about accessible software, there is something you can do right now.
Talk about it. Share the project with someone who builds software. Post about it. Mention it in a conversation. The biggest thing holding accessibility back is that not enough people know it is a problem. Every time someone new hears about this project, that changes a little.
Try it. Install it with one command. Use it on your next project. See what it catches. See what it misses.
If you find a bug, file it. Go to the GitHub repo, open an issue, and describe what happened. What you expected. What you got instead. That is it. A good bug report is one of the most valuable contributions anyone can make. It does not take expertise. It takes honesty.
If you want to contribute code, the agents are plain markdown files. You do not need special tooling. You do not need permission. Fork it, make a change, open a pull request. Jeff did exactly that on Saturday morning and look where we are now.

Website: https://community-access.github.io/
GitHub: https://github.com/Community-Access/accessibility-agents

Thank You

To Jeff, for picking this up on Saturday morning and not putting it down. For removing the hooks when I was still trying to fix them. For writing forty-three commits in five days. For caring about this as much as I do.
To every contributor who showed up, opened a PR, filed an issue, or starred the repo. You turned a frustrated Friday night into something real.
And to everyone reading this. If you build software, you have the power to make it accessible. These agents are one way to start. But they are not the finish line. They are the starting block.
This is how it starts. Not with a company. Not with funding. With people who got tired of fighting the same fight every day and decided to build something that fights back.
That is not just me. That is all of us.


_______________________________________________
NFBCS mailing list
NFBCS at nfbnet.org
http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org
To unsubscribe, change your list options or get your account info for NFBCS:
http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/ntcarver%40outlook.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://nfbnet.org/pipermail/nfbcs_nfbnet.org/attachments/20260225/0b358b04/attachment.htm>

From tyler at tysdomain.com  Wed Feb 25 22:42:58 2026
From: tyler at tysdomain.com (Ty Littlefield)
Date: Wed, 25 Feb 2026 15:42:58 -0700
Subject: [NFBCS] 6 Agents on Friday. 47 by Monday
In-Reply-To: 
 <CYYPR02MB9901175A68AA353241D2A90CBA75A@CYYPR02MB9901.namprd02.prod.outlook.com>
References: <post-189168941@substack.com>
 <20260225183924.3.35f8d6578a430bc7@mg-d1.substack.com>
 <CYYPR02MB9901C9B543A7776D7D8150E5BA75A@CYYPR02MB9901.namprd02.prod.outlook.com>
 <CYYPR02MB9901175A68AA353241D2A90CBA75A@CYYPR02MB9901.namprd02.prod.outlook.com>
Message-ID: <3916b311-b426-4370-97ce-141f943abc5f@tysdomain.com>

Sorry for the double email, but on thinking about this a bit more, I 
want to push back harder against this narrative.


I spend a lot of my time in the accessibility field. I work with people 
every day to help products become more accessible, and a lot of that 
work is nuanced discussion about design patterns, UX, and how to make 
everything functional regardless of ability.


I strongly believe that we should be using AI to make our lives better. 
It solves a lot of needs, and to outright ignore it is not the way to go.


That said, executives are trying to replace people like me. These are 
execs in companies who never have and never will use a screen reader. 
When putting out this type of content, I firmly believe that it does the 
entire community a disservice to suggest that exponentially increasing 
the number of agents somehow magically makes content more accessible and 
usable.


This reality is pretty obvious by going to the linked page, where there 
are a plethora of WCAG issues including the region label I mentioned in 
my prior email, regions being created where there should be none, and 
most notably a grid used for displaying information visually about the 
stats that is converted into one long line and not provided the proper 
aria roles to either display it as a table, or otherwise convert the 
information to a format that it can be more easily read.


If we're going to make claims that x agents solves accessibility 
concerns, they fall down rather quickly when a vibe coded page 
demonstrates most of the issues that professionals in this field often 
warn against and are fighting to solve every day.

Thanks,

*Ty Littlefield (he/him/his)*

  * From Bytes to Bites <https://tysdomain.com>|
  * Linkedin <https://www.linkedin.com/in/ty-lerlittlefield/>|
  * Github <https://github.com/tlfdev>

On 2/25/2026 12:50 PM, Jeff Bishop via NFBCS wrote:
> 6 Agents on Friday. 47 by Monday
>
> Hello NFBCS Members,
>
> Taylor and I are so excited about what this project has turned out to 
> be … Visit the community site on Github, learn about the GIT Going 
> with Github course that is happening on March 7^th and 8^th and get 
> involved. We would love your input, engagement and most importantly 
> your contributions.
>
> Jeff Bishop
>
> It is early Wednesday morning. February 26th. Something went so right 
> over the past five days that my brain will not stop replaying it.
>
> Let me take you back to Friday night.
>
> How a Frustrated Friday Night Became a Movement
>
> Friday Night on Discord
>
> I was working on a project. I do not even remember what it was. 
> Something with Claude Code, like most of my nights. And I was on a 
> Discord call with some friends, just talking while I worked.
>
> Then something happened in the code that just set me off.
>
> ARIA roles placed wherever the model felt like putting them. No logic. 
> No structure. Just ARIA sprayed across the page like decoration. 
> Inputs without labels. Modals with no focus trapping. Divs pretending 
> to be buttons. The same failures I have been correcting for months. 
> Every single session.
>
> I had enough.
>
> I had enough of fixing ARIA by hand. I had enough of inaccessible code 
> shipping as the default. I had enough of correcting these AIs over and 
> over and getting the same broken output the next time I asked. You 
> know the feeling. It is too much. At some point you stop asking nicely 
> and you start building.
>
> So that is what I did. I decided to build a team of AI agents. Not one 
> model trying to remember everything. A team. Specialists. Each one 
> responsible for one piece of accessibility that it cannot forget, 
> because that is the only thing it knows.
>
> I had no idea what I was getting into.
>
> I was just trying to solve a problem for myself. I wanted Claude to 
> actually write accessible code without me having to babysit every 
> line. That is it. I did not set out to build a forty-seven agent 
> system across three platforms with a GitHub organization and a website 
> and a press release. I was just frustrated on a Friday night.
>
> Of course, I tried other things first. I tried skills in Claude Code. 
> They activate maybe 10 percent of the time without manual 
> intervention. I tried writing detailed instructions in CLAUDE.md 
> files. They work at first, but as the conversation grows, they drift. 
> The model deprioritizes them. It decides other things matter more. 
> Accessibility gets quietly dropped from the plan. Every time.
>
> So, I built agents instead. Six of them. I published a preview post 
> that night, shared the repo, and went to bed.
>
> By Saturday morning, this thing had already outgrown what I imagined. 
> And it did not stop there.
>
> This Is Not Just Me
>
> I need to say this up front because it matters more than anything else 
> in this post.
>
> This is not my project anymore. It never should have been just mine. 
> The moment it stopped being one person yelling into the void and 
> became a team of people building together, everything changed. The 
> scope changed. The quality changed. The ambition changed. The whole 
> thing became something I could not have built alone. And that is the 
> point.
>
> Accessibility has always been a community fight. One person cannot 
> cover every screen reader, every browser, every framework, every 
> assistive technology, every lived experience. That is why the project 
> moved to a GitHub organization called Community Access. That is why it 
> is MIT licensed. That is why it costs nothing. Because the more people 
> who touch this, the better it gets for the people who need it.
>
> Jeff
>
> Jeff Bishop and I were talking on Friday night. That is how this 
> started. I was venting about AI tools forgetting accessibility, and 
> Jeff was right there with me. We were already in the same conversation 
> when I published the preview post and shared the repo.
>
> By Saturday morning, Jeff was not just talking anymore. He was 
> building. I did not expect what happened next.
>
> Jeff did not open an issue or send a message saying nice work. He 
> started pushing code. Within hours he was deep in the codebase, moving 
> faster than I could keep up. By the end of Saturday, he had more 
> commits than I did.
>
> That is not an exaggeration. Look at the git log. Forty-three commits 
> from Jeff in five days. He saw what I was trying to do. He saw where 
> it needed to go. And he went there.
>
> Jeff is blind. Like me, he uses assistive technology every day. He is 
> not reviewing accessibility as an abstract checklist. He is living it. 
> When he builds an agent that enforces focus trapping in modals, it is 
> because he has been trapped in modals. When he writes rules for screen 
> reader announcements, it is because he has sat in silence waiting for 
> an announcement that never came.
>
> That shared experience is what made this work. We did not have to 
> convince each other that accessibility matters. We just had to build.
>
> The Hooks Problem
>
> Now let me explain hooks, because if you read my preview post on 
> Friday, I made hooks sound like the answer to everything. They were not.
>
> A hook in Claude Code is a script that fires every time you send a 
> prompt. Think of it like a checkpoint. Before the AI starts working, 
> the hook looks at what you asked and decides if extra rules should 
> apply. If the task involves UI code, the accessibility agents 
> activate. If it does not, they stay out of the way. That was the idea. 
> And on Friday night, it worked.
>
> The problem arose when we tried to make hooks work for everyone. Not 
> just me on my Mac. Everyone. On every platform and different Claude 
> Code version.
>
> Hooks are fragile. They break across platforms. The JSON schema kept 
> changing. PowerShell on Windows handled them differently than bash on 
> Mac and Linux. Some hooks fired when they should not have. Others did 
> not fire when they should have. We spent hours debugging output 
> formats, timeout issues, and schema mismatches.
>
> Jeff and I merged pull requests fixing hooks. A pull request is how 
> you propose a change to code on GitHub. Someone reviews it, approves 
> it, and it gets merged into the main project. We merged pull requests 
> fixing hooks. Then more pull requests fixing the fixes. Then more 
> fixing those. It was a cycle. Every time we thought we had it, 
> something else broke.
>
> On Tuesday, Jeff made a decision I did not expect. He removed all of 
> them. Every hook. Every hook file. Every hook reference in every 
> documentation file. Gone.
>
> He replaced them with something better. Instead of hooks intercepting 
> prompts, orchestrator agents now coordinate the team through explicit 
> contracts. Each agent returns structured output with confidence levels 
> so the next agent knows exactly what it is getting. Nothing gets lost 
> between steps because the contracts define exactly what goes in and 
> what comes out.
>
> It is cleaner. It is more reliable. And it works on every platform 
> without platform-specific debugging.
>
> That is the kind of decision that only happens when someone is deep 
> enough in the code to see the real problem. Jeff was deep enough by 
> Saturday afternoon.
>
> What It Was
>
> On Friday, Accessibility Agents was six agents in a personal GitHub 
> repo under my name. An accessibility lead, an ARIA specialist, a modal 
> specialist, a contrast master, a keyboard navigator, and a live region 
> controller. It supported Claude Code. That was it.
>
> What It Is Now
>
> Forty-seven agents across four teams. Three platforms. Fourteen shared 
> knowledge modules. Fifty-two pre-built prompts. A GitHub organization. 
> A dedicated website. One command to install.
>
> The web accessibility team alone has sixteen agents. ARIA, modals, 
> contrast, keyboard navigation, live regions, forms, alt text and 
> headings, data tables, link text, cognitive accessibility, mobile 
> accessibility, design systems, guided audits, testing guidance, and 
> WCAG reference.
>
> There is a document scanning team that covers Word, Excel, PowerPoint, 
> PDF, and EPUB files. Forty-six built-in rules for Office documents. 
> Fifty-six for PDFs. It generates VPAT compliance reports. It exports 
> findings to CSV with links to help documentation so people know 
> exactly how to fix what it finds.
>
> There is a markdown documentation team that scans files across nine 
> accessibility domains.
>
> There is a GitHub workflow team with eleven agents for PR review, 
> issue triage, daily briefings, analytics, and repository management.
>
> It runs on Claude Code, GitHub Copilot, and Claude Desktop. It 
> installs with one command on macOS, Linux, and Windows. It is free. It 
> is MIT licensed. It costs nothing.
>
> Before Anyone Asks, No, This Is Not an Overlay
>
> I can already see the comment. Someone is going to read this post, see 
> forty-seven AI agents and the word accessibility in the same sentence, 
> and think: great, another magic fix. Another overlay. Another tool 
> that claims to solve accessibility so developers do not have to think 
> about it.
>
> No. Absolutely not. If you have read my writing before, you know how I 
> feel about overlays. One of them literally broke my rent portal so 
> badly that I could not pay rent until the landlord removed it. I have 
> written an entire post about why overlays are harmful. I am not about 
> to build one.
>
> Let me be crystal clear about what Accessibility Agents is and what it 
> is not.
>
> This is a developer tool. It runs inside your code editor while you 
> are writing code. It helps the AI write more accessible code from the 
> start. That is it. It does not touch your website. It does not add a 
> widget. It does not inject JavaScript into your pages. It does not 
> promise compliance. There is no toolbar. There is no badge. There is 
> no fee.
>
> And here is the part I really need you to hear. This does not replace 
> testing with real assistive technology. It does not replace VoiceOver. 
> It does not replace NVDA. It does not replace JAWS. It does not 
> replace a human being navigating your site with a keyboard and a 
> screen reader and telling you what is broken.
>
> What it does is raise the floor. Code that comes out of an AI tool 
> with these agents active is going to be more accessible than code that 
> comes out without them. Labels will be there. Focus trapping will be 
> there. ARIA roles will make sense instead of being scattered like 
> confetti. Contrast ratios will be checked before you ship, not after 
> someone files a complaint.
>
> That is not a magic fix. That is a better starting point. You still 
> need to test. You still need real users. You still need to care. But 
> at least you are not starting from zero every single time.
>
> If anyone tries to sell you a tool that replaces accessibility 
> testing, run. This is not that tool. This is the tool that makes the 
> code better before testing even begins.
>
> It Moved
>
> The project does not live under my personal GitHub account anymore. It 
> is at the Community Access organization now.
>
> That was deliberate. This is not my project. It is not Jeff’s project. 
> It is a community project. The more perspectives and lived experiences 
> that go into these agents, the better they serve the people who need them.
>
> Thirty Pull Requests in Five Days
>
> I keep coming back to this number because it tells the story better 
> than anything else I can say.
>
> Thirty pull requests merged in five days. That means thirty separate 
> changes were proposed, reviewed, and added to the project. Three 
> hundred and sixty files changed. Seventy-three thousand lines of code 
> added. Thirty-four security vulnerabilities identified and resolved. 
> Path traversal prevention. Injection protection. ZIP bomb limits. 
> Input validation at every call site.
>
> This was not a casual weekend project. This was a sprint. Jeff and I 
> were building in parallel, reviewing each other’s code, catching 
> issues, pushing fixes. The velocity was unlike anything I have 
> experienced on an open source project.
>
> And it happened because people who need accessible software decided to 
> stop waiting for someone else to build it.
>
> Why This Matters
>
> AI coding tools generate code at a speed and scale that humans never 
> could. If that code is inaccessible by default, the problem is not 
> getting smaller. It is getting bigger. Fast.
>
> Ninety-five point nine percent of the top one million websites already 
> have detectable accessibility failures. That number has barely moved 
> in years. AI tools risk making it worse by automating the same 
> mistakes at a scale no human team could match.
>
> I am a screen reader user. When AI generates a modal without focus 
> trapping, I am the person who gets stuck. When it skips live regions 
> on search results, I am the person who hears nothing. When it uses a 
> div with an onClick instead of a button, I am the person who cannot 
> activate it with my keyboard.
>
> But here is what I have learned over the past five days. I am not the 
> only one who feels this way. Jeff feels it. The people who starred the 
> repo and opened issues feel it. This is not one person’s frustration. 
> It is a shared experience across an entire community that has been 
> dealing with inaccessible software for decades.
>
> That is why this is not just me. That is why it cannot be just me. One 
> person’s agents catch one person’s blind spots. A community’s agents 
> catch the patterns that none of us would find alone.
>
> Version 2.0
>
> On Tuesday, Jeff and I got on a call and decided it was time. We were 
> going to release version 2.0.
>
> Five days earlier I had six agents and a personal repo. Now we had 
> forty-seven agents, three platforms, a GitHub organization, a website, 
> and a community. It was not a preview anymore. It was a release.
>
> We published the official announcement yesterday. You can read the 
> full press release on the Community Access website:
>
> https://community-access.github.io/news.html#post/accessibility-agents-v2-launch
>
> I am sharing it here because this community has followed this journey 
> from the beginning. You read the preview post on Friday. You saw the 
> Swift agent team launch. You have been here for the frustration and 
> the building and the breakthroughs. You deserve to see how it landed.
>
> Forty-seven agents. Three platforms. One command to install. Zero 
> cost. That is the headline. But the real story is that a community 
> built this in five days because the tools we depend on every day were 
> not building it for us.
>
> Be Part of This
>
> So now I am promoting it. And I am hoping you will try it out.
>
> I want to make this as easy as possible. You do not need to be a 
> developer to help. You do not need to write code. You do not need to 
> know what ARIA stands for. If you care about accessible software, 
> there is something you can do right now.
>
> Talk about it. Share the project with someone who builds software. 
> Post about it. Mention it in a conversation. The biggest thing holding 
> accessibility back is that not enough people know it is a problem. 
> Every time someone new hears about this project, that changes a little.
>
> Try it. Install it with one command. Use it on your next project. See 
> what it catches. See what it misses.
>
> If you find a bug, file it. Go to the GitHub repo, open an issue, and 
> describe what happened. What you expected. What you got instead. That 
> is it. A good bug report is one of the most valuable contributions 
> anyone can make. It does not take expertise. It takes honesty.
>
> If you want to contribute code, the agents are plain markdown files. 
> You do not need special tooling. You do not need permission. Fork it, 
> make a change, open a pull request. Jeff did exactly that on Saturday 
> morning and look where we are now.
>
> Website: https://community-access.github.io/
>
> GitHub: https://github.com/Community-Access/accessibility-agents
>
> Thank You
>
> To Jeff, for picking this up on Saturday morning and not putting it 
> down. For removing the hooks when I was still trying to fix them. For 
> writing forty-three commits in five days. For caring about this as 
> much as I do.
>
> To every contributor who showed up, opened a PR, filed an issue, or 
> starred the repo. You turned a frustrated Friday night into something 
> real.
>
> And to everyone reading this. If you build software, you have the 
> power to make it accessible. These agents are one way to start. But 
> they are not the finish line. They are the starting block.
>
> This is how it starts. Not with a company. Not with funding. With 
> people who got tired of fighting the same fight every day and decided 
> to build something that fights back.
>
> That is not just me. That is all of us.
>
>
> _______________________________________________
> NFBCS mailing list
> NFBCS at nfbnet.org
> http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org
> To unsubscribe, change your list options or get your account info for NFBCS:
> http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/tyler%40tysdomain.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://nfbnet.org/pipermail/nfbcs_nfbnet.org/attachments/20260225/120374cc/attachment.htm>

From jeff at jeffbishop.com  Wed Feb 25 23:16:18 2026
From: jeff at jeffbishop.com (Jeff Bishop)
Date: Wed, 25 Feb 2026 23:16:18 +0000
Subject: [NFBCS] 6 Agents on Friday. 47 by Monday
In-Reply-To: <3916b311-b426-4370-97ce-141f943abc5f@tysdomain.com>
References: <post-189168941@substack.com>
 <20260225183924.3.35f8d6578a430bc7@mg-d1.substack.com>
 <CYYPR02MB9901C9B543A7776D7D8150E5BA75A@CYYPR02MB9901.namprd02.prod.outlook.com>
 <CYYPR02MB9901175A68AA353241D2A90CBA75A@CYYPR02MB9901.namprd02.prod.outlook.com>
 <3916b311-b426-4370-97ce-141f943abc5f@tysdomain.com>
Message-ID: 
 <CYYPR02MB9901368263090F531D378513BA75A@CYYPR02MB9901.namprd02.prod.outlook.com>

As a professional in this space myself I hear you and understand it and even agree with much of what you are saying. Again, this is about a community driven effort and not a single minded effort to try and make a difference.

From: Ty Littlefield <tyler at tysdomain.com>
Sent: Wednesday, February 25, 2026 3:43 PM
To: NFB in Computer Science Mailing List <nfbcs at nfbnet.org>
Cc: Jeff Bishop <jeff at jeffbishop.com>
Subject: Re: [NFBCS] 6 Agents on Friday. 47 by Monday


Sorry for the double email, but on thinking about this a bit more, I want to push back harder against this narrative.



I spend a lot of my time in the accessibility field. I work with people every day to help products become more accessible, and a lot of that work is nuanced discussion about design patterns, UX, and how to make everything functional regardless of ability.



I strongly believe that we should be using AI to make our lives better. It solves a lot of needs, and to outright ignore it is not the way to go.



That said, executives are trying to replace people like me. These are execs in companies who never have and never will use a screen reader. When putting out this type of content, I firmly believe that it does the entire community a disservice to suggest that exponentially increasing the number of agents somehow magically makes content more accessible and usable.



This reality is pretty obvious by going to the linked page, where there are a plethora of WCAG issues including the region label I mentioned in my prior email, regions being created where there should be none, and most notably a grid used for displaying information visually about the stats that is converted into one long line and not provided the proper aria roles to either display it as a table, or otherwise convert the information to a format that it can be more easily read.



If we're going to make claims that x agents solves accessibility concerns, they fall down rather quickly when a vibe coded page demonstrates most of the issues that professionals in this field often warn against and are fighting to solve every day.

Thanks,

Ty Littlefield (he/him/his)

  *   From Bytes to Bites<https://tysdomain.com>|
  *   Linkedin<https://www.linkedin.com/in/ty-lerlittlefield/>|
  *   Github<https://github.com/tlfdev>
On 2/25/2026 12:50 PM, Jeff Bishop via NFBCS wrote:
Hello NFBCS Members,

Taylor and I are so excited about what this project has turned out to be … Visit the community site on Github, learn about the GIT Going with Github course that is happening on March 7th and 8th and get involved. We would love your input, engagement and most importantly your contributions.

Jeff Bishop

It is early Wednesday morning. February 26th. Something went so right over the past five days that my brain will not stop replaying it.
Let me take you back to Friday night.

How a Frustrated Friday Night Became a Movement

Friday Night on Discord
I was working on a project. I do not even remember what it was. Something with Claude Code, like most of my nights. And I was on a Discord call with some friends, just talking while I worked.
Then something happened in the code that just set me off.
ARIA roles placed wherever the model felt like putting them. No logic. No structure. Just ARIA sprayed across the page like decoration. Inputs without labels. Modals with no focus trapping. Divs pretending to be buttons. The same failures I have been correcting for months. Every single session.
I had enough.
I had enough of fixing ARIA by hand. I had enough of inaccessible code shipping as the default. I had enough of correcting these AIs over and over and getting the same broken output the next time I asked. You know the feeling. It is too much. At some point you stop asking nicely and you start building.
So that is what I did. I decided to build a team of AI agents. Not one model trying to remember everything. A team. Specialists. Each one responsible for one piece of accessibility that it cannot forget, because that is the only thing it knows.
I had no idea what I was getting into.
I was just trying to solve a problem for myself. I wanted Claude to actually write accessible code without me having to babysit every line. That is it. I did not set out to build a forty-seven agent system across three platforms with a GitHub organization and a website and a press release. I was just frustrated on a Friday night.
Of course, I tried other things first. I tried skills in Claude Code. They activate maybe 10 percent of the time without manual intervention. I tried writing detailed instructions in CLAUDE.md files. They work at first, but as the conversation grows, they drift. The model deprioritizes them. It decides other things matter more. Accessibility gets quietly dropped from the plan. Every time.
So, I built agents instead. Six of them. I published a preview post that night, shared the repo, and went to bed.
By Saturday morning, this thing had already outgrown what I imagined. And it did not stop there.

This Is Not Just Me

I need to say this up front because it matters more than anything else in this post.
This is not my project anymore. It never should have been just mine. The moment it stopped being one person yelling into the void and became a team of people building together, everything changed. The scope changed. The quality changed. The ambition changed. The whole thing became something I could not have built alone. And that is the point.
Accessibility has always been a community fight. One person cannot cover every screen reader, every browser, every framework, every assistive technology, every lived experience. That is why the project moved to a GitHub organization called Community Access. That is why it is MIT licensed. That is why it costs nothing. Because the more people who touch this, the better it gets for the people who need it.

Jeff

Jeff Bishop and I were talking on Friday night. That is how this started. I was venting about AI tools forgetting accessibility, and Jeff was right there with me. We were already in the same conversation when I published the preview post and shared the repo.
By Saturday morning, Jeff was not just talking anymore. He was building. I did not expect what happened next.
Jeff did not open an issue or send a message saying nice work. He started pushing code. Within hours he was deep in the codebase, moving faster than I could keep up. By the end of Saturday, he had more commits than I did.
That is not an exaggeration. Look at the git log. Forty-three commits from Jeff in five days. He saw what I was trying to do. He saw where it needed to go. And he went there.
Jeff is blind. Like me, he uses assistive technology every day. He is not reviewing accessibility as an abstract checklist. He is living it. When he builds an agent that enforces focus trapping in modals, it is because he has been trapped in modals. When he writes rules for screen reader announcements, it is because he has sat in silence waiting for an announcement that never came.
That shared experience is what made this work. We did not have to convince each other that accessibility matters. We just had to build.

The Hooks Problem

Now let me explain hooks, because if you read my preview post on Friday, I made hooks sound like the answer to everything. They were not.
A hook in Claude Code is a script that fires every time you send a prompt. Think of it like a checkpoint. Before the AI starts working, the hook looks at what you asked and decides if extra rules should apply. If the task involves UI code, the accessibility agents activate. If it does not, they stay out of the way. That was the idea. And on Friday night, it worked.
The problem arose when we tried to make hooks work for everyone. Not just me on my Mac. Everyone. On every platform and different Claude Code version.
Hooks are fragile. They break across platforms. The JSON schema kept changing. PowerShell on Windows handled them differently than bash on Mac and Linux. Some hooks fired when they should not have. Others did not fire when they should have. We spent hours debugging output formats, timeout issues, and schema mismatches.
Jeff and I merged pull requests fixing hooks. A pull request is how you propose a change to code on GitHub. Someone reviews it, approves it, and it gets merged into the main project. We merged pull requests fixing hooks. Then more pull requests fixing the fixes. Then more fixing those. It was a cycle. Every time we thought we had it, something else broke.
On Tuesday, Jeff made a decision I did not expect. He removed all of them. Every hook. Every hook file. Every hook reference in every documentation file. Gone.
He replaced them with something better. Instead of hooks intercepting prompts, orchestrator agents now coordinate the team through explicit contracts. Each agent returns structured output with confidence levels so the next agent knows exactly what it is getting. Nothing gets lost between steps because the contracts define exactly what goes in and what comes out.
It is cleaner. It is more reliable. And it works on every platform without platform-specific debugging.
That is the kind of decision that only happens when someone is deep enough in the code to see the real problem. Jeff was deep enough by Saturday afternoon.

What It Was

On Friday, Accessibility Agents was six agents in a personal GitHub repo under my name. An accessibility lead, an ARIA specialist, a modal specialist, a contrast master, a keyboard navigator, and a live region controller. It supported Claude Code. That was it.

What It Is Now

Forty-seven agents across four teams. Three platforms. Fourteen shared knowledge modules. Fifty-two pre-built prompts. A GitHub organization. A dedicated website. One command to install.
The web accessibility team alone has sixteen agents. ARIA, modals, contrast, keyboard navigation, live regions, forms, alt text and headings, data tables, link text, cognitive accessibility, mobile accessibility, design systems, guided audits, testing guidance, and WCAG reference.
There is a document scanning team that covers Word, Excel, PowerPoint, PDF, and EPUB files. Forty-six built-in rules for Office documents. Fifty-six for PDFs. It generates VPAT compliance reports. It exports findings to CSV with links to help documentation so people know exactly how to fix what it finds.
There is a markdown documentation team that scans files across nine accessibility domains.
There is a GitHub workflow team with eleven agents for PR review, issue triage, daily briefings, analytics, and repository management.
It runs on Claude Code, GitHub Copilot, and Claude Desktop. It installs with one command on macOS, Linux, and Windows. It is free. It is MIT licensed. It costs nothing.

Before Anyone Asks, No, This Is Not an Overlay

I can already see the comment. Someone is going to read this post, see forty-seven AI agents and the word accessibility in the same sentence, and think: great, another magic fix. Another overlay. Another tool that claims to solve accessibility so developers do not have to think about it.
No. Absolutely not. If you have read my writing before, you know how I feel about overlays. One of them literally broke my rent portal so badly that I could not pay rent until the landlord removed it. I have written an entire post about why overlays are harmful. I am not about to build one.
Let me be crystal clear about what Accessibility Agents is and what it is not.
This is a developer tool. It runs inside your code editor while you are writing code. It helps the AI write more accessible code from the start. That is it. It does not touch your website. It does not add a widget. It does not inject JavaScript into your pages. It does not promise compliance. There is no toolbar. There is no badge. There is no fee.
And here is the part I really need you to hear. This does not replace testing with real assistive technology. It does not replace VoiceOver. It does not replace NVDA. It does not replace JAWS. It does not replace a human being navigating your site with a keyboard and a screen reader and telling you what is broken.
What it does is raise the floor. Code that comes out of an AI tool with these agents active is going to be more accessible than code that comes out without them. Labels will be there. Focus trapping will be there. ARIA roles will make sense instead of being scattered like confetti. Contrast ratios will be checked before you ship, not after someone files a complaint.
That is not a magic fix. That is a better starting point. You still need to test. You still need real users. You still need to care. But at least you are not starting from zero every single time.
If anyone tries to sell you a tool that replaces accessibility testing, run. This is not that tool. This is the tool that makes the code better before testing even begins.

It Moved

The project does not live under my personal GitHub account anymore. It is at the Community Access organization now.
That was deliberate. This is not my project. It is not Jeff’s project. It is a community project. The more perspectives and lived experiences that go into these agents, the better they serve the people who need them.

Thirty Pull Requests in Five Days

I keep coming back to this number because it tells the story better than anything else I can say.
Thirty pull requests merged in five days. That means thirty separate changes were proposed, reviewed, and added to the project. Three hundred and sixty files changed. Seventy-three thousand lines of code added. Thirty-four security vulnerabilities identified and resolved. Path traversal prevention. Injection protection. ZIP bomb limits. Input validation at every call site.
This was not a casual weekend project. This was a sprint. Jeff and I were building in parallel, reviewing each other’s code, catching issues, pushing fixes. The velocity was unlike anything I have experienced on an open source project.
And it happened because people who need accessible software decided to stop waiting for someone else to build it.

Why This Matters

AI coding tools generate code at a speed and scale that humans never could. If that code is inaccessible by default, the problem is not getting smaller. It is getting bigger. Fast.
Ninety-five point nine percent of the top one million websites already have detectable accessibility failures. That number has barely moved in years. AI tools risk making it worse by automating the same mistakes at a scale no human team could match.
I am a screen reader user. When AI generates a modal without focus trapping, I am the person who gets stuck. When it skips live regions on search results, I am the person who hears nothing. When it uses a div with an onClick instead of a button, I am the person who cannot activate it with my keyboard.
But here is what I have learned over the past five days. I am not the only one who feels this way. Jeff feels it. The people who starred the repo and opened issues feel it. This is not one person’s frustration. It is a shared experience across an entire community that has been dealing with inaccessible software for decades.
That is why this is not just me. That is why it cannot be just me. One person’s agents catch one person’s blind spots. A community’s agents catch the patterns that none of us would find alone.

Version 2.0

On Tuesday, Jeff and I got on a call and decided it was time. We were going to release version 2.0.
Five days earlier I had six agents and a personal repo. Now we had forty-seven agents, three platforms, a GitHub organization, a website, and a community. It was not a preview anymore. It was a release.
We published the official announcement yesterday. You can read the full press release on the Community Access website:

https://community-access.github.io/news.html#post/accessibility-agents-v2-launch

I am sharing it here because this community has followed this journey from the beginning. You read the preview post on Friday. You saw the Swift agent team launch. You have been here for the frustration and the building and the breakthroughs. You deserve to see how it landed.
Forty-seven agents. Three platforms. One command to install. Zero cost. That is the headline. But the real story is that a community built this in five days because the tools we depend on every day were not building it for us.

Be Part of This

So now I am promoting it. And I am hoping you will try it out.
I want to make this as easy as possible. You do not need to be a developer to help. You do not need to write code. You do not need to know what ARIA stands for. If you care about accessible software, there is something you can do right now.
Talk about it. Share the project with someone who builds software. Post about it. Mention it in a conversation. The biggest thing holding accessibility back is that not enough people know it is a problem. Every time someone new hears about this project, that changes a little.
Try it. Install it with one command. Use it on your next project. See what it catches. See what it misses.
If you find a bug, file it. Go to the GitHub repo, open an issue, and describe what happened. What you expected. What you got instead. That is it. A good bug report is one of the most valuable contributions anyone can make. It does not take expertise. It takes honesty.
If you want to contribute code, the agents are plain markdown files. You do not need special tooling. You do not need permission. Fork it, make a change, open a pull request. Jeff did exactly that on Saturday morning and look where we are now.

Website: https://community-access.github.io/
GitHub: https://github.com/Community-Access/accessibility-agents

Thank You

To Jeff, for picking this up on Saturday morning and not putting it down. For removing the hooks when I was still trying to fix them. For writing forty-three commits in five days. For caring about this as much as I do.
To every contributor who showed up, opened a PR, filed an issue, or starred the repo. You turned a frustrated Friday night into something real.
And to everyone reading this. If you build software, you have the power to make it accessible. These agents are one way to start. But they are not the finish line. They are the starting block.
This is how it starts. Not with a company. Not with funding. With people who got tired of fighting the same fight every day and decided to build something that fights back.
That is not just me. That is all of us.





_______________________________________________

NFBCS mailing list

NFBCS at nfbnet.org<mailto:NFBCS at nfbnet.org>

http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org

To unsubscribe, change your list options or get your account info for NFBCS:

http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/tyler%40tysdomain.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://nfbnet.org/pipermail/nfbcs_nfbnet.org/attachments/20260225/09d487fd/attachment.htm>

From buddy at brannan.name  Wed Feb 25 23:44:57 2026
From: buddy at brannan.name (Buddy Brannan)
Date: Wed, 25 Feb 2026 18:44:57 -0500
Subject: [NFBCS] 6 Agents on Friday. 47 by Monday
In-Reply-To: 
 <CYYPR02MB9901368263090F531D378513BA75A@CYYPR02MB9901.namprd02.prod.outlook.com>
References: <post-189168941@substack.com>
 <20260225183924.3.35f8d6578a430bc7@mg-d1.substack.com>
 <CYYPR02MB9901C9B543A7776D7D8150E5BA75A@CYYPR02MB9901.namprd02.prod.outlook.com>
 <CYYPR02MB9901175A68AA353241D2A90CBA75A@CYYPR02MB9901.namprd02.prod.outlook.com>
 <3916b311-b426-4370-97ce-141f943abc5f@tysdomain.com>
 <CYYPR02MB9901368263090F531D378513BA75A@CYYPR02MB9901.namprd02.prod.outlook.com>
Message-ID: <894C6CD8-6592-4A43-8C26-26C7B031F6F9@brannan.name>

More to the point, yes, I agree that there are problems with AI and accessibility, even when it’s prompted to minimize those. But I think it’s also important to understand that two things can be true at once:
* AI is not necessarily great at accessibility, and it isn’t ready to take on those sorts of tasks independently.
* AI can be used to do this work, even though it requires more human oversight.

In general, walk before you run, crawl before you walk. And AI is still crawling. But AI will never walk, let alone run, until it gets beyond the crawling stage, which it will never do if we don’t take those incremental steps in training and optimizing and doing everything we can to get closer to the results we want. 


--
Buddy Brannan, KB5ELV, WRVB670 - Erie, PA
Email: buddy at brannan.name
Mobile: (814) 431-0962



> On Feb 25, 2026, at 6:16 PM, Jeff Bishop via NFBCS <nfbcs at nfbnet.org> wrote:
> 
> As a professional in this space myself I hear you and understand it and even agree with much of what you are saying. Again, this is about a community driven effort and not a single minded effort to try and make a difference.
>  
> From: Ty Littlefield <tyler at tysdomain.com <mailto:tyler at tysdomain.com>>
> Sent: Wednesday, February 25, 2026 3:43 PM
> To: NFB in Computer Science Mailing List <nfbcs at nfbnet.org <mailto:nfbcs at nfbnet.org>>
> Cc: Jeff Bishop <jeff at jeffbishop.com <mailto:jeff at jeffbishop.com>>
> Subject: Re: [NFBCS] 6 Agents on Friday. 47 by Monday
>  
> Sorry for the double email, but on thinking about this a bit more, I want to push back harder against this narrative.
> 
>  
> 
> I spend a lot of my time in the accessibility field. I work with people every day to help products become more accessible, and a lot of that work is nuanced discussion about design patterns, UX, and how to make everything functional regardless of ability.
> 
>  
> 
> I strongly believe that we should be using AI to make our lives better. It solves a lot of needs, and to outright ignore it is not the way to go.
> 
>  
> 
> That said, executives are trying to replace people like me. These are execs in companies who never have and never will use a screen reader. When putting out this type of content, I firmly believe that it does the entire community a disservice to suggest that exponentially increasing the number of agents somehow magically makes content more accessible and usable.
> 
>  
> 
> This reality is pretty obvious by going to the linked page, where there are a plethora of WCAG issues including the region label I mentioned in my prior email, regions being created where there should be none, and most notably a grid used for displaying information visually about the stats that is converted into one long line and not provided the proper aria roles to either display it as a table, or otherwise convert the information to a format that it can be more easily read.
> 
>  
> 
> If we're going to make claims that x agents solves accessibility concerns, they fall down rather quickly when a vibe coded page demonstrates most of the issues that professionals in this field often warn against and are fighting to solve every day.
> 
> Thanks,
> 
> Ty Littlefield (he/him/his)
> 
> From Bytes to Bites <https://tysdomain.com/>| 
> Linkedin <https://www.linkedin.com/in/ty-lerlittlefield/>|
> Github <https://github.com/tlfdev>
> On 2/25/2026 12:50 PM, Jeff Bishop via NFBCS wrote:
> Hello NFBCS Members,
>  
> Taylor and I are so excited about what this project has turned out to be … Visit the community site on Github, learn about the GIT Going with Github course that is happening on March 7th and 8th and get involved. We would love your input, engagement and most importantly your contributions.
>  
> Jeff Bishop
>  
> It is early Wednesday morning. February 26th. Something went so right over the past five days that my brain will not stop replaying it.
> Let me take you back to Friday night.
>  
> How a Frustrated Friday Night Became a Movement
>  
> Friday Night on Discord
> I was working on a project. I do not even remember what it was. Something with Claude Code, like most of my nights. And I was on a Discord call with some friends, just talking while I worked.
> Then something happened in the code that just set me off.
> ARIA roles placed wherever the model felt like putting them. No logic. No structure. Just ARIA sprayed across the page like decoration. Inputs without labels. Modals with no focus trapping. Divs pretending to be buttons. The same failures I have been correcting for months. Every single session.
> I had enough.
> I had enough of fixing ARIA by hand. I had enough of inaccessible code shipping as the default. I had enough of correcting these AIs over and over and getting the same broken output the next time I asked. You know the feeling. It is too much. At some point you stop asking nicely and you start building.
> So that is what I did. I decided to build a team of AI agents. Not one model trying to remember everything. A team. Specialists. Each one responsible for one piece of accessibility that it cannot forget, because that is the only thing it knows.
> I had no idea what I was getting into.
> I was just trying to solve a problem for myself. I wanted Claude to actually write accessible code without me having to babysit every line. That is it. I did not set out to build a forty-seven agent system across three platforms with a GitHub organization and a website and a press release. I was just frustrated on a Friday night.
> Of course, I tried other things first. I tried skills in Claude Code. They activate maybe 10 percent of the time without manual intervention. I tried writing detailed instructions in CLAUDE.md files. They work at first, but as the conversation grows, they drift. The model deprioritizes them. It decides other things matter more. Accessibility gets quietly dropped from the plan. Every time.
> So, I built agents instead. Six of them. I published a preview post that night, shared the repo, and went to bed.
> By Saturday morning, this thing had already outgrown what I imagined. And it did not stop there.
>  
> This Is Not Just Me
>  
> I need to say this up front because it matters more than anything else in this post.
> This is not my project anymore. It never should have been just mine. The moment it stopped being one person yelling into the void and became a team of people building together, everything changed. The scope changed. The quality changed. The ambition changed. The whole thing became something I could not have built alone. And that is the point.
> Accessibility has always been a community fight. One person cannot cover every screen reader, every browser, every framework, every assistive technology, every lived experience. That is why the project moved to a GitHub organization called Community Access. That is why it is MIT licensed. That is why it costs nothing. Because the more people who touch this, the better it gets for the people who need it.
>  
> Jeff
>  
> Jeff Bishop and I were talking on Friday night. That is how this started. I was venting about AI tools forgetting accessibility, and Jeff was right there with me. We were already in the same conversation when I published the preview post and shared the repo.
> By Saturday morning, Jeff was not just talking anymore. He was building. I did not expect what happened next.
> Jeff did not open an issue or send a message saying nice work. He started pushing code. Within hours he was deep in the codebase, moving faster than I could keep up. By the end of Saturday, he had more commits than I did.
> That is not an exaggeration. Look at the git log. Forty-three commits from Jeff in five days. He saw what I was trying to do. He saw where it needed to go. And he went there.
> Jeff is blind. Like me, he uses assistive technology every day. He is not reviewing accessibility as an abstract checklist. He is living it. When he builds an agent that enforces focus trapping in modals, it is because he has been trapped in modals. When he writes rules for screen reader announcements, it is because he has sat in silence waiting for an announcement that never came.
> That shared experience is what made this work. We did not have to convince each other that accessibility matters. We just had to build.
>  
> The Hooks Problem
>  
> Now let me explain hooks, because if you read my preview post on Friday, I made hooks sound like the answer to everything. They were not.
> A hook in Claude Code is a script that fires every time you send a prompt. Think of it like a checkpoint. Before the AI starts working, the hook looks at what you asked and decides if extra rules should apply. If the task involves UI code, the accessibility agents activate. If it does not, they stay out of the way. That was the idea. And on Friday night, it worked.
> The problem arose when we tried to make hooks work for everyone. Not just me on my Mac. Everyone. On every platform and different Claude Code version.
> Hooks are fragile. They break across platforms. The JSON schema kept changing. PowerShell on Windows handled them differently than bash on Mac and Linux. Some hooks fired when they should not have. Others did not fire when they should have. We spent hours debugging output formats, timeout issues, and schema mismatches.
> Jeff and I merged pull requests fixing hooks. A pull request is how you propose a change to code on GitHub. Someone reviews it, approves it, and it gets merged into the main project. We merged pull requests fixing hooks. Then more pull requests fixing the fixes. Then more fixing those. It was a cycle. Every time we thought we had it, something else broke.
> On Tuesday, Jeff made a decision I did not expect. He removed all of them. Every hook. Every hook file. Every hook reference in every documentation file. Gone.
> He replaced them with something better. Instead of hooks intercepting prompts, orchestrator agents now coordinate the team through explicit contracts. Each agent returns structured output with confidence levels so the next agent knows exactly what it is getting. Nothing gets lost between steps because the contracts define exactly what goes in and what comes out.
> It is cleaner. It is more reliable. And it works on every platform without platform-specific debugging.
> That is the kind of decision that only happens when someone is deep enough in the code to see the real problem. Jeff was deep enough by Saturday afternoon.
>  
> What It Was
>  
> On Friday, Accessibility Agents was six agents in a personal GitHub repo under my name. An accessibility lead, an ARIA specialist, a modal specialist, a contrast master, a keyboard navigator, and a live region controller. It supported Claude Code. That was it.
>  
> What It Is Now
>  
> Forty-seven agents across four teams. Three platforms. Fourteen shared knowledge modules. Fifty-two pre-built prompts. A GitHub organization. A dedicated website. One command to install.
> The web accessibility team alone has sixteen agents. ARIA, modals, contrast, keyboard navigation, live regions, forms, alt text and headings, data tables, link text, cognitive accessibility, mobile accessibility, design systems, guided audits, testing guidance, and WCAG reference.
> There is a document scanning team that covers Word, Excel, PowerPoint, PDF, and EPUB files. Forty-six built-in rules for Office documents. Fifty-six for PDFs. It generates VPAT compliance reports. It exports findings to CSV with links to help documentation so people know exactly how to fix what it finds.
> There is a markdown documentation team that scans files across nine accessibility domains.
> There is a GitHub workflow team with eleven agents for PR review, issue triage, daily briefings, analytics, and repository management.
> It runs on Claude Code, GitHub Copilot, and Claude Desktop. It installs with one command on macOS, Linux, and Windows. It is free. It is MIT licensed. It costs nothing.
>  
> Before Anyone Asks, No, This Is Not an Overlay
>  
> I can already see the comment. Someone is going to read this post, see forty-seven AI agents and the word accessibility in the same sentence, and think: great, another magic fix. Another overlay. Another tool that claims to solve accessibility so developers do not have to think about it.
> No. Absolutely not. If you have read my writing before, you know how I feel about overlays. One of them literally broke my rent portal so badly that I could not pay rent until the landlord removed it. I have written an entire post about why overlays are harmful. I am not about to build one.
> Let me be crystal clear about what Accessibility Agents is and what it is not.
> This is a developer tool. It runs inside your code editor while you are writing code. It helps the AI write more accessible code from the start. That is it. It does not touch your website. It does not add a widget. It does not inject JavaScript into your pages. It does not promise compliance. There is no toolbar. There is no badge. There is no fee.
> And here is the part I really need you to hear. This does not replace testing with real assistive technology. It does not replace VoiceOver. It does not replace NVDA. It does not replace JAWS. It does not replace a human being navigating your site with a keyboard and a screen reader and telling you what is broken.
> What it does is raise the floor. Code that comes out of an AI tool with these agents active is going to be more accessible than code that comes out without them. Labels will be there. Focus trapping will be there. ARIA roles will make sense instead of being scattered like confetti. Contrast ratios will be checked before you ship, not after someone files a complaint.
> That is not a magic fix. That is a better starting point. You still need to test. You still need real users. You still need to care. But at least you are not starting from zero every single time.
> If anyone tries to sell you a tool that replaces accessibility testing, run. This is not that tool. This is the tool that makes the code better before testing even begins.
>  
> It Moved
>  
> The project does not live under my personal GitHub account anymore. It is at the Community Access organization now.
> That was deliberate. This is not my project. It is not Jeff’s project. It is a community project. The more perspectives and lived experiences that go into these agents, the better they serve the people who need them.
>  
> Thirty Pull Requests in Five Days
>  
> I keep coming back to this number because it tells the story better than anything else I can say.
> Thirty pull requests merged in five days. That means thirty separate changes were proposed, reviewed, and added to the project. Three hundred and sixty files changed. Seventy-three thousand lines of code added. Thirty-four security vulnerabilities identified and resolved. Path traversal prevention. Injection protection. ZIP bomb limits. Input validation at every call site.
> This was not a casual weekend project. This was a sprint. Jeff and I were building in parallel, reviewing each other’s code, catching issues, pushing fixes. The velocity was unlike anything I have experienced on an open source project.
> And it happened because people who need accessible software decided to stop waiting for someone else to build it.
>  
> Why This Matters
>  
> AI coding tools generate code at a speed and scale that humans never could. If that code is inaccessible by default, the problem is not getting smaller. It is getting bigger. Fast.
> Ninety-five point nine percent of the top one million websites already have detectable accessibility failures. That number has barely moved in years. AI tools risk making it worse by automating the same mistakes at a scale no human team could match.
> I am a screen reader user. When AI generates a modal without focus trapping, I am the person who gets stuck. When it skips live regions on search results, I am the person who hears nothing. When it uses a div with an onClick instead of a button, I am the person who cannot activate it with my keyboard.
> But here is what I have learned over the past five days. I am not the only one who feels this way. Jeff feels it. The people who starred the repo and opened issues feel it. This is not one person’s frustration. It is a shared experience across an entire community that has been dealing with inaccessible software for decades.
> That is why this is not just me. That is why it cannot be just me. One person’s agents catch one person’s blind spots. A community’s agents catch the patterns that none of us would find alone.
>  
> Version 2.0
>  
> On Tuesday, Jeff and I got on a call and decided it was time. We were going to release version 2.0.
> Five days earlier I had six agents and a personal repo. Now we had forty-seven agents, three platforms, a GitHub organization, a website, and a community. It was not a preview anymore. It was a release.
> We published the official announcement yesterday. You can read the full press release on the Community Access website:
>  
> https://community-access.github.io/news.html#post/accessibility-agents-v2-launch
>  
> I am sharing it here because this community has followed this journey from the beginning. You read the preview post on Friday. You saw the Swift agent team launch. You have been here for the frustration and the building and the breakthroughs. You deserve to see how it landed.
> Forty-seven agents. Three platforms. One command to install. Zero cost. That is the headline. But the real story is that a community built this in five days because the tools we depend on every day were not building it for us.
>  
> Be Part of This
>  
> So now I am promoting it. And I am hoping you will try it out.
> I want to make this as easy as possible. You do not need to be a developer to help. You do not need to write code. You do not need to know what ARIA stands for. If you care about accessible software, there is something you can do right now.
> Talk about it. Share the project with someone who builds software. Post about it. Mention it in a conversation. The biggest thing holding accessibility back is that not enough people know it is a problem. Every time someone new hears about this project, that changes a little.
> Try it. Install it with one command. Use it on your next project. See what it catches. See what it misses.
> If you find a bug, file it. Go to the GitHub repo, open an issue, and describe what happened. What you expected. What you got instead. That is it. A good bug report is one of the most valuable contributions anyone can make. It does not take expertise. It takes honesty.
> If you want to contribute code, the agents are plain markdown files. You do not need special tooling. You do not need permission. Fork it, make a change, open a pull request. Jeff did exactly that on Saturday morning and look where we are now.
>  
> Website: https://community-access.github.io/
> GitHub: https://github.com/Community-Access/accessibility-agents
>  
> Thank You
>  
> To Jeff, for picking this up on Saturday morning and not putting it down. For removing the hooks when I was still trying to fix them. For writing forty-three commits in five days. For caring about this as much as I do.
> To every contributor who showed up, opened a PR, filed an issue, or starred the repo. You turned a frustrated Friday night into something real.
> And to everyone reading this. If you build software, you have the power to make it accessible. These agents are one way to start. But they are not the finish line. They are the starting block.
> This is how it starts. Not with a company. Not with funding. With people who got tired of fighting the same fight every day and decided to build something that fights back.
> That is not just me. That is all of us.
>  
>  
> 
> 
> _______________________________________________
> NFBCS mailing list
> NFBCS at nfbnet.org <mailto:NFBCS at nfbnet.org>
> http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org
> To unsubscribe, change your list options or get your account info for NFBCS:
> http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/tyler%40tysdomain.com
> _______________________________________________
> NFBCS mailing list
> NFBCS at nfbnet.org <mailto:NFBCS at nfbnet.org>
> http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org
> To unsubscribe, change your list options or get your account info for NFBCS:
> http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/buddy%40brannan.name

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://nfbnet.org/pipermail/nfbcs_nfbnet.org/attachments/20260225/6f25f6ac/attachment-0001.htm>

From jeff at jeffbishop.com  Wed Feb 25 23:46:25 2026
From: jeff at jeffbishop.com (Jeff Bishop)
Date: Wed, 25 Feb 2026 23:46:25 +0000
Subject: [NFBCS] 6 Agents on Friday. 47 by Monday
In-Reply-To: <894C6CD8-6592-4A43-8C26-26C7B031F6F9@brannan.name>
References: <post-189168941@substack.com>
 <20260225183924.3.35f8d6578a430bc7@mg-d1.substack.com>
 <CYYPR02MB9901C9B543A7776D7D8150E5BA75A@CYYPR02MB9901.namprd02.prod.outlook.com>
 <CYYPR02MB9901175A68AA353241D2A90CBA75A@CYYPR02MB9901.namprd02.prod.outlook.com>
 <3916b311-b426-4370-97ce-141f943abc5f@tysdomain.com>
 <CYYPR02MB9901368263090F531D378513BA75A@CYYPR02MB9901.namprd02.prod.outlook.com>
 <894C6CD8-6592-4A43-8C26-26C7B031F6F9@brannan.name>
Message-ID: 
 <CYYPR02MB990182666CC2C4B37B5D0945BA75A@CYYPR02MB9901.namprd02.prod.outlook.com>

This is spot on Buddy. Thank you for this.

From: Buddy Brannan <buddy at brannan.name>
Sent: Wednesday, February 25, 2026 4:45 PM
To: NFB in Computer Science Mailing List <nfbcs at nfbnet.org>
Cc: Ty Littlefield <tyler at tysdomain.com>; Jeff Bishop <jeff at jeffbishop.com>
Subject: Re: [NFBCS] 6 Agents on Friday. 47 by Monday

More to the point, yes, I agree that there are problems with AI and accessibility, even when it’s prompted to minimize those. But I think it’s also important to understand that two things can be true at once:
* AI is not necessarily great at accessibility, and it isn’t ready to take on those sorts of tasks independently.
* AI can be used to do this work, even though it requires more human oversight.

In general, walk before you run, crawl before you walk. And AI is still crawling. But AI will never walk, let alone run, until it gets beyond the crawling stage, which it will never do if we don’t take those incremental steps in training and optimizing and doing everything we can to get closer to the results we want.


--
Buddy Brannan, KB5ELV, WRVB670 - Erie, PA
Email: buddy at brannan.name<mailto:buddy at brannan.name>
Mobile: (814) 431-0962



On Feb 25, 2026, at 6:16 PM, Jeff Bishop via NFBCS <nfbcs at nfbnet.org<mailto:nfbcs at nfbnet.org>> wrote:

As a professional in this space myself I hear you and understand it and even agree with much of what you are saying. Again, this is about a community driven effort and not a single minded effort to try and make a difference.

From: Ty Littlefield <tyler at tysdomain.com<mailto:tyler at tysdomain.com>>
Sent: Wednesday, February 25, 2026 3:43 PM
To: NFB in Computer Science Mailing List <nfbcs at nfbnet.org<mailto:nfbcs at nfbnet.org>>
Cc: Jeff Bishop <jeff at jeffbishop.com<mailto:jeff at jeffbishop.com>>
Subject: Re: [NFBCS] 6 Agents on Friday. 47 by Monday


Sorry for the double email, but on thinking about this a bit more, I want to push back harder against this narrative.



I spend a lot of my time in the accessibility field. I work with people every day to help products become more accessible, and a lot of that work is nuanced discussion about design patterns, UX, and how to make everything functional regardless of ability.



I strongly believe that we should be using AI to make our lives better. It solves a lot of needs, and to outright ignore it is not the way to go.



That said, executives are trying to replace people like me. These are execs in companies who never have and never will use a screen reader. When putting out this type of content, I firmly believe that it does the entire community a disservice to suggest that exponentially increasing the number of agents somehow magically makes content more accessible and usable.



This reality is pretty obvious by going to the linked page, where there are a plethora of WCAG issues including the region label I mentioned in my prior email, regions being created where there should be none, and most notably a grid used for displaying information visually about the stats that is converted into one long line and not provided the proper aria roles to either display it as a table, or otherwise convert the information to a format that it can be more easily read.



If we're going to make claims that x agents solves accessibility concerns, they fall down rather quickly when a vibe coded page demonstrates most of the issues that professionals in this field often warn against and are fighting to solve every day.

Thanks,

Ty Littlefield (he/him/his)

  *   From Bytes to Bites<https://tysdomain.com/>|
  *   Linkedin<https://www.linkedin.com/in/ty-lerlittlefield/>|
  *   Github<https://github.com/tlfdev>
On 2/25/2026 12:50 PM, Jeff Bishop via NFBCS wrote:
Hello NFBCS Members,

Taylor and I are so excited about what this project has turned out to be … Visit the community site on Github, learn about the GIT Going with Github course that is happening on March 7th and 8th and get involved. We would love your input, engagement and most importantly your contributions.

Jeff Bishop

It is early Wednesday morning. February 26th. Something went so right over the past five days that my brain will not stop replaying it.
Let me take you back to Friday night.

How a Frustrated Friday Night Became a Movement

Friday Night on Discord
I was working on a project. I do not even remember what it was. Something with Claude Code, like most of my nights. And I was on a Discord call with some friends, just talking while I worked.
Then something happened in the code that just set me off.
ARIA roles placed wherever the model felt like putting them. No logic. No structure. Just ARIA sprayed across the page like decoration. Inputs without labels. Modals with no focus trapping. Divs pretending to be buttons. The same failures I have been correcting for months. Every single session.
I had enough.
I had enough of fixing ARIA by hand. I had enough of inaccessible code shipping as the default. I had enough of correcting these AIs over and over and getting the same broken output the next time I asked. You know the feeling. It is too much. At some point you stop asking nicely and you start building.
So that is what I did. I decided to build a team of AI agents. Not one model trying to remember everything. A team. Specialists. Each one responsible for one piece of accessibility that it cannot forget, because that is the only thing it knows.
I had no idea what I was getting into.
I was just trying to solve a problem for myself. I wanted Claude to actually write accessible code without me having to babysit every line. That is it. I did not set out to build a forty-seven agent system across three platforms with a GitHub organization and a website and a press release. I was just frustrated on a Friday night.
Of course, I tried other things first. I tried skills in Claude Code. They activate maybe 10 percent of the time without manual intervention. I tried writing detailed instructions in CLAUDE.md files. They work at first, but as the conversation grows, they drift. The model deprioritizes them. It decides other things matter more. Accessibility gets quietly dropped from the plan. Every time.
So, I built agents instead. Six of them. I published a preview post that night, shared the repo, and went to bed.
By Saturday morning, this thing had already outgrown what I imagined. And it did not stop there.

This Is Not Just Me

I need to say this up front because it matters more than anything else in this post.
This is not my project anymore. It never should have been just mine. The moment it stopped being one person yelling into the void and became a team of people building together, everything changed. The scope changed. The quality changed. The ambition changed. The whole thing became something I could not have built alone. And that is the point.
Accessibility has always been a community fight. One person cannot cover every screen reader, every browser, every framework, every assistive technology, every lived experience. That is why the project moved to a GitHub organization called Community Access. That is why it is MIT licensed. That is why it costs nothing. Because the more people who touch this, the better it gets for the people who need it.

Jeff

Jeff Bishop and I were talking on Friday night. That is how this started. I was venting about AI tools forgetting accessibility, and Jeff was right there with me. We were already in the same conversation when I published the preview post and shared the repo.
By Saturday morning, Jeff was not just talking anymore. He was building. I did not expect what happened next.
Jeff did not open an issue or send a message saying nice work. He started pushing code. Within hours he was deep in the codebase, moving faster than I could keep up. By the end of Saturday, he had more commits than I did.
That is not an exaggeration. Look at the git log. Forty-three commits from Jeff in five days. He saw what I was trying to do. He saw where it needed to go. And he went there.
Jeff is blind. Like me, he uses assistive technology every day. He is not reviewing accessibility as an abstract checklist. He is living it. When he builds an agent that enforces focus trapping in modals, it is because he has been trapped in modals. When he writes rules for screen reader announcements, it is because he has sat in silence waiting for an announcement that never came.
That shared experience is what made this work. We did not have to convince each other that accessibility matters. We just had to build.

The Hooks Problem

Now let me explain hooks, because if you read my preview post on Friday, I made hooks sound like the answer to everything. They were not.
A hook in Claude Code is a script that fires every time you send a prompt. Think of it like a checkpoint. Before the AI starts working, the hook looks at what you asked and decides if extra rules should apply. If the task involves UI code, the accessibility agents activate. If it does not, they stay out of the way. That was the idea. And on Friday night, it worked.
The problem arose when we tried to make hooks work for everyone. Not just me on my Mac. Everyone. On every platform and different Claude Code version.
Hooks are fragile. They break across platforms. The JSON schema kept changing. PowerShell on Windows handled them differently than bash on Mac and Linux. Some hooks fired when they should not have. Others did not fire when they should have. We spent hours debugging output formats, timeout issues, and schema mismatches.
Jeff and I merged pull requests fixing hooks. A pull request is how you propose a change to code on GitHub. Someone reviews it, approves it, and it gets merged into the main project. We merged pull requests fixing hooks. Then more pull requests fixing the fixes. Then more fixing those. It was a cycle. Every time we thought we had it, something else broke.
On Tuesday, Jeff made a decision I did not expect. He removed all of them. Every hook. Every hook file. Every hook reference in every documentation file. Gone.
He replaced them with something better. Instead of hooks intercepting prompts, orchestrator agents now coordinate the team through explicit contracts. Each agent returns structured output with confidence levels so the next agent knows exactly what it is getting. Nothing gets lost between steps because the contracts define exactly what goes in and what comes out.
It is cleaner. It is more reliable. And it works on every platform without platform-specific debugging.
That is the kind of decision that only happens when someone is deep enough in the code to see the real problem. Jeff was deep enough by Saturday afternoon.

What It Was

On Friday, Accessibility Agents was six agents in a personal GitHub repo under my name. An accessibility lead, an ARIA specialist, a modal specialist, a contrast master, a keyboard navigator, and a live region controller. It supported Claude Code. That was it.

What It Is Now

Forty-seven agents across four teams. Three platforms. Fourteen shared knowledge modules. Fifty-two pre-built prompts. A GitHub organization. A dedicated website. One command to install.
The web accessibility team alone has sixteen agents. ARIA, modals, contrast, keyboard navigation, live regions, forms, alt text and headings, data tables, link text, cognitive accessibility, mobile accessibility, design systems, guided audits, testing guidance, and WCAG reference.
There is a document scanning team that covers Word, Excel, PowerPoint, PDF, and EPUB files. Forty-six built-in rules for Office documents. Fifty-six for PDFs. It generates VPAT compliance reports. It exports findings to CSV with links to help documentation so people know exactly how to fix what it finds.
There is a markdown documentation team that scans files across nine accessibility domains.
There is a GitHub workflow team with eleven agents for PR review, issue triage, daily briefings, analytics, and repository management.
It runs on Claude Code, GitHub Copilot, and Claude Desktop. It installs with one command on macOS, Linux, and Windows. It is free. It is MIT licensed. It costs nothing.

Before Anyone Asks, No, This Is Not an Overlay

I can already see the comment. Someone is going to read this post, see forty-seven AI agents and the word accessibility in the same sentence, and think: great, another magic fix. Another overlay. Another tool that claims to solve accessibility so developers do not have to think about it.
No. Absolutely not. If you have read my writing before, you know how I feel about overlays. One of them literally broke my rent portal so badly that I could not pay rent until the landlord removed it. I have written an entire post about why overlays are harmful. I am not about to build one.
Let me be crystal clear about what Accessibility Agents is and what it is not.
This is a developer tool. It runs inside your code editor while you are writing code. It helps the AI write more accessible code from the start. That is it. It does not touch your website. It does not add a widget. It does not inject JavaScript into your pages. It does not promise compliance. There is no toolbar. There is no badge. There is no fee.
And here is the part I really need you to hear. This does not replace testing with real assistive technology. It does not replace VoiceOver. It does not replace NVDA. It does not replace JAWS. It does not replace a human being navigating your site with a keyboard and a screen reader and telling you what is broken.
What it does is raise the floor. Code that comes out of an AI tool with these agents active is going to be more accessible than code that comes out without them. Labels will be there. Focus trapping will be there. ARIA roles will make sense instead of being scattered like confetti. Contrast ratios will be checked before you ship, not after someone files a complaint.
That is not a magic fix. That is a better starting point. You still need to test. You still need real users. You still need to care. But at least you are not starting from zero every single time.
If anyone tries to sell you a tool that replaces accessibility testing, run. This is not that tool. This is the tool that makes the code better before testing even begins.

It Moved

The project does not live under my personal GitHub account anymore. It is at the Community Access organization now.
That was deliberate. This is not my project. It is not Jeff’s project. It is a community project. The more perspectives and lived experiences that go into these agents, the better they serve the people who need them.

Thirty Pull Requests in Five Days

I keep coming back to this number because it tells the story better than anything else I can say.
Thirty pull requests merged in five days. That means thirty separate changes were proposed, reviewed, and added to the project. Three hundred and sixty files changed. Seventy-three thousand lines of code added. Thirty-four security vulnerabilities identified and resolved. Path traversal prevention. Injection protection. ZIP bomb limits. Input validation at every call site.
This was not a casual weekend project. This was a sprint. Jeff and I were building in parallel, reviewing each other’s code, catching issues, pushing fixes. The velocity was unlike anything I have experienced on an open source project.
And it happened because people who need accessible software decided to stop waiting for someone else to build it.

Why This Matters

AI coding tools generate code at a speed and scale that humans never could. If that code is inaccessible by default, the problem is not getting smaller. It is getting bigger. Fast.
Ninety-five point nine percent of the top one million websites already have detectable accessibility failures. That number has barely moved in years. AI tools risk making it worse by automating the same mistakes at a scale no human team could match.
I am a screen reader user. When AI generates a modal without focus trapping, I am the person who gets stuck. When it skips live regions on search results, I am the person who hears nothing. When it uses a div with an onClick instead of a button, I am the person who cannot activate it with my keyboard.
But here is what I have learned over the past five days. I am not the only one who feels this way. Jeff feels it. The people who starred the repo and opened issues feel it. This is not one person’s frustration. It is a shared experience across an entire community that has been dealing with inaccessible software for decades.
That is why this is not just me. That is why it cannot be just me. One person’s agents catch one person’s blind spots. A community’s agents catch the patterns that none of us would find alone.

Version 2.0

On Tuesday, Jeff and I got on a call and decided it was time. We were going to release version 2.0.
Five days earlier I had six agents and a personal repo. Now we had forty-seven agents, three platforms, a GitHub organization, a website, and a community. It was not a preview anymore. It was a release.
We published the official announcement yesterday. You can read the full press release on the Community Access website:

https://community-access.github.io/news.html#post/accessibility-agents-v2-launch

I am sharing it here because this community has followed this journey from the beginning. You read the preview post on Friday. You saw the Swift agent team launch. You have been here for the frustration and the building and the breakthroughs. You deserve to see how it landed.
Forty-seven agents. Three platforms. One command to install. Zero cost. That is the headline. But the real story is that a community built this in five days because the tools we depend on every day were not building it for us.

Be Part of This

So now I am promoting it. And I am hoping you will try it out.
I want to make this as easy as possible. You do not need to be a developer to help. You do not need to write code. You do not need to know what ARIA stands for. If you care about accessible software, there is something you can do right now.
Talk about it. Share the project with someone who builds software. Post about it. Mention it in a conversation. The biggest thing holding accessibility back is that not enough people know it is a problem. Every time someone new hears about this project, that changes a little.
Try it. Install it with one command. Use it on your next project. See what it catches. See what it misses.
If you find a bug, file it. Go to the GitHub repo, open an issue, and describe what happened. What you expected. What you got instead. That is it. A good bug report is one of the most valuable contributions anyone can make. It does not take expertise. It takes honesty.
If you want to contribute code, the agents are plain markdown files. You do not need special tooling. You do not need permission. Fork it, make a change, open a pull request. Jeff did exactly that on Saturday morning and look where we are now.

Website: https://community-access.github.io/
GitHub: https://github.com/Community-Access/accessibility-agents

Thank You

To Jeff, for picking this up on Saturday morning and not putting it down. For removing the hooks when I was still trying to fix them. For writing forty-three commits in five days. For caring about this as much as I do.
To every contributor who showed up, opened a PR, filed an issue, or starred the repo. You turned a frustrated Friday night into something real.
And to everyone reading this. If you build software, you have the power to make it accessible. These agents are one way to start. But they are not the finish line. They are the starting block.
This is how it starts. Not with a company. Not with funding. With people who got tired of fighting the same fight every day and decided to build something that fights back.
That is not just me. That is all of us.






_______________________________________________

NFBCS mailing list

NFBCS at nfbnet.org<mailto:NFBCS at nfbnet.org>

http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org

To unsubscribe, change your list options or get your account info for NFBCS:

http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/tyler%40tysdomain.com
_______________________________________________
NFBCS mailing list
NFBCS at nfbnet.org<mailto:NFBCS at nfbnet.org>
http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org
To unsubscribe, change your list options or get your account info for NFBCS:
http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/buddy%40brannan.name

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://nfbnet.org/pipermail/nfbcs_nfbnet.org/attachments/20260225/4bf7ad5b/attachment.htm>

From ring1864 at outlook.com  Thu Feb 26 01:49:26 2026
From: ring1864 at outlook.com (Donna Ring)
Date: Thu, 26 Feb 2026 01:49:26 +0000
Subject: [NFBCS] FW: Erica C. Vaughns NLS Aspiring Leaders Internship
 Program, summer
 2026
In-Reply-To: 
 <SA1PR09MB1122777DCD1F418B72369245BD160A@SA1PR09MB11227.namprd09.prod.outlook.com>
References: 
 <SA1PR09MB1122777DCD1F418B72369245BD160A@SA1PR09MB11227.namprd09.prod.outlook.com>
Message-ID: 
 <DS7PR12MB8321F76AC9FFEA95A3AEBBA2C572A@DS7PR12MB8321.namprd12.prod.outlook.com>

Please share.

Donna Ring


From: NLS Patron Announce <NLS-PATRONANNOUNCE at LISTSERV.LOC.GOV> On Behalf Of Rorie, Tamara
Sent: Thursday, February 12, 2026 11:57 AM
To: NLS-PATRONANNOUNCE at LISTSERV.LOC.GOV
Subject: Erica C. Vaughns NLS Aspiring Leaders Internship Program, summer 2026


All:
This paid internship-established through an endowment and named in memory of Erica Vaughns, a longtime NLS staff member who created the program-offers legally blind individuals the opportunity to work at NLS in areas that support services for the blind, including collections building, program delivery, and business management. Through this program, interns gain valuable experience and explore potential career options while being guided through mentorships and development activities. The next session runs for 10 weeks during the summer of 2026.
Application Process
Currently enrolled undergraduate and graduate students and those who have graduated within the past five years from an accredited two-year or four-year college or university are eligible to apply. In addition, applicants must be a U.S. citizen, legally blind, and able to work remotely.
A complete application package includes a cover letter expressing interest, a resume, a recent official or unofficial transcript, and an application form that is completed online.
Applicants interested in the summer 2026 session must submit completed applications by Sunday, March 1, 2026.
To learn more about the program and the application process, please visit www.loc.gov/nls/about/internship-program<https://www.loc.gov/nls/about/internship-program/>.



________________________________

To unsubscribe from the NLS-PATRONANNOUNCE list, click the following link:
http://listserv.loc.gov/cgi-bin/wa?TICKET=NzM5Njg5IHJpbmcxODY0QE9VVExPT0suQ09NIE5MUy1QQVRST05BTk5PVU5DRbUjQ46xLJIt&c=SIGNOFF
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://nfbnet.org/pipermail/nfbcs_nfbnet.org/attachments/20260226/569ed0df/attachment.htm>

From pdonahue2 at satx.rr.com  Thu Feb 26 02:06:25 2026
From: pdonahue2 at satx.rr.com (Peter)
Date: Wed, 25 Feb 2026 20:06:25 -0600
Subject: [NFBCS] 6 Agents on Friday. 47 by Monday
In-Reply-To: <3916b311-b426-4370-97ce-141f943abc5f@tysdomain.com>
References: <post-189168941@substack.com>
 <20260225183924.3.35f8d6578a430bc7@mg-d1.substack.com>
 <CYYPR02MB9901C9B543A7776D7D8150E5BA75A@CYYPR02MB9901.namprd02.prod.outlook.com>
 <CYYPR02MB9901175A68AA353241D2A90CBA75A@CYYPR02MB9901.namprd02.prod.outlook.com>
 <3916b311-b426-4370-97ce-141f943abc5f@tysdomain.com>
Message-ID: <008b01dca6c4$83496b60$89dc4220$@satx.rr.com>

Good evening everyone,

 

Taylor said that while this large number of AI agents can help mitigate accessibility issues they will never replace testing by real screen reader users. Google calls this approach “A human in the loop.” I’m looking forward to taking this agent army on maneuvers’ myself, but after they engage the enemyI’ll be right behind them to insure they have totally wiped out the enemy of inaccessibility by putting apps and websites through testing with a screen reader myself.

 

Peter Donahue

 

 

 

From: NFBCS <nfbcs-bounces at nfbnet.org> On Behalf Of Ty Littlefield via NFBCS
Sent: Wednesday, February 25, 2026 4:43 PM
To: NFB in Computer Science Mailing List <nfbcs at nfbnet.org>
Cc: Ty Littlefield <tyler at tysdomain.com>
Subject: Re: [NFBCS] 6 Agents on Friday. 47 by Monday

 

Sorry for the double email, but on thinking about this a bit more, I want to push back harder against this narrative.

 

I spend a lot of my time in the accessibility field. I work with people every day to help products become more accessible, and a lot of that work is nuanced discussion about design patterns, UX, and how to make everything functional regardless of ability.

 

I strongly believe that we should be using AI to make our lives better. It solves a lot of needs, and to outright ignore it is not the way to go.

 

That said, executives are trying to replace people like me. These are execs in companies who never have and never will use a screen reader. When putting out this type of content, I firmly believe that it does the entire community a disservice to suggest that exponentially increasing the number of agents somehow magically makes content more accessible and usable.

 

This reality is pretty obvious by going to the linked page, where there are a plethora of WCAG issues including the region label I mentioned in my prior email, regions being created where there should be none, and most notably a grid used for displaying information visually about the stats that is converted into one long line and not provided the proper aria roles to either display it as a table, or otherwise convert the information to a format that it can be more easily read.

 

If we're going to make claims that x agents solves accessibility concerns, they fall down rather quickly when a vibe coded page demonstrates most of the issues that professionals in this field often warn against and are fighting to solve every day.

Thanks,

Ty Littlefield (he/him/his)

*	From Bytes to Bites <https://tysdomain.com> | 
*	Linkedin <https://www.linkedin.com/in/ty-lerlittlefield/> |
*	Github <https://github.com/tlfdev> 

On 2/25/2026 12:50 PM, Jeff Bishop via NFBCS wrote:

Hello NFBCS Members,

 

Taylor and I are so excited about what this project has turned out to be … Visit the community site on Github, learn about the GIT Going with Github course that is happening on March 7th and 8th and get involved. We would love your input, engagement and most importantly your contributions.

 

Jeff Bishop

 

It is early Wednesday morning. February 26th. Something went so right over the past five days that my brain will not stop replaying it.

Let me take you back to Friday night.

 

How a Frustrated Friday Night Became a Movement

 

Friday Night on Discord

I was working on a project. I do not even remember what it was. Something with Claude Code, like most of my nights. And I was on a Discord call with some friends, just talking while I worked.

Then something happened in the code that just set me off.

ARIA roles placed wherever the model felt like putting them. No logic. No structure. Just ARIA sprayed across the page like decoration. Inputs without labels. Modals with no focus trapping. Divs pretending to be buttons. The same failures I have been correcting for months. Every single session.

I had enough.

I had enough of fixing ARIA by hand. I had enough of inaccessible code shipping as the default. I had enough of correcting these AIs over and over and getting the same broken output the next time I asked. You know the feeling. It is too much. At some point you stop asking nicely and you start building.

So that is what I did. I decided to build a team of AI agents. Not one model trying to remember everything. A team. Specialists. Each one responsible for one piece of accessibility that it cannot forget, because that is the only thing it knows.

I had no idea what I was getting into.

I was just trying to solve a problem for myself. I wanted Claude to actually write accessible code without me having to babysit every line. That is it. I did not set out to build a forty-seven agent system across three platforms with a GitHub organization and a website and a press release. I was just frustrated on a Friday night.

Of course, I tried other things first. I tried skills in Claude Code. They activate maybe 10 percent of the time without manual intervention. I tried writing detailed instructions in CLAUDE.md files. They work at first, but as the conversation grows, they drift. The model deprioritizes them. It decides other things matter more. Accessibility gets quietly dropped from the plan. Every time.

So, I built agents instead. Six of them. I published a preview post that night, shared the repo, and went to bed.

By Saturday morning, this thing had already outgrown what I imagined. And it did not stop there.

 

This Is Not Just Me

 

I need to say this up front because it matters more than anything else in this post.

This is not my project anymore. It never should have been just mine. The moment it stopped being one person yelling into the void and became a team of people building together, everything changed. The scope changed. The quality changed. The ambition changed. The whole thing became something I could not have built alone. And that is the point.

Accessibility has always been a community fight. One person cannot cover every screen reader, every browser, every framework, every assistive technology, every lived experience. That is why the project moved to a GitHub organization called Community Access. That is why it is MIT licensed. That is why it costs nothing. Because the more people who touch this, the better it gets for the people who need it.

 

Jeff

 

Jeff Bishop and I were talking on Friday night. That is how this started. I was venting about AI tools forgetting accessibility, and Jeff was right there with me. We were already in the same conversation when I published the preview post and shared the repo.

By Saturday morning, Jeff was not just talking anymore. He was building. I did not expect what happened next.

Jeff did not open an issue or send a message saying nice work. He started pushing code. Within hours he was deep in the codebase, moving faster than I could keep up. By the end of Saturday, he had more commits than I did.

That is not an exaggeration. Look at the git log. Forty-three commits from Jeff in five days. He saw what I was trying to do. He saw where it needed to go. And he went there.

Jeff is blind. Like me, he uses assistive technology every day. He is not reviewing accessibility as an abstract checklist. He is living it. When he builds an agent that enforces focus trapping in modals, it is because he has been trapped in modals. When he writes rules for screen reader announcements, it is because he has sat in silence waiting for an announcement that never came.

That shared experience is what made this work. We did not have to convince each other that accessibility matters. We just had to build.

 

The Hooks Problem

 

Now let me explain hooks, because if you read my preview post on Friday, I made hooks sound like the answer to everything. They were not.

A hook in Claude Code is a script that fires every time you send a prompt. Think of it like a checkpoint. Before the AI starts working, the hook looks at what you asked and decides if extra rules should apply. If the task involves UI code, the accessibility agents activate. If it does not, they stay out of the way. That was the idea. And on Friday night, it worked.

The problem arose when we tried to make hooks work for everyone. Not just me on my Mac. Everyone. On every platform and different Claude Code version.

Hooks are fragile. They break across platforms. The JSON schema kept changing. PowerShell on Windows handled them differently than bash on Mac and Linux. Some hooks fired when they should not have. Others did not fire when they should have. We spent hours debugging output formats, timeout issues, and schema mismatches.

Jeff and I merged pull requests fixing hooks. A pull request is how you propose a change to code on GitHub. Someone reviews it, approves it, and it gets merged into the main project. We merged pull requests fixing hooks. Then more pull requests fixing the fixes. Then more fixing those. It was a cycle. Every time we thought we had it, something else broke.

On Tuesday, Jeff made a decision I did not expect. He removed all of them. Every hook. Every hook file. Every hook reference in every documentation file. Gone.

He replaced them with something better. Instead of hooks intercepting prompts, orchestrator agents now coordinate the team through explicit contracts. Each agent returns structured output with confidence levels so the next agent knows exactly what it is getting. Nothing gets lost between steps because the contracts define exactly what goes in and what comes out.

It is cleaner. It is more reliable. And it works on every platform without platform-specific debugging.

That is the kind of decision that only happens when someone is deep enough in the code to see the real problem. Jeff was deep enough by Saturday afternoon.

 

What It Was

 

On Friday, Accessibility Agents was six agents in a personal GitHub repo under my name. An accessibility lead, an ARIA specialist, a modal specialist, a contrast master, a keyboard navigator, and a live region controller. It supported Claude Code. That was it.

 

What It Is Now

 

Forty-seven agents across four teams. Three platforms. Fourteen shared knowledge modules. Fifty-two pre-built prompts. A GitHub organization. A dedicated website. One command to install.

The web accessibility team alone has sixteen agents. ARIA, modals, contrast, keyboard navigation, live regions, forms, alt text and headings, data tables, link text, cognitive accessibility, mobile accessibility, design systems, guided audits, testing guidance, and WCAG reference.

There is a document scanning team that covers Word, Excel, PowerPoint, PDF, and EPUB files. Forty-six built-in rules for Office documents. Fifty-six for PDFs. It generates VPAT compliance reports. It exports findings to CSV with links to help documentation so people know exactly how to fix what it finds.

There is a markdown documentation team that scans files across nine accessibility domains.

There is a GitHub workflow team with eleven agents for PR review, issue triage, daily briefings, analytics, and repository management.

It runs on Claude Code, GitHub Copilot, and Claude Desktop. It installs with one command on macOS, Linux, and Windows. It is free. It is MIT licensed. It costs nothing.

 

Before Anyone Asks, No, This Is Not an Overlay

 

I can already see the comment. Someone is going to read this post, see forty-seven AI agents and the word accessibility in the same sentence, and think: great, another magic fix. Another overlay. Another tool that claims to solve accessibility so developers do not have to think about it.

No. Absolutely not. If you have read my writing before, you know how I feel about overlays. One of them literally broke my rent portal so badly that I could not pay rent until the landlord removed it. I have written an entire post about why overlays are harmful. I am not about to build one.

Let me be crystal clear about what Accessibility Agents is and what it is not.

This is a developer tool. It runs inside your code editor while you are writing code. It helps the AI write more accessible code from the start. That is it. It does not touch your website. It does not add a widget. It does not inject JavaScript into your pages. It does not promise compliance. There is no toolbar. There is no badge. There is no fee.

And here is the part I really need you to hear. This does not replace testing with real assistive technology. It does not replace VoiceOver. It does not replace NVDA. It does not replace JAWS. It does not replace a human being navigating your site with a keyboard and a screen reader and telling you what is broken.

What it does is raise the floor. Code that comes out of an AI tool with these agents active is going to be more accessible than code that comes out without them. Labels will be there. Focus trapping will be there. ARIA roles will make sense instead of being scattered like confetti. Contrast ratios will be checked before you ship, not after someone files a complaint.

That is not a magic fix. That is a better starting point. You still need to test. You still need real users. You still need to care. But at least you are not starting from zero every single time.

If anyone tries to sell you a tool that replaces accessibility testing, run. This is not that tool. This is the tool that makes the code better before testing even begins.

 

It Moved

 

The project does not live under my personal GitHub account anymore. It is at the Community Access organization now.

That was deliberate. This is not my project. It is not Jeff’s project. It is a community project. The more perspectives and lived experiences that go into these agents, the better they serve the people who need them.

 

Thirty Pull Requests in Five Days

 

I keep coming back to this number because it tells the story better than anything else I can say.

Thirty pull requests merged in five days. That means thirty separate changes were proposed, reviewed, and added to the project. Three hundred and sixty files changed. Seventy-three thousand lines of code added. Thirty-four security vulnerabilities identified and resolved. Path traversal prevention. Injection protection. ZIP bomb limits. Input validation at every call site.

This was not a casual weekend project. This was a sprint. Jeff and I were building in parallel, reviewing each other’s code, catching issues, pushing fixes. The velocity was unlike anything I have experienced on an open source project.

And it happened because people who need accessible software decided to stop waiting for someone else to build it.

 

Why This Matters

 

AI coding tools generate code at a speed and scale that humans never could. If that code is inaccessible by default, the problem is not getting smaller. It is getting bigger. Fast.

Ninety-five point nine percent of the top one million websites already have detectable accessibility failures. That number has barely moved in years. AI tools risk making it worse by automating the same mistakes at a scale no human team could match.

I am a screen reader user. When AI generates a modal without focus trapping, I am the person who gets stuck. When it skips live regions on search results, I am the person who hears nothing. When it uses a div with an onClick instead of a button, I am the person who cannot activate it with my keyboard.

But here is what I have learned over the past five days. I am not the only one who feels this way. Jeff feels it. The people who starred the repo and opened issues feel it. This is not one person’s frustration. It is a shared experience across an entire community that has been dealing with inaccessible software for decades.

That is why this is not just me. That is why it cannot be just me. One person’s agents catch one person’s blind spots. A community’s agents catch the patterns that none of us would find alone.

 

Version 2.0

 

On Tuesday, Jeff and I got on a call and decided it was time. We were going to release version 2.0.

Five days earlier I had six agents and a personal repo. Now we had forty-seven agents, three platforms, a GitHub organization, a website, and a community. It was not a preview anymore. It was a release.

We published the official announcement yesterday. You can read the full press release on the Community Access website:

 

https://community-access.github.io/news.html#post/accessibility-agents-v2-launch

 

I am sharing it here because this community has followed this journey from the beginning. You read the preview post on Friday. You saw the Swift agent team launch. You have been here for the frustration and the building and the breakthroughs. You deserve to see how it landed.

Forty-seven agents. Three platforms. One command to install. Zero cost. That is the headline. But the real story is that a community built this in five days because the tools we depend on every day were not building it for us.

 

Be Part of This

 

So now I am promoting it. And I am hoping you will try it out.

I want to make this as easy as possible. You do not need to be a developer to help. You do not need to write code. You do not need to know what ARIA stands for. If you care about accessible software, there is something you can do right now.

Talk about it. Share the project with someone who builds software. Post about it. Mention it in a conversation. The biggest thing holding accessibility back is that not enough people know it is a problem. Every time someone new hears about this project, that changes a little.

Try it. Install it with one command. Use it on your next project. See what it catches. See what it misses.

If you find a bug, file it. Go to the GitHub repo, open an issue, and describe what happened. What you expected. What you got instead. That is it. A good bug report is one of the most valuable contributions anyone can make. It does not take expertise. It takes honesty.

If you want to contribute code, the agents are plain markdown files. You do not need special tooling. You do not need permission. Fork it, make a change, open a pull request. Jeff did exactly that on Saturday morning and look where we are now.

 

Website: https://community-access.github.io/

GitHub: https://github.com/Community-Access/accessibility-agents

 

Thank You

 

To Jeff, for picking this up on Saturday morning and not putting it down. For removing the hooks when I was still trying to fix them. For writing forty-three commits in five days. For caring about this as much as I do.

To every contributor who showed up, opened a PR, filed an issue, or starred the repo. You turned a frustrated Friday night into something real.

And to everyone reading this. If you build software, you have the power to make it accessible. These agents are one way to start. But they are not the finish line. They are the starting block.

This is how it starts. Not with a company. Not with funding. With people who got tired of fighting the same fight every day and decided to build something that fights back.

That is not just me. That is all of us.

 

 





_______________________________________________
NFBCS mailing list
NFBCS at nfbnet.org <mailto:NFBCS at nfbnet.org> 
http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org
To unsubscribe, change your list options or get your account info for NFBCS:
http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/tyler%40tysdomain.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://nfbnet.org/pipermail/nfbcs_nfbnet.org/attachments/20260225/e7286dc9/attachment.htm>

From sean.mcmahon.dc at gmail.com  Thu Feb 26 02:25:52 2026
From: sean.mcmahon.dc at gmail.com (sean.mcmahon.dc at gmail.com)
Date: Wed, 25 Feb 2026 21:25:52 -0500
Subject: [NFBCS] Lately Zoom with JAWS 2026 are to verbose when announcing
 buttons and controls
Message-ID: <000001dca6c7$3b2363b0$b16a2b10$@gmail.com>

I updated to the latest version of Azoom and have the latest JAWS 2026.  Now
when announcing a button JAWS says something like "share button quote
control id = true quote."  I didn't change any verbosity settings, I can't
find a specific setting for controlID announcement and this is annoying
because it takes a really long time to just hear the simple status of what
tab I am on or is the chat pannell open.  I'm in a class on Zoom every day
for the next few weeks, so this has become a problem for me.  Thanks for any
suggestions you may have.

Sean

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://nfbnet.org/pipermail/nfbcs_nfbnet.org/attachments/20260225/0d8b9ac3/attachment.htm>

From bhavya.shah125 at gmail.com  Thu Feb 26 07:53:39 2026
From: bhavya.shah125 at gmail.com (Bhavya shah)
Date: Wed, 25 Feb 2026 23:53:39 -0800
Subject: [NFBCS] Accessible AI agents
Message-ID: 
 <CACHadJ3CqfvXgdt43SJVcHHFsh-0wiBdomyvrTTNpSMV6aE5tw@mail.gmail.com>

Have you tried agentic AI tools like MultiOn, Claude Cowork, OpenClaw,
Microsoft Copilot, etc? How has your experience been as a screen reader
user? I am interested in in getting started with one of these and would
prefer one that is both capable and accessible.



Warmly,

Bhavya Shah | M.S. AI & B.S. Math/CS, Stanford University

LinkedIn <https://www.linkedin.com/in/bhavyashah125/> | Instagram
<https://www.instagram.com/mynameisnotjavier> | Website
<https://bhavyashahcomedy.com/>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://nfbnet.org/pipermail/nfbcs_nfbnet.org/attachments/20260225/b4ffa3da/attachment.htm>

From chong.curtis at gmail.com  Thu Feb 26 16:24:30 2026
From: chong.curtis at gmail.com (Curtis Chong)
Date: Thu, 26 Feb 2026 09:24:30 -0700
Subject: [NFBCS] Lately Zoom with JAWS 2026 are to verbose when announcing
 buttons and controls
In-Reply-To: <000001dca6c7$3b2363b0$b16a2b10$@gmail.com>
References: <000001dca6c7$3b2363b0$b16a2b10$@gmail.com>
Message-ID: <00ae01dca73c$62e9fb50$28bdf1f0$@gmail.com>

Hello:

 

This problem has been reported to Zoom. If you buy the scripts from Brian
Hartgen, the problem goes away.

 

I am hoping the next Zoom update gets rid of the issue for everyone.

 

Cordially,

 

Curtis Chong

 

From: NFBCS <nfbcs-bounces at nfbnet.org> On Behalf Of Sean McMahon via NFBCS
Sent: Wednesday, February 25, 2026 7:26 PM
To: nfbcs at nfbnet.org
Cc: sean.mcmahon.dc at gmail.com
Subject: [NFBCS] Lately Zoom with JAWS 2026 are to verbose when announcing
buttons and controls

 

I updated to the latest version of Azoom and have the latest JAWS 2026.  Now
when announcing a button JAWS says something like "share button quote
control id = true quote."  I didn't change any verbosity settings, I can't
find a specific setting for controlID announcement and this is annoying
because it takes a really long time to just hear the simple status of what
tab I am on or is the chat pannell open.  I'm in a class on Zoom every day
for the next few weeks, so this has become a problem for me.  Thanks for any
suggestions you may have.

Sean

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://nfbnet.org/pipermail/nfbcs_nfbnet.org/attachments/20260226/c2aea64b/attachment.htm>

From chong.curtis at gmail.com  Thu Feb 26 16:25:32 2026
From: chong.curtis at gmail.com (Curtis Chong)
Date: Thu, 26 Feb 2026 09:25:32 -0700
Subject: [NFBCS] Lately Zoom with JAWS 2026 are to verbose when announcing
 buttons and controls
In-Reply-To: <000001dca6c7$3b2363b0$b16a2b10$@gmail.com>
References: <000001dca6c7$3b2363b0$b16a2b10$@gmail.com>
Message-ID: <00b301dca73c$888bec60$99a3c520$@gmail.com>

The fine folks at Zoom tell me that, "This has been reported to our engineer
and is being worked on for the March release."

 

Cordially,

 

Curtis Chong

 

From: NFBCS <nfbcs-bounces at nfbnet.org> On Behalf Of Sean McMahon via NFBCS
Sent: Wednesday, February 25, 2026 7:26 PM
To: nfbcs at nfbnet.org
Cc: sean.mcmahon.dc at gmail.com
Subject: [NFBCS] Lately Zoom with JAWS 2026 are to verbose when announcing
buttons and controls

 

I updated to the latest version of Azoom and have the latest JAWS 2026.  Now
when announcing a button JAWS says something like "share button quote
control id = true quote."  I didn't change any verbosity settings, I can't
find a specific setting for controlID announcement and this is annoying
because it takes a really long time to just hear the simple status of what
tab I am on or is the chat pannell open.  I'm in a class on Zoom every day
for the next few weeks, so this has become a problem for me.  Thanks for any
suggestions you may have.

Sean

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://nfbnet.org/pipermail/nfbcs_nfbnet.org/attachments/20260226/10cfc035/attachment.htm>

From chong.curtis at gmail.com  Thu Feb 26 16:47:22 2026
From: chong.curtis at gmail.com (Curtis Chong)
Date: Thu, 26 Feb 2026 09:47:22 -0700
Subject: [NFBCS] Lately Zoom with JAWS 2026 are to verbose when announcing
 buttons and controls
In-Reply-To: <00b301dca73c$888bec60$99a3c520$@gmail.com>
References: <000001dca6c7$3b2363b0$b16a2b10$@gmail.com>
 <00b301dca73c$888bec60$99a3c520$@gmail.com>
Message-ID: <010901dca73f$94b37780$be1a6680$@gmail.com>

Greetings:

 

I believe I have a temporary fix for your problem short of having to
purchase scripts from Hartgen Consultancy.

 

Here is a procedure which assumes you are using JAWS without the Zoom Pro
scripts from Hartgen Consultancy.

 

1.	Get into the Zoom Workspace program, but do not start a meeting or
anything like that.
2.	Press the JAWSKEY along with the number 6 to bring up the JAWS
Settings Center. Tab once to focus on the Tree view.
3.	Arrow down in the Tree View until you reach JAWS Verbosity, which
should be reported by JAWS as being "closed."
4.	Press Right Arrow to open this.
5.	Arrow down once to hear what level is set for Speech Verbosity. For
most folks, this is stated as Beginner. Mine is set to Intermediate, but
that doesn't really matter.
6.	Arrow down once to Configure Verbosity Levels, which JAWS will
report as being "closed." Press Right Arrow to open this branch of the tree.
7.	Assuming you are at the Beginner verbosity level, Arrow down once to
hear "Beginner...".
8.	Do not press Enter on this. Press the Spacebar instead. You should
now be in a list of 24 items.
9.	Press the letter h to focus on Help Balloon, which JAWS will report
as being checked. Press Space to uncheck this.
10.	Tab to and activate OK for as many times as you need to in order to
exit JAWS Settings.

 

This should do the trick and save you lots of aggravation during your Zoom
meetings.

 

Cordially,

 

Curtis Chong

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://nfbnet.org/pipermail/nfbcs_nfbnet.org/attachments/20260226/ba1c131f/attachment.htm>

From dgl at dlee.org  Thu Feb 26 17:13:52 2026
From: dgl at dlee.org (Doug Lee)
Date: Thu, 26 Feb 2026 12:13:52 -0500
Subject: [NFBCS] Lately Zoom with JAWS 2026 are to verbose when
 announcing buttons and controls
In-Reply-To: <010901dca73f$94b37780$be1a6680$@gmail.com>
References: <000001dca6c7$3b2363b0$b16a2b10$@gmail.com>
 <00b301dca73c$888bec60$99a3c520$@gmail.com>
 <010901dca73f$94b37780$be1a6680$@gmail.com>
Message-ID: <diy6rgqvosc7wfxnlj4ue7b42zxrt6t6zqst73vck2ogju62v4@37loruvmm7nt>

This approach makes sense. I rarely use Zoom, but I saw this issue last
week and realized that the unwanted text is assigned to the UIA Help and
MSAA AccHelp properties of accessibility elements in the Zoom
accessibility trees. Glad to hear this should be fixed internally at
some point.

On Thu, Feb 26, 2026 at 09:47:22AM -0700, Curtis Chong via NFBCS wrote:
   Greetings:


   I believe I have a temporary fix for your problem short of having to
   purchase scripts from Hartgen Consultancy.


   Here is a procedure which assumes you are using JAWS without the Zoom
   Pro scripts from Hartgen Consultancy.


    1. Get into the Zoom Workspace program, but do not start a meeting or
       anything like that.
    2. Press the JAWSKEY along with the number 6 to bring up the JAWS
       Settings Center. Tab once to focus on the Tree view.
    3. Arrow down in the Tree View until you reach JAWS Verbosity, which
       should be reported by JAWS as being “closed.”
    4. Press Right Arrow to open this.
    5. Arrow down once to hear what level is set for Speech Verbosity. For
       most folks, this is stated as Beginner. Mine is set to
       Intermediate, but that doesn’t really matter.
    6. Arrow down once to Configure Verbosity Levels, which JAWS will
       report as being “closed.” Press Right Arrow to open this branch of
       the tree.
    7. Assuming you are at the Beginner verbosity level, Arrow down once
       to hear “Beginner...”.
    8. Do not press Enter on this. Press the Spacebar instead. You should
       now be in a list of 24 items.
    9. Press the letter h to focus on Help Balloon, which JAWS will report
       as being checked. Press Space to uncheck this.
   10. Tab to and activate OK for as many times as you need to in order to
       exit JAWS Settings.


   This should do the trick and save you lots of aggravation during your
   Zoom meetings.


   Cordially,


   Curtis Chong



-- 
Doug Lee                 dgl at dlee.org                http://www.dlee.org
"When your best-laid plans have turned to dust, vacuum!"
- Whoopi Goldberg 

From sean.mcmahon.dc at gmail.com  Thu Feb 26 18:37:16 2026
From: sean.mcmahon.dc at gmail.com (Sean McMahon)
Date: Thu, 26 Feb 2026 18:37:16 +0000
Subject: [NFBCS] Lately Zoom with JAWS 2026 are to verbose when announcing
 buttons and controls
In-Reply-To: <diy6rgqvosc7wfxnlj4ue7b42zxrt6t6zqst73vck2ogju62v4@37loruvmm7nt>
References: <000001dca6c7$3b2363b0$b16a2b10$@gmail.com>
 <00b301dca73c$888bec60$99a3c520$@gmail.com>
 <010901dca73f$94b37780$be1a6680$@gmail.com>
 <diy6rgqvosc7wfxnlj4ue7b42zxrt6t6zqst73vck2ogju62v4@37loruvmm7nt>
Message-ID: 
	<BY1P221MB1412AD8E32EA125B97C103A1A772A@BY1P221MB1412.NAMP221.PROD.OUTLOOK.COM>

Thanks, Doug and Curtis for your suggestions for your information. I am currently using the jaws pro scripts. I got these at some point back when I wanted to have the ability to toggle alerts off I think they might have finally migrated that to main jaws functionality either way, there is a configuration line of for help balloon and I didn’t know that  affected this I was looking for control ID because that was the text I was hearing thank you so much and I’ll try this suggestion.

Get Outlook for iOS<https://aka.ms/o0ukef>
________________________________
From: NFBCS <nfbcs-bounces at nfbnet.org> on behalf of Doug Lee via NFBCS <nfbcs at nfbnet.org>
Sent: Thursday, February 26, 2026 12:13:52 PM
To: NFB in Computer Science Mailing List <nfbcs at nfbnet.org>
Cc: Doug Lee <dgl at dlee.org>
Subject: Re: [NFBCS] Lately Zoom with JAWS 2026 are to verbose when announcing buttons and controls

This approach makes sense. I rarely use Zoom, but I saw this issue last
week and realized that the unwanted text is assigned to the UIA Help and
MSAA AccHelp properties of accessibility elements in the Zoom
accessibility trees. Glad to hear this should be fixed internally at
some point.

On Thu, Feb 26, 2026 at 09:47:22AM -0700, Curtis Chong via NFBCS wrote:
   Greetings:


   I believe I have a temporary fix for your problem short of having to
   purchase scripts from Hartgen Consultancy.


   Here is a procedure which assumes you are using JAWS without the Zoom
   Pro scripts from Hartgen Consultancy.


    1. Get into the Zoom Workspace program, but do not start a meeting or
       anything like that.
    2. Press the JAWSKEY along with the number 6 to bring up the JAWS
       Settings Center. Tab once to focus on the Tree view.
    3. Arrow down in the Tree View until you reach JAWS Verbosity, which
       should be reported by JAWS as being “closed.”
    4. Press Right Arrow to open this.
    5. Arrow down once to hear what level is set for Speech Verbosity. For
       most folks, this is stated as Beginner. Mine is set to
       Intermediate, but that doesn’t really matter.
    6. Arrow down once to Configure Verbosity Levels, which JAWS will
       report as being “closed.” Press Right Arrow to open this branch of
       the tree.
    7. Assuming you are at the Beginner verbosity level, Arrow down once
       to hear “Beginner...”.
    8. Do not press Enter on this. Press the Spacebar instead. You should
       now be in a list of 24 items.
    9. Press the letter h to focus on Help Balloon, which JAWS will report
       as being checked. Press Space to uncheck this.
   10. Tab to and activate OK for as many times as you need to in order to
       exit JAWS Settings.


   This should do the trick and save you lots of aggravation during your
   Zoom meetings.


   Cordially,


   Curtis Chong



--
Doug Lee                 dgl at dlee.org                http://www.dlee.org
"When your best-laid plans have turned to dust, vacuum!"
- Whoopi Goldberg

_______________________________________________
NFBCS mailing list
NFBCS at nfbnet.org
http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org
To unsubscribe, change your list options or get your account info for NFBCS:
http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/sean.mcmahon.dc%40gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://nfbnet.org/pipermail/nfbcs_nfbnet.org/attachments/20260226/a84f607c/attachment.htm>

From chong.curtis at gmail.com  Thu Feb 26 18:52:51 2026
From: chong.curtis at gmail.com (Curtis Chong)
Date: Thu, 26 Feb 2026 11:52:51 -0700
Subject: [NFBCS] Lately Zoom with JAWS 2026 are to verbose when announcing
 buttons and controls
In-Reply-To: 
 <BY1P221MB1412AD8E32EA125B97C103A1A772A@BY1P221MB1412.NAMP221.PROD.OUTLOOK.COM>
References: <000001dca6c7$3b2363b0$b16a2b10$@gmail.com>
 <00b301dca73c$888bec60$99a3c520$@gmail.com>
 <010901dca73f$94b37780$be1a6680$@gmail.com>
 <diy6rgqvosc7wfxnlj4ue7b42zxrt6t6zqst73vck2ogju62v4@37loruvmm7nt>
 	<BY1P221MB1412AD8E32EA125B97C103A1A772A@BY1P221MB1412.NAMP221.PROD.OUTLOOK.COM>
Message-ID: <001001dca751$1c865ef0$55931cd0$@gmail.com>

Hi Sean:

 

If you update the Pro Scripts from Hartgen Consultancy, the excessive and
unwanted verbiage goes away Press JAWSKEY h and Enter on the Check for
Updates link.

 

Cordially,

 

Curtis Chong

 

 

From: NFBCS <nfbcs-bounces at nfbnet.org> On Behalf Of Sean McMahon via NFBCS
Sent: Thursday, February 26, 2026 11:37 AM
To: NFB in Computer Science Mailing List <nfbcs at nfbnet.org>
Cc: Sean McMahon <sean.mcmahon.dc at gmail.com>
Subject: Re: [NFBCS] Lately Zoom with JAWS 2026 are to verbose when
announcing buttons and controls

 

Thanks, Doug and Curtis for your suggestions for your information. I am
currently using the jaws pro scripts. I got these at some point back when I
wanted to have the ability to toggle alerts off I think they might have
finally migrated that to main jaws functionality either way, there is a
configuration line of for help balloon and I didn't know that  affected this
I was looking for control ID because that was the text I was hearing thank
you so much and I'll try this suggestion.

 

Get Outlook for iOS <https://aka.ms/o0ukef> 

  _____  

From: NFBCS <nfbcs-bounces at nfbnet.org> on behalf of Doug Lee via NFBCS
<nfbcs at nfbnet.org>
Sent: Thursday, February 26, 2026 12:13:52 PM
To: NFB in Computer Science Mailing List <nfbcs at nfbnet.org>
Cc: Doug Lee <dgl at dlee.org>
Subject: Re: [NFBCS] Lately Zoom with JAWS 2026 are to verbose when
announcing buttons and controls 

 

This approach makes sense. I rarely use Zoom, but I saw this issue last
week and realized that the unwanted text is assigned to the UIA Help and
MSAA AccHelp properties of accessibility elements in the Zoom
accessibility trees. Glad to hear this should be fixed internally at
some point.

On Thu, Feb 26, 2026 at 09:47:22AM -0700, Curtis Chong via NFBCS wrote:
   Greetings:


   I believe I have a temporary fix for your problem short of having to
   purchase scripts from Hartgen Consultancy.


   Here is a procedure which assumes you are using JAWS without the Zoom
   Pro scripts from Hartgen Consultancy.


    1. Get into the Zoom Workspace program, but do not start a meeting or
       anything like that.
    2. Press the JAWSKEY along with the number 6 to bring up the JAWS
       Settings Center. Tab once to focus on the Tree view.
    3. Arrow down in the Tree View until you reach JAWS Verbosity, which
       should be reported by JAWS as being "closed."
    4. Press Right Arrow to open this.
    5. Arrow down once to hear what level is set for Speech Verbosity. For
       most folks, this is stated as Beginner. Mine is set to
       Intermediate, but that doesn't really matter.
    6. Arrow down once to Configure Verbosity Levels, which JAWS will
       report as being "closed." Press Right Arrow to open this branch of
       the tree.
    7. Assuming you are at the Beginner verbosity level, Arrow down once
       to hear "Beginner...".
    8. Do not press Enter on this. Press the Spacebar instead. You should
       now be in a list of 24 items.
    9. Press the letter h to focus on Help Balloon, which JAWS will report
       as being checked. Press Space to uncheck this.
   10. Tab to and activate OK for as many times as you need to in order to
       exit JAWS Settings.


   This should do the trick and save you lots of aggravation during your
   Zoom meetings.


   Cordially,


   Curtis Chong



-- 
Doug Lee                 dgl at dlee.org                http://www.dlee.org
"When your best-laid plans have turned to dust, vacuum!"
- Whoopi Goldberg 

_______________________________________________
NFBCS mailing list
NFBCS at nfbnet.org
http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org
To unsubscribe, change your list options or get your account info for NFBCS:
http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/sean.mcmahon.dc%40gmail.c
om

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://nfbnet.org/pipermail/nfbcs_nfbnet.org/attachments/20260226/ea429a10/attachment.htm>

From dandrews920 at comcast.net  Thu Feb 26 23:55:01 2026
From: dandrews920 at comcast.net (dandrews920 at comcast.net)
Date: Thu, 26 Feb 2026 17:55:01 -0600
Subject: [NFBCS] Lately Zoom with JAWS 2026 are to verbose when announcing
 buttons and controls
In-Reply-To: <010901dca73f$94b37780$be1a6680$@gmail.com>
References: <000001dca6c7$3b2363b0$b16a2b10$@gmail.com>
 <00b301dca73c$888bec60$99a3c520$@gmail.com>
 <010901dca73f$94b37780$be1a6680$@gmail.com>
Message-ID: <4c5001dca77b$537ae050$fa70a0f0$@comcast.net>

I am getting all kinds of extraneous codes in Zoom Workplace for Government!

 

Dave

 

 

 

From: NFBCS <nfbcs-bounces at nfbnet.org> On Behalf Of Curtis Chong via NFBCS
Sent: Thursday, February 26, 2026 10:47 AM
To: 'NFB in Computer Science Mailing List' <nfbcs at nfbnet.org>
Cc: Curtis Chong <chong.curtis at gmail.com>
Subject: [NFBCS] Lately Zoom with JAWS 2026 are to verbose when announcing
buttons and controls

 

Greetings:

 

I believe I have a temporary fix for your problem short of having to
purchase scripts from Hartgen Consultancy.

 

Here is a procedure which assumes you are using JAWS without the Zoom Pro
scripts from Hartgen Consultancy.

 

1.	Get into the Zoom Workspace program, but do not start a meeting or
anything like that.
2.	Press the JAWSKEY along with the number 6 to bring up the JAWS
Settings Center. Tab once to focus on the Tree view.
3.	Arrow down in the Tree View until you reach JAWS Verbosity, which
should be reported by JAWS as being "closed."
4.	Press Right Arrow to open this.
5.	Arrow down once to hear what level is set for Speech Verbosity. For
most folks, this is stated as Beginner. Mine is set to Intermediate, but
that doesn't really matter.
6.	Arrow down once to Configure Verbosity Levels, which JAWS will
report as being "closed." Press Right Arrow to open this branch of the tree.
7.	Assuming you are at the Beginner verbosity level, Arrow down once to
hear "Beginner...".
8.	Do not press Enter on this. Press the Spacebar instead. You should
now be in a list of 24 items.
9.	Press the letter h to focus on Help Balloon, which JAWS will report
as being checked. Press Space to uncheck this.
10.	Tab to and activate OK for as many times as you need to in order to
exit JAWS Settings.

 

This should do the trick and save you lots of aggravation during your Zoom
meetings.

 

Cordially,

 

Curtis Chong

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://nfbnet.org/pipermail/nfbcs_nfbnet.org/attachments/20260226/c0d06338/attachment.htm>

From sean.mcmahon.dc at gmail.com  Fri Feb 27 02:13:08 2026
From: sean.mcmahon.dc at gmail.com (sean.mcmahon.dc at gmail.com)
Date: Thu, 26 Feb 2026 21:13:08 -0500
Subject: [NFBCS] Lately Zoom with JAWS 2026 are to verbose when announcing
 buttons and controls
In-Reply-To: <4c5001dca77b$537ae050$fa70a0f0$@comcast.net>
References: <000001dca6c7$3b2363b0$b16a2b10$@gmail.com>
 <00b301dca73c$888bec60$99a3c520$@gmail.com>
 <010901dca73f$94b37780$be1a6680$@gmail.com>
 <4c5001dca77b$537ae050$fa70a0f0$@comcast.net>
Message-ID: <007001dca78e$9e2b1350$da8139f0$@gmail.com>

Ok, I have the pro scripts, but there wasn't an update available, so I am on
the latest version.  I finally got the noise to stop after I unchecked the
box for help text and help balloons under Zoom's user verbosity settings in
the JAWS configuration file for Zoom. 

Sean

 

 

From: NFBCS <nfbcs-bounces at nfbnet.org> On Behalf Of dandrews920--- via NFBCS
Sent: Thursday, February 26, 2026 6:55 PM
To: 'NFB in Computer Science Mailing List' <nfbcs at nfbnet.org>
Cc: dandrews920 at comcast.net
Subject: Re: [NFBCS] Lately Zoom with JAWS 2026 are to verbose when
announcing buttons and controls

 

I am getting all kinds of extraneous codes in Zoom Workplace for Government!

 

Dave

 

 

 

From: NFBCS <nfbcs-bounces at nfbnet.org <mailto:nfbcs-bounces at nfbnet.org> > On
Behalf Of Curtis Chong via NFBCS
Sent: Thursday, February 26, 2026 10:47 AM
To: 'NFB in Computer Science Mailing List' <nfbcs at nfbnet.org
<mailto:nfbcs at nfbnet.org> >
Cc: Curtis Chong <chong.curtis at gmail.com <mailto:chong.curtis at gmail.com> >
Subject: [NFBCS] Lately Zoom with JAWS 2026 are to verbose when announcing
buttons and controls

 

Greetings:

 

I believe I have a temporary fix for your problem short of having to
purchase scripts from Hartgen Consultancy.

 

Here is a procedure which assumes you are using JAWS without the Zoom Pro
scripts from Hartgen Consultancy.

 

1.	Get into the Zoom Workspace program, but do not start a meeting or
anything like that.
2.	Press the JAWSKEY along with the number 6 to bring up the JAWS
Settings Center. Tab once to focus on the Tree view.
3.	Arrow down in the Tree View until you reach JAWS Verbosity, which
should be reported by JAWS as being "closed."
4.	Press Right Arrow to open this.
5.	Arrow down once to hear what level is set for Speech Verbosity. For
most folks, this is stated as Beginner. Mine is set to Intermediate, but
that doesn't really matter.
6.	Arrow down once to Configure Verbosity Levels, which JAWS will
report as being "closed." Press Right Arrow to open this branch of the tree.
7.	Assuming you are at the Beginner verbosity level, Arrow down once to
hear "Beginner...".
8.	Do not press Enter on this. Press the Spacebar instead. You should
now be in a list of 24 items.
9.	Press the letter h to focus on Help Balloon, which JAWS will report
as being checked. Press Space to uncheck this.
10.	Tab to and activate OK for as many times as you need to in order to
exit JAWS Settings.

 

This should do the trick and save you lots of aggravation during your Zoom
meetings.

 

Cordially,

 

Curtis Chong

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://nfbnet.org/pipermail/nfbcs_nfbnet.org/attachments/20260226/a6afb4ee/attachment.htm>

From steve.jacobson at outlook.com  Fri Feb 27 02:21:00 2026
From: steve.jacobson at outlook.com (Steve Jacobson)
Date: Fri, 27 Feb 2026 02:21:00 +0000
Subject: [NFBCS] Lately Zoom with JAWS 2026 are to verbose when announcing
 buttons and controls
In-Reply-To: <007001dca78e$9e2b1350$da8139f0$@gmail.com>
References: <000001dca6c7$3b2363b0$b16a2b10$@gmail.com>
 <00b301dca73c$888bec60$99a3c520$@gmail.com>
 <010901dca73f$94b37780$be1a6680$@gmail.com>
 <4c5001dca77b$537ae050$fa70a0f0$@comcast.net>
 <007001dca78e$9e2b1350$da8139f0$@gmail.com>
Message-ID: 
 <SN7P223MB05777575310C46528507BFDA9473A@SN7P223MB0577.NAMP223.PROD.OUTLOOK.COM>

Curtis,

I didn't see all of the emails in this thread, but does Speech on Demand stop this unwanted speech?  That used to be a temporary solution to quickly stop the announcements of who is entering or leaving.

Best regards,

Steve Jacobson


From: NFBCS <nfbcs-bounces at nfbnet.org> On Behalf Of Sean McMahon via NFBCS
Sent: Thursday, February 26, 2026 8:13 PM
To: 'NFB in Computer Science Mailing List' <nfbcs at nfbnet.org>
Cc: sean.mcmahon.dc at gmail.com
Subject: Re: [NFBCS] Lately Zoom with JAWS 2026 are to verbose when announcing buttons and controls

Ok, I have the pro scripts, but there wasn't an update available, so I am on the latest version.  I finally got the noise to stop after I unchecked the box for help text and help balloons under Zoom's user verbosity settings in the JAWS configuration file for Zoom.
Sean


From: NFBCS <nfbcs-bounces at nfbnet.org> On Behalf Of dandrews920--- via NFBCS
Sent: Thursday, February 26, 2026 6:55 PM
To: 'NFB in Computer Science Mailing List' <nfbcs at nfbnet.org>
Cc: dandrews920 at comcast.net
Subject: Re: [NFBCS] Lately Zoom with JAWS 2026 are to verbose when announcing buttons and controls

I am getting all kinds of extraneous codes in Zoom Workplace for Government!

Dave



From: NFBCS <nfbcs-bounces at nfbnet.org<mailto:nfbcs-bounces at nfbnet.org>> On Behalf Of Curtis Chong via NFBCS
Sent: Thursday, February 26, 2026 10:47 AM
To: 'NFB in Computer Science Mailing List' <nfbcs at nfbnet.org<mailto:nfbcs at nfbnet.org>>
Cc: Curtis Chong <chong.curtis at gmail.com<mailto:chong.curtis at gmail.com>>
Subject: [NFBCS] Lately Zoom with JAWS 2026 are to verbose when announcing buttons and controls

Greetings:

I believe I have a temporary fix for your problem short of having to purchase scripts from Hartgen Consultancy.

Here is a procedure which assumes you are using JAWS without the Zoom Pro scripts from Hartgen Consultancy.


  1.  Get into the Zoom Workspace program, but do not start a meeting or anything like that.
  2.  Press the JAWSKEY along with the number 6 to bring up the JAWS Settings Center. Tab once to focus on the Tree view.
  3.  Arrow down in the Tree View until you reach JAWS Verbosity, which should be reported by JAWS as being "closed."
  4.  Press Right Arrow to open this.
  5.  Arrow down once to hear what level is set for Speech Verbosity. For most folks, this is stated as Beginner. Mine is set to Intermediate, but that doesn't really matter.
  6.  Arrow down once to Configure Verbosity Levels, which JAWS will report as being "closed." Press Right Arrow to open this branch of the tree.
  7.  Assuming you are at the Beginner verbosity level, Arrow down once to hear "Beginner...".
  8.  Do not press Enter on this. Press the Spacebar instead. You should now be in a list of 24 items.
  9.  Press the letter h to focus on Help Balloon, which JAWS will report as being checked. Press Space to uncheck this.
  10. Tab to and activate OK for as many times as you need to in order to exit JAWS Settings.



This should do the trick and save you lots of aggravation during your Zoom meetings.



Cordially,



Curtis Chong



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://nfbnet.org/pipermail/nfbcs_nfbnet.org/attachments/20260227/cdc5dbfa/attachment.htm>

From chong.curtis at gmail.com  Fri Feb 27 05:31:57 2026
From: chong.curtis at gmail.com (Curtis Chong)
Date: Thu, 26 Feb 2026 22:31:57 -0700
Subject: [NFBCS] Lately Zoom with JAWS 2026 are to verbose when announcing
 buttons and controls
In-Reply-To: 
 <SN7P223MB05777575310C46528507BFDA9473A@SN7P223MB0577.NAMP223.PROD.OUTLOOK.COM>
References: <000001dca6c7$3b2363b0$b16a2b10$@gmail.com>
 <00b301dca73c$888bec60$99a3c520$@gmail.com>
 <010901dca73f$94b37780$be1a6680$@gmail.com>
 <4c5001dca77b$537ae050$fa70a0f0$@comcast.net>
 <007001dca78e$9e2b1350$da8139f0$@gmail.com>
  <SN7P223MB05777575310C46528507BFDA9473A@SN7P223MB0577.NAMP223.PROD.OUTLOOK.COM>
Message-ID: <003901dca7aa$64e0df50$2ea29df0$@gmail.com>

Hi Steve:

 

The problem I reported has nothing to do with knowing who is arriving and
leaving. Speech on Demand definitely stops those announcements.

 

Curtis

 

From: NFBCS <nfbcs-bounces at nfbnet.org> On Behalf Of Steve Jacobson via NFBCS
Sent: Thursday, February 26, 2026 7:21 PM
To: NFB in Computer Science Mailing List <nfbcs at nfbnet.org>
Cc: Steve Jacobson <steve.jacobson at outlook.com>
Subject: Re: [NFBCS] Lately Zoom with JAWS 2026 are to verbose when
announcing buttons and controls

 

Curtis,

 

I didn't see all of the emails in this thread, but does Speech on Demand
stop this unwanted speech?  That used to be a temporary solution to quickly
stop the announcements of who is entering or leaving.

 

Best regards,

 

Steve Jacobson

 

 

From: NFBCS <nfbcs-bounces at nfbnet.org <mailto:nfbcs-bounces at nfbnet.org> > On
Behalf Of Sean McMahon via NFBCS
Sent: Thursday, February 26, 2026 8:13 PM
To: 'NFB in Computer Science Mailing List' <nfbcs at nfbnet.org
<mailto:nfbcs at nfbnet.org> >
Cc: sean.mcmahon.dc at gmail.com <mailto:sean.mcmahon.dc at gmail.com> 
Subject: Re: [NFBCS] Lately Zoom with JAWS 2026 are to verbose when
announcing buttons and controls

 

Ok, I have the pro scripts, but there wasn't an update available, so I am on
the latest version.  I finally got the noise to stop after I unchecked the
box for help text and help balloons under Zoom's user verbosity settings in
the JAWS configuration file for Zoom. 

Sean

 

 

From: NFBCS <nfbcs-bounces at nfbnet.org <mailto:nfbcs-bounces at nfbnet.org> > On
Behalf Of dandrews920--- via NFBCS
Sent: Thursday, February 26, 2026 6:55 PM
To: 'NFB in Computer Science Mailing List' <nfbcs at nfbnet.org
<mailto:nfbcs at nfbnet.org> >
Cc: dandrews920 at comcast.net <mailto:dandrews920 at comcast.net> 
Subject: Re: [NFBCS] Lately Zoom with JAWS 2026 are to verbose when
announcing buttons and controls

 

I am getting all kinds of extraneous codes in Zoom Workplace for Government!

 

Dave

 

 

 

From: NFBCS <nfbcs-bounces at nfbnet.org <mailto:nfbcs-bounces at nfbnet.org> > On
Behalf Of Curtis Chong via NFBCS
Sent: Thursday, February 26, 2026 10:47 AM
To: 'NFB in Computer Science Mailing List' <nfbcs at nfbnet.org
<mailto:nfbcs at nfbnet.org> >
Cc: Curtis Chong <chong.curtis at gmail.com <mailto:chong.curtis at gmail.com> >
Subject: [NFBCS] Lately Zoom with JAWS 2026 are to verbose when announcing
buttons and controls

 

Greetings:

 

I believe I have a temporary fix for your problem short of having to
purchase scripts from Hartgen Consultancy.

 

Here is a procedure which assumes you are using JAWS without the Zoom Pro
scripts from Hartgen Consultancy.

 

1.	Get into the Zoom Workspace program, but do not start a meeting or
anything like that.
2.	Press the JAWSKEY along with the number 6 to bring up the JAWS
Settings Center. Tab once to focus on the Tree view.
3.	Arrow down in the Tree View until you reach JAWS Verbosity, which
should be reported by JAWS as being "closed."
4.	Press Right Arrow to open this.
5.	Arrow down once to hear what level is set for Speech Verbosity. For
most folks, this is stated as Beginner. Mine is set to Intermediate, but
that doesn't really matter.
6.	Arrow down once to Configure Verbosity Levels, which JAWS will
report as being "closed." Press Right Arrow to open this branch of the tree.
7.	Assuming you are at the Beginner verbosity level, Arrow down once to
hear "Beginner...".
8.	Do not press Enter on this. Press the Spacebar instead. You should
now be in a list of 24 items.
9.	Press the letter h to focus on Help Balloon, which JAWS will report
as being checked. Press Space to uncheck this.
10.	Tab to and activate OK for as many times as you need to in order to
exit JAWS Settings.

 

This should do the trick and save you lots of aggravation during your Zoom
meetings.

 

Cordially,

 

Curtis Chong

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://nfbnet.org/pipermail/nfbcs_nfbnet.org/attachments/20260226/19dfcab0/attachment.htm>

From chong.curtis at gmail.com  Fri Feb 27 05:34:06 2026
From: chong.curtis at gmail.com (Curtis Chong)
Date: Thu, 26 Feb 2026 22:34:06 -0700
Subject: [NFBCS] Lately Zoom with JAWS 2026 are to verbose when announcing
 buttons and controls
In-Reply-To: <007001dca78e$9e2b1350$da8139f0$@gmail.com>
References: <000001dca6c7$3b2363b0$b16a2b10$@gmail.com>
 <00b301dca73c$888bec60$99a3c520$@gmail.com>
 <010901dca73f$94b37780$be1a6680$@gmail.com>
 <4c5001dca77b$537ae050$fa70a0f0$@comcast.net>
 <007001dca78e$9e2b1350$da8139f0$@gmail.com>
Message-ID: <006901dca7aa$b1502210$13f06630$@gmail.com>

Hello:

 

The current version of the Pro Scripts is 111. Insert q gives you that
information.

 

Glad the problem is solved on your end.

 

Kind regards,

 

Curtis Chong

 

 

From: NFBCS <nfbcs-bounces at nfbnet.org> On Behalf Of Sean McMahon via NFBCS
Sent: Thursday, February 26, 2026 7:13 PM
To: 'NFB in Computer Science Mailing List' <nfbcs at nfbnet.org>
Cc: sean.mcmahon.dc at gmail.com
Subject: Re: [NFBCS] Lately Zoom with JAWS 2026 are to verbose when
announcing buttons and controls

 

Ok, I have the pro scripts, but there wasn't an update available, so I am on
the latest version.  I finally got the noise to stop after I unchecked the
box for help text and help balloons under Zoom's user verbosity settings in
the JAWS configuration file for Zoom. 

Sean

 

 

From: NFBCS <nfbcs-bounces at nfbnet.org <mailto:nfbcs-bounces at nfbnet.org> > On
Behalf Of dandrews920--- via NFBCS
Sent: Thursday, February 26, 2026 6:55 PM
To: 'NFB in Computer Science Mailing List' <nfbcs at nfbnet.org
<mailto:nfbcs at nfbnet.org> >
Cc: dandrews920 at comcast.net <mailto:dandrews920 at comcast.net> 
Subject: Re: [NFBCS] Lately Zoom with JAWS 2026 are to verbose when
announcing buttons and controls

 

I am getting all kinds of extraneous codes in Zoom Workplace for Government!

 

Dave

 

 

 

From: NFBCS <nfbcs-bounces at nfbnet.org <mailto:nfbcs-bounces at nfbnet.org> > On
Behalf Of Curtis Chong via NFBCS
Sent: Thursday, February 26, 2026 10:47 AM
To: 'NFB in Computer Science Mailing List' <nfbcs at nfbnet.org
<mailto:nfbcs at nfbnet.org> >
Cc: Curtis Chong <chong.curtis at gmail.com <mailto:chong.curtis at gmail.com> >
Subject: [NFBCS] Lately Zoom with JAWS 2026 are to verbose when announcing
buttons and controls

 

Greetings:

 

I believe I have a temporary fix for your problem short of having to
purchase scripts from Hartgen Consultancy.

 

Here is a procedure which assumes you are using JAWS without the Zoom Pro
scripts from Hartgen Consultancy.

 

1.	Get into the Zoom Workspace program, but do not start a meeting or
anything like that.
2.	Press the JAWSKEY along with the number 6 to bring up the JAWS
Settings Center. Tab once to focus on the Tree view.
3.	Arrow down in the Tree View until you reach JAWS Verbosity, which
should be reported by JAWS as being "closed."
4.	Press Right Arrow to open this.
5.	Arrow down once to hear what level is set for Speech Verbosity. For
most folks, this is stated as Beginner. Mine is set to Intermediate, but
that doesn't really matter.
6.	Arrow down once to Configure Verbosity Levels, which JAWS will
report as being "closed." Press Right Arrow to open this branch of the tree.
7.	Assuming you are at the Beginner verbosity level, Arrow down once to
hear "Beginner...".
8.	Do not press Enter on this. Press the Spacebar instead. You should
now be in a list of 24 items.
9.	Press the letter h to focus on Help Balloon, which JAWS will report
as being checked. Press Space to uncheck this.
10.	Tab to and activate OK for as many times as you need to in order to
exit JAWS Settings.

 

This should do the trick and save you lots of aggravation during your Zoom
meetings.

 

Cordially,

 

Curtis Chong

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://nfbnet.org/pipermail/nfbcs_nfbnet.org/attachments/20260226/a1ab30a4/attachment.htm>

From mohammad-sule.maidawa at imt-atlantique.fr  Fri Feb 27 10:30:59 2026
From: mohammad-sule.maidawa at imt-atlantique.fr (Mohammad Sule MAIDAWA)
Date: Fri, 27 Feb 2026 11:30:59 +0100 (CET)
Subject: [NFBCS] 12th European Conference on Service-Oriented and Cloud-Edge
 Continuum (ESOCC 2026)
Message-ID: 
 <836789210.42142078.1772188259290.JavaMail.zimbra@imt-atlantique.fr>

====================================================================
CALL FOR PAPERS
====================================================================

ESOCC 2026
12th European Conference on Service-Oriented and Cloud Computing
7–8 September 2026 | Free University of Bozen–Bolzano, Italy

Conference website:
https://conf.researchr.org/home/esocc-2026

Submission deadline:
27 March 2026
====================================================================

ABOUT THE CONFERENCE
--------------------
ESOCC is the premier European forum for advances in Service-Oriented
Computing, Cloud and Edge Computing, and AI-driven systems. It brings
together researchers and practitioners from academia and industry.

ESOCC 2026 invites original submissions on Service-Oriented Computing,
Cloud and Edge Computing, and AI-driven systems, including (but not
limited to):

TOPICS OF INTEREST
------------------
- Applications for Service-Oriented and Edge–Cloud Continuum
  (e.g., smart cities, health, energy, finance, scientific computing)
- Generative AI and Machine Learning for service-oriented and
  cloud-native systems
- AI/ML services and LLM-based cloud platforms
- Distributed intelligence at the Edge, including Federated Learning
- Blockchain technologies for service-oriented and cloud–edge systems
- Business models, processes, brokerage, and cloud marketplaces
- Governance, privacy, security, trust, and quality in the
  Edge–Cloud Continuum

SUBMISSION TRACKS
-----------------
- Regular Research Papers (up to 15 pages, LNCS format)
- PhD Symposium Papers (up to 12 pages)
- Projects and Industry Reports (1–2 pages)

PUBLICATION
-----------
All accepted papers will appear in the Springer LNCS proceedings.
Selected papers will be invited to submit extended versions to a
special issue of the Springer Journal of Cluster Computing.

Authors should follow Springer’s Instructions for Authors and use the
official LaTeX or Word templates available on the conference website.

SUBMISSION SYSTEM
-----------------
EasyChair:
https://easychair.org/my/conference?conf=ecsa2026

IMPORTANT DATES
---------------
- Paper submission deadline: 27 March 2026
- Notification of acceptance: 20 May 2026
- Camera-ready papers due: 20 June 2026
- Conference dates: 7–8 September 2026

JOURNAL SPECIAL ISSUE
---------------------
A journal special issue is planned at the Springer Journal on Cluster
Computing (Impact Factor 4.4, 2022). Authors of selected accepted papers
will be invited to submit extended versions.

CONTACT
-------
For further details, please visit:
https://conf.researchr.org/home/esocc-2026

For questions, please contact the conference chairs.
====================================================================

From nadia.brancati at icar.cnr.it  Fri Feb 27 11:34:51 2026
From: nadia.brancati at icar.cnr.it (Nadia Brancati)
Date: Fri, 27 Feb 2026 12:34:51 +0100
Subject: [NFBCS] Call for Research Contributions- Join Us at the 6th IEEE
 ICTS4eHealth
Message-ID: 
 <CANxf_fWRKmaaHmZu3QdpLXUS6ktL0zmne-amzX92zMF8bhH1JA@mail.gmail.com>

[Apologies if you receive multiple copies of this CFP]
Dearr colleagues,
We are delighted to announce the Call for Papers for the 6th edition
of IEEE ICTS4eHealth, held in conjunction with IEEE ISCC 2026.

We warmly invite original, high-quality submissions that contribute to
advancing the state of the art in Information and Communication
Technologies for healthcare. Join us in Portugal to showcase your
research, exchange insights, and connect with leading experts in the
field.


Yours sincerely,
IEEE ICTS4eHealth Organization

=======================================================

6th Edition of IEEE International Conference on ICT Solutions for e-Health

ICTS4eHealth 2026

Algarve, Portugal - June 23-26, 2026
https://icts4ehealth.icar.cnr.it

In conjunction with the 31st IEEE Symposium on Computers and Communications

All paper submissions must be done through EDAS by using the link
https://edas.info/N35010

=======================================================

MISSION:
-----------------------------------------------------------------------------------------------
E-Health is one of the major research topics that have been attracting
cross-disciplinary research groups.
The deployment of new emerging ICT technologies for Health, especially
based on Cloud computing, Internet of Things (IoT), and Artificial
Intelligence (AI), is attracting the interest of many researchers.
Following the success of five workshop editions and two years as an
International IEEE Conference, we are now proud to announce the third
edition of this popular event dedicated to ICT solutions for e-Health.
The conference will bring together researchers from academia,
industry, government, and medical centers in order to present the
state of the art in the emerging area of the use of cloud systems in
connected health infrastructure and applications, and the use of IoT
and AI techniques in the area of e-Health.

TOPICS:
-----------------------------------------------------------------------------------------------
Conference topics include (but are not limited to):

- Artificial Intelligence & Data Analytics for eHealth
Artificial Intelligence for eHealth
Generative AI for Longitudinal Data
AI for Precision Medicine
Knowledge Discovery and Decision Support
Biomedical Data Processing
Data/Visual Mining for Diagnostics
Computer-Aided Diagnostics
Intelligent Bio-signal Interpretation

- Sensing, Wearables & Internet of Medical Things (IoMT)
Internet of Things (IoT) applications for eHealth
Biosensors and Sensor Networks
Wearable Devices and Smart Sensors
Monitoring of Vital Functions
Sensor-based mHealth applications

- Signal, Image & Multimodal Processing
Advanced Bio-signal Processing
Signal Processing for Health
Image Analysis for Health
Medical Imaging Analysis
Generative Models for Medical Imaging
Image-to-Image Translation
Computer Vision and Pattern Recognition
Advanced Medical Visualization
Multimodal Data Fusion

- Digital Health Systems & Architectures
Cloud Computing for eHealth
Distributed and Edge Computing for Healthcare
Telehealth, Telemonitoring and Telediagnostics
e-Healthcare, m-Healthcare, x-Health
Extended and Digital Health Ecosystems
AI-enabled Digital Twins for Healthcare

- Assistive Technologies & Human-Centered Design
Assistive Technology and Assisted Living
Personalized Assistive Technologies
User-Centered Design and Usability
e-Accessibility and Web Accessibility
Assistive Technologies for Urban and Smart Environments

- Security, Privacy & Trustworthy eHealth
Security and Privacy in eHealth
Ethical, Legal and Social Implications (ELSI)
Trustworthy AI for Healthcare
Explainable/Interpretable AI for Health
Federated/Privacy-Preserving Learning

- Modeling, Simulation & Clinical Applications
Healthcare Modeling and Simulation
Computational Biology and Bioinformatics
Modeling and Simulation in BM
Improved Therapeutic and Rehabilitation Methods


IMPORTANT DATES:
-----------------------------------------------------------------------------------------------
- Submission deadline: MARCH 15, 2026
- Notification of paper acceptance: MARCH 31, 2026
- Conference Dates: June 23-26, 2026

PAPER SUBMISSION:
-----------------------------------------------------------------------------------------------
Manuscripts should describe original work and should be no more than 7
pages in the IEEE double-column proceedings format, including tables,
figures and references. Download manuscript templates for IEEE
conference proceedings from:
https://www.ieee.org/conferences/publishing/templates.html
Note that accepted papers up to 6 pages will be published with no
additional charge. Exceeding pages will be charged an additional fee.
Papers exceeding 7 pages will not be accepted.
At least one author of each accepted paper is required to register to
the conference and present the paper. Only registered and presented
papers will be published in the conference proceedings.
In IEEE ICTS4eHealth 2026, as well as in IEEE ISCC 2026, all
submissions must be done through EDAS.
Accepted papers will be included in the proceedings of ISCC 2026, of
which ICTS4eHealth conference is a co-located event, and will be
submitted for inclusion to IEEE Xplore. The ICTSeHealth and ISCC
proceedings have been indexed in the past by ISI, DBLP and Scopus.
This makes the ISCC conference one of the publication venues with very
high visibility and impact in both Computer and Communications areas.


BEST PAPER AWARD:
-----------------------------------------------------------------------------------------------
A "Best Paper Award" Certificate will be conferred on the author(s) of
a paper presented at the conference, selected by the Chairs based on
scientific significance, originality and outstanding technical quality
of the paper, as assessed also by the evaluations of the members of
the Program Committee.


SPECIAL ISSUES:
-----------------------------------------------------------------------------------------------
Authors of selected papers may be invited to submit extended versions
of their papers for publication as full journal papers in special
issues organized in prestigious indexed journals.


STEERING COMMITTEE:
-----------------------------------------------------------------------------------------------
- Antonio Celesti, University of Messina, Italy;
- Ivanoe De Falco, ICAR-CNR, Italy;
- Giovanna Sannino, ICAR-CNR, Italy;
- Massimo Villari, University of Messina, Italy.


ORGANIZATION:
-----------------------------------------------------------------------------------------------
General chair:
- Daniele Raví, University of Messina, Italy

Technical Program Co-Chairs:
- Brancati Nadia, ICAR-CNR, Italy
- Francesco La Rosa, University of Messina, Italy
- Laura Verde, University of Campania "L. Vanvitelli”, Italy
- Saber Sami, University of East Anglia, UK
- Hugo Plácido da Silva, Instituto de Telecomunicações, Portugal

Publicity Co-Chairs:
- Salvatore Giugliano, ICAR-CNR, Italy
- Gabriele Morabito, University of Messina, Italy


Please visit https://icts4ehealth.icar.cnr.it for more information,
and, if you have any questions, kindly get back to us by sending an
email to ICTS4eHealth at icar.cnr.it

Kind regards,
IEEE ICTS4eHealth Organization

########################################################################





-- 
Nadia Brancati
Senior Researcher @ AI-ISA Lab
<https://www.icar.cnr.it/en/gruppi-di-ricerca/artificial-intelligence-in-image-and-signal-analysis/>
Institute for High Performance Computing and Networking - National Research
Council of Italy (CNR - ICAR)
Via P. Castellino, 111 - 80131 Napoli
Tel. 081.6139228
nadia.brancati at icar.cnr.it
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://nfbnet.org/pipermail/nfbcs_nfbnet.org/attachments/20260227/5a626b03/attachment-0001.htm>

From carcione at access.net  Fri Feb 27 14:14:35 2026
From: carcione at access.net (carcione at access.net)
Date: Fri, 27 Feb 2026 09:14:35 -0500
Subject: [NFBCS] Lately Zoom with JAWS 2026 are to verbose when announcing
 buttons and controls
In-Reply-To: <007001dca78e$9e2b1350$da8139f0$@gmail.com>
References: <000001dca6c7$3b2363b0$b16a2b10$@gmail.com>
 <00b301dca73c$888bec60$99a3c520$@gmail.com>
 <010901dca73f$94b37780$be1a6680$@gmail.com>
 <4c5001dca77b$537ae050$fa70a0f0$@comcast.net>
 <007001dca78e$9e2b1350$da8139f0$@gmail.com>
Message-ID: <00c801dca7f3$66ec83a0$34c58ae0$@access.net>

How do I get to the settings you mention?  I'm using Jaws Home Annual, and I
see Zoom settings under the Manage Applications menu, but I can't find any
checkboxes.

Tracy

 

From: NFBCS <nfbcs-bounces at nfbnet.org> On Behalf Of Sean McMahon via NFBCS
Sent: Thursday, February 26, 2026 9:13 PM
To: 'NFB in Computer Science Mailing List' <nfbcs at nfbnet.org>
Cc: sean.mcmahon.dc at gmail.com
Subject: Re: [NFBCS] Lately Zoom with JAWS 2026 are to verbose when
announcing buttons and controls

 

Ok, I have the pro scripts, but there wasn't an update available, so I am on
the latest version.  I finally got the noise to stop after I unchecked the
box for help text and help balloons under Zoom's user verbosity settings in
the JAWS configuration file for Zoom. 

Sean

 

 

From: NFBCS <nfbcs-bounces at nfbnet.org <mailto:nfbcs-bounces at nfbnet.org> > On
Behalf Of dandrews920--- via NFBCS
Sent: Thursday, February 26, 2026 6:55 PM
To: 'NFB in Computer Science Mailing List' <nfbcs at nfbnet.org
<mailto:nfbcs at nfbnet.org> >
Cc: dandrews920 at comcast.net <mailto:dandrews920 at comcast.net> 
Subject: Re: [NFBCS] Lately Zoom with JAWS 2026 are to verbose when
announcing buttons and controls

 

I am getting all kinds of extraneous codes in Zoom Workplace for Government!

 

Dave

 

 

 

From: NFBCS <nfbcs-bounces at nfbnet.org <mailto:nfbcs-bounces at nfbnet.org> > On
Behalf Of Curtis Chong via NFBCS
Sent: Thursday, February 26, 2026 10:47 AM
To: 'NFB in Computer Science Mailing List' <nfbcs at nfbnet.org
<mailto:nfbcs at nfbnet.org> >
Cc: Curtis Chong <chong.curtis at gmail.com <mailto:chong.curtis at gmail.com> >
Subject: [NFBCS] Lately Zoom with JAWS 2026 are to verbose when announcing
buttons and controls

 

Greetings:

 

I believe I have a temporary fix for your problem short of having to
purchase scripts from Hartgen Consultancy.

 

Here is a procedure which assumes you are using JAWS without the Zoom Pro
scripts from Hartgen Consultancy.

 

1.	Get into the Zoom Workspace program, but do not start a meeting or
anything like that.
2.	Press the JAWSKEY along with the number 6 to bring up the JAWS
Settings Center. Tab once to focus on the Tree view.
3.	Arrow down in the Tree View until you reach JAWS Verbosity, which
should be reported by JAWS as being "closed."
4.	Press Right Arrow to open this.
5.	Arrow down once to hear what level is set for Speech Verbosity. For
most folks, this is stated as Beginner. Mine is set to Intermediate, but
that doesn't really matter.
6.	Arrow down once to Configure Verbosity Levels, which JAWS will
report as being "closed." Press Right Arrow to open this branch of the tree.
7.	Assuming you are at the Beginner verbosity level, Arrow down once to
hear "Beginner...".
8.	Do not press Enter on this. Press the Spacebar instead. You should
now be in a list of 24 items.
9.	Press the letter h to focus on Help Balloon, which JAWS will report
as being checked. Press Space to uncheck this.
10.	Tab to and activate OK for as many times as you need to in order to
exit JAWS Settings.

 

This should do the trick and save you lots of aggravation during your Zoom
meetings.

 

Cordially,

 

Curtis Chong

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://nfbnet.org/pipermail/nfbcs_nfbnet.org/attachments/20260227/75cd4b47/attachment.htm>

From charles.vanek at gmail.com  Sat Feb 28 15:08:29 2026
From: charles.vanek at gmail.com (Charles Vanek)
Date: Sat, 28 Feb 2026 09:08:29 -0600
Subject: [NFBCS] Accessible AI agents
In-Reply-To: 
 <CACHadJ3CqfvXgdt43SJVcHHFsh-0wiBdomyvrTTNpSMV6aE5tw@mail.gmail.com>
References: 
 <CACHadJ3CqfvXgdt43SJVcHHFsh-0wiBdomyvrTTNpSMV6aE5tw@mail.gmail.com>
Message-ID: <C80389F4-1035-48FC-8A27-F6A89EE6AADC@gmail.com>

Hi Bhavya, knowing what you are looking to create may result in better answers.  
Assuming you are looking to generate specifications and cod scripts, applications or explore existing repositories/files, etc. You may find VS Code is the place to start working with Agentic AI models. 

There’s some setup you’ll need to do one time such as enabling accessibility mode with control+alt+Z, installing coding assistant extensions such as Google Gemini’s free assistant. I use Github Copilot Enterprise which has a wide range of models to use from free all the way up to Claude Opus 4.6 (FastMode). The nice thing about learning VS Code and using free/paid agents is the interaction with files and the interface doesn’t change you simply select the model you want or set it to Auto. Thus you can write and refine specs with a powerful Claude Opus model but then switch to a lower cost OpenAI CodeX, Claude Sonnet or Gemini to write your code, markdown docs, etc. It’s also very easy to write with one model then switch to a different model and ask it to do an Adversarial Code Review of whatever is created in the folder.

Once you are set up in VS Code with accessible mode, extensions installed for AI here’s the basic steps:
1. Open a Folder to work in, you should be asked if you Trust the files, do so if you have an Empty or Trusted folder.
2. Press Control+Shift+I to place the cursor into the prompt box and then simply tell it to do something. E.g. Write for me an HTML page that is WCAG 2.0 compliant and explains how to use agentic AI agents in VS Code.
3. Press Alt+F2 to open up an Accessible view of what the model has output. 

NOTE: The models are going to ask to execute specific commands such as Terminal commands when connected to a terminal such as PowerSheLL, WSL or the MacOS terminal.  You’ll have to Allow these via Control+Enter as you review them, but you can also always allow certain operations to speed things up.

This is a very brief look into what can be possible in VS Code. I’d suggest anyone getting started should review VS Code accessibility docs as well as set yourself up with a browser based ChatGPT, Claude or Gemini chat session to help you along your journey.

 Best of luck,
CV

Sent from my iPhone


> On Feb 26, 2026, at 1:53 AM, Bhavya shah via NFBCS <nfbcs at nfbnet.org> wrote:
> 
> Have you tried agentic AI tools like MultiOn, Claude Cowork, OpenClaw, Microsoft Copilot, etc? How has your experience been as a screen reader user? I am interested in in getting started with one of these and would prefer one that is both capable and accessible.
> 
>  
> Warmly,
> 
> Bhavya Shah | M.S. AI & B.S. Math/CS, Stanford University
> 
> LinkedIn <https://www.linkedin.com/in/bhavyashah125/> | Instagram <https://www.instagram.com/mynameisnotjavier> | Website <https://bhavyashahcomedy.com/>_______________________________________________
> NFBCS mailing list
> NFBCS at nfbnet.org
> http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org
> To unsubscribe, change your list options or get your account info for NFBCS:
> http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/charles.vanek%40gmail.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://nfbnet.org/pipermail/nfbcs_nfbnet.org/attachments/20260228/4923580f/attachment.htm>

From ljmaher03 at outlook.com  Sat Feb 28 15:23:19 2026
From: ljmaher03 at outlook.com (Louis Maher)
Date: Sat, 28 Feb 2026 15:23:19 +0000
Subject: [NFBCS] Audiom: Evaluating if digital interactive alternate text
 provides the
 same information as visual spatial maps and diagrams
In-Reply-To: 
 <DSWPR14MB958149138FD62FCBF95FE7C80DAA70A@DSWPR14MB958149.namprd14.prod.outlook.com>
References: 
 <DSWPR14MB958149D5A87A05C0505C667A74AA70A@DSWPR14MB958149.namprd14.prod.outlook.com>
 <DSWPR14MB958149138FD62FCBF95FE7C80DAA70A@DSWPR14MB958149.namprd14.prod.outlook.com>
Message-ID: 
 <DSWPR14MB958149DCF0C766BB6FF4C3E112AA70A@DSWPR14MB958149.namprd14.prod.outlook.com>

Hello,

One of the speakers at the February 22, 2026 Science and Engineering / National Association of Blind Students STEM seminar was Brandon Biggs. The title of his talk was "Audiom: Evaluating if digital interactive alternate text provides the same information as visual spatial maps and diagrams". The talk abstract and speaker introduction are pasted below my signature.

Brandon wrote: "I am looking for blind folks in need of using spatial diagrams for education or professionally, so if you know of anyone, especially around maps, please let me know.".

Audiom seeks to give the blind and partially sighted as much information audibly, and through magnification, as can be obtained visually from maps and diagrams.

A Recording of the STEM meeting is available at
"2026-02-22 SED seminar_Recording.mp3<https://drive.google.com/file/d/1TO2CQ-Eq_X1ufKYQqvRcMvwFpl5eg8wf/view?usp=drive_link>". Once this link is accessed, once your virtual cursor is off, hitting enter on this file produces a "play" dialog, and tabbing around the "play" dialog will bring you to a download button.

While I am happy to recommend the entire seminar, Brandon's thirty-minute talk starts around 58 minutes and 26 seconds into the program.

Brandon's contact information is:

Brandon Biggs
CEO
XR Navigation<https://xrnavigation.io/>
Phone: 650-833-9394
brandon.biggs at xrnavigation.io<mailto:brandon.biggs at xrnavigation.io>
Official Esri Partner<https://www.esri.com/partners/xr-navigation-a2TUU00000102CX2AY>, and in partnership with the National Federation of the Blind<https://nfb.org/>.

Regards
Louis Maher
Phone: 713-444-7838
Email: ljmaher03 at outlook.com<mailto:ljmaher03 at outlook.com>

--------------
Brandon's title, abstract, and speaker introduction, are:

Title: Audiom: Evaluating if digital interactive alternate text provides the same information as visual spatial maps and diagrams

Speaker: Brandon Biggs (brandon.biggs at xrnavigation.io<mailto:brandon.biggs at xrnavigation.io>)

Abstract: Sighted people view over 300 digital maps a year, in contrast to blind people, who view less than one map a year on average. Only around 17.5% of blind
people have ever viewed a map of any kind as a blind person. This talk will present Audiom, an interactive alternate text game-like digital interface that
can allow the non-visual viewing and creation of diverse types of spatial information, such as maps and diagrams. Over 13 academic studies and co-designs
have been performed on over 150 blind and 40 sighted participants to create and evaluate Audiom. The presentation will then discuss how Audiom is being
compared with visual digital maps and diagrams. The objective of this work is to clearly define what it means for a non-visual text map to serve the equivalent
purpose to a visual map to meet the Web Content Accessibility Guidelines. The results of this work should inform digital accessibility legislation to facilitate
equal educational and employment opportunities for professions require the use of spatial information.

Links to Audiom:
Personal use:
https://audiom.net<https://audiom.net/>
Commercial use:
https://xrnavigation.io<https://xrnavigation.io/>

Speaker Introduction: Brandon Biggs is an entrepreneur, researcher, inclusive designer, developer, and life-long learner. He is the CEO of XR Navigation, an Engineer at the
Smith-Kettlewell Eye Research Institute, Co-Founder and board treasurer at Sonja Biggs Educational Services Inc., and a PhD student at the Georgia institute
of Technology. In 2016, he received his bachelor's in music from California State University East Bay, in 2019 he received his master's in Inclusive Design
from the Ontario College of Art and Design University, and in 2021, began his PhD in Human Centered Computing from the Georgia Institute of Technology.
He is almost completely blind from Leber's Congenital Amaurosis (LCA). His projects and ventures center around building tools to solve some of the most
difficult problems in the blindness field. He leverages his lived experience coupled with human centered inclusive design principles to create solutions
that create lasting and sustainable impact. To achieve this goal, Brandon is half entrepreneur and half academic.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://nfbnet.org/pipermail/nfbcs_nfbnet.org/attachments/20260228/2c239efd/attachment.htm>

