Accessibility Industry Update: May 2026
From the Desk of the Editor
Conference season may be behind us, but the regulatory roller coaster hasn’t stopped quite yet.
This month, we unpack the fallout and reactions to the recent ADA Title II deadline extension, examine the growing legislative pushback against serial accessibility litigation across multiple states, discuss yet another last-minute compliance extension, and share some of the most insightful writing we have found on the web. Let’s get into it!
Standing Notes
If you are new here, welcome. We compile this update every month to keep you informed on the changing landscape of digital accessibility. Whether you are a developer, product manager, QA specialist, leader, or somewhere in between, we want to give you the context you need to stay in the know. As always, reach out if you think we missed something, or share the link with your colleagues or partners who may benefit from some or all of this information. You can also sign up to receive these accessibility updates via email.
– The QualityLogic Editorial Team
What’s Inside
- Another Accessibility Update, Another Deadline Extension
- Reactions to the DOJ Deadline Extension
- Our Thoughts
- Legal Stuff
- What We’ve Been Reading
- Jobs and Opportunities
- Learn More
Another Accessibility Update, Another Deadline Extension
Just a week before recipients of U.S. Health and Human Services (HHS) funding with 15 or more employees were supposed to be in compliance with WCAG 2.1, a last-minute extension was published. Their justification for doing so mirrors the DOJ’s justification nearly word for word. “This action responds to concerns that a significant number of recipients of federal financial assistance, such as community health centers, large and small hospitals, and primary care centers, among other recipients, would not be able to meet the upcoming deadlines.”
Additionally, they clarified that the extension “also aligns Section 504 requirements with those in the Department of Justice’s (DOJ) parallel rulemaking for Title II of the Americans with Disabilities Act, ensuring consistency for entities covered by both laws.”
Given the recent trend of regulatory delays across the board, this comes as no surprise, and our perspective remains unchanged in that it matters less than most people think.
Reactions to the DOJ Deadline Extension
In our last edition, we briefly covered the Department of Justice pushing back the ADA Title II digital accessibility deadlines. That analysis came directly following the announcement.
Now that the dust has settled, we can take a deeper look into the numerous perspectives on the change based on what we’ve been hearing both from our customers and the larger community.
Predictably, government organizations that we are talking to are quite happy that they have more time to secure resources and execute remediation plans.
Most everyday users of assistive technology either do not seem to know much about the deadline, or do not really care how it is enforced so long as they can fully access the digital services that their tax dollars fund. “The deadline was never the point,” one person told us.
However, many seasoned advocates are annoyed and concerned. A broad coalition of disability rights organizations, led by the American Association of People with Disabilities (AAPD), issued a statement unequivocally opposing the delay. They argue that the delay undermines significant efforts already underway and bypasses standard notice-and-comment procedures.
Meanwhile, there is a widely circulating opinion piece in the Austin Chronicle by Sharron Rush (Knowbility) making a point that should not be controversial: Nobody Should Be Denied Digital Access. Rush points out that the ADA’s promise of universal access was never partisan, and backing away from enforcement has a chilling effect on the momentum local governments were building. To make it partisan is merely going to slow things down. As we like to say in our trainings, disability is something that will impact everyone at some point in their lives: “we are ultimately just temporarily abled.”
Our Thoughts
The one thing the IFR did get right is that it made this statement. “Regardless of the compliance dates, covered entities have an ongoing obligation to ensure that their services, programs, and activities offered using web content and mobile apps are accessible to individuals with disabilities in accordance with their existing obligations under title II of the ADA.”
The underlying obligation is not new, it is not suspended, and it has been the law for more than three decades. The question is more along the lines of the extent to which enforcement will happen. Encouragingly, many universities and local governments have not halted their efforts, because at least as of right now, the budgeted money is still there to do the work.
Legal Stuff
The legislative pushback against serial web accessibility lawsuits is officially gaining traction across the country.
We talked more about Missouri’s SB 907, an act against abusive website accessibility litigation, back in March. It has now been signed into law and takes effect August 28, 2026. Once that happens, businesses facing claims of digital inaccessibility will have a 90-day safe harbor period after they receive notice to correct the alleged violations before litigation can proceed.
A similar law from Utah, SB 68, was signed by the governor and went into effect on May 6, 2026. While Missouri’s law focuses on allowing businesses to counter-sue and establish a presumption of abuse if they remediate within 90 days, Utah’s SB 68 introduces its own mechanisms to deter lawsuits that prioritize monetary settlements over actual website accessibility improvements.
Georgia’s HB 1470, which is quite similar, passed the legislature and is awaiting signature from the governor. All signs point to this passing soon.
These state-level actions are largely a response to recurrent incidents like the recent investigation by MSN detailing how a single plaintiff filed 1,800 disability lawsuits against Southern California shops, leaving business owners fed up with the legal system.
Proactively speaking, you may recall that Virginia passed a law in March of 2025 (HB 2541) requiring vendors to provide a VPAT ACR authored by a qualified accessibility expert prior to being used by the state. Vendors must also submit a plan for remediating any identified gaps in a timely manner. The deadline for this requirement matches the previous DOJ deadline of April 24, 2026, for institutions serving a population greater than 50,000. So, this is now officially implemented. It will be interesting to see what comes of this as a vantage point for the rest of the state governments that must do so in a little under a year.
What We’ve Been Reading
- Think About What You Feed Into Generative AI BEFORE The Demand Letter Arrives – Sheri Byrne-Haber: A warning for accessibility managers about the legal risks of feeding bug lists or audit findings into public AI tools, potentially waiving attorney-client privilege.
- Why Accessibility is the Infrastructure for AI Readiness – Applause: Explores how building accessible, semantically structured digital products natively prepares your infrastructure for future AI integration. Add this to the list of arguments to make in favor of accessibility for those that do not see it as a priority.
- The State of Digital Quality in Accessibility 2026 – Applause: A comprehensive survey showing that while 79% of organizations use AI to improve accessibility, human validation remains absolutely essential to catch critical blockers. There also seems to be a difference in presumption of capability vs. measurable outcomes.
- ACSES Releases First Insights Report on Disability in Higher Education – Centre for Accessibility: An inaugural report reviewing Australian universities against disability regulations, finding that while 93% exceed global benchmarks for homepage accessibility, deep gaps remain when it comes to documents.
- keyboard testing with the POWER OF AI! – Steve Faulkner: A witty, open-source experiment poking fun at vendors slapping “AI powered” labels onto basic accessibility testing tools.
- Student Creates More Accessible Digital Map of University of Michigan – GovTech: A great story about a student using AI assistance to build a custom, accessible campus navigation app when existing institutional maps fell short.
- Upcoming Changes to AI Features in JAWS and Fusion – Vispero: An update outlining new age verification and account requirements for using AI features within the JAWS ecosystem.
- 20 Years of NVDA Development: A Data-Driven Retrospective – NV Access: A celebration of two decades of the free, open-source screen reader, highlighting massive community contributions and a steady growth in code changes with a brief explanation on current processes.
- 9 Accessibility Myths and Pushbacks (And How to Answer Them) – Stéphanie Walter: An amazing post with a detailed look at the most common misconceptions about accessibility, backed by real experience as an accessibility specialist, and exactly how to refute them.
- AI Doesn’t Fix Accessible Systems, It Depends on Them – Anna E. Cook: Tackling yet another myth, this piece breaks down why AI is not a magic wand for broken accessibility, and why it actually requires well-structured, semantically sound systems to function properly.
- There is no need to include ‘navigation’ in your navigation labels – tempertemper: A common issue we constantly flag during audits, making this a surprisingly useful reminder. Screen readers already announce the navigation role natively, so adding the word “navigation” to your label creates annoying redundancy. Pro tip: the same applies to other landmark regions.
- Ask AIMee – WebAIM: WebAIM just launched AIMee, an AI chatbot trained specifically on a curated dataset of high-quality accessibility information to help answer your WCAG and remediation questions.
- New bookmarklet: Structure Revealer – a11y-tools: A handy new bookmarklet that visually exposes the underlying structure of a webpage, making it easier to spot semantic issues and testing gaps on the fly.
- Playwright Accessibility Testing: What axe and Lighthouse Miss – David Mello: A stark reminder that automated tools only catch around 30 to 40 percent of WCAG violations. Blindly accepting AI-suggested fixes to turn scanners green is a dangerous practice that ignores user impact.
Jobs and Opportunities
- Digital Accessibility Specialist at City of Chicago – Department of Technology & Innovation – Chicago, IL (On-Site)
- Vice President, Accessibility Team Lead at BNY – Denver, CO or Remote
- Digital Accessibility Lead at System One – Remote
- Document Accessibility Remediation Specialist at Software Technology Inc – Remote
- Accessibility QA Engineer / AI Trainer at DataAnnotation – Philadelphia, PA
QualityLogic does not explicitly endorse these companies. Should you decide to seek a position with one of them, please perform your own due diligence.
Looking for more opportunities? Check out A11yJobs, Indeed, and LinkedIn.
Thanks for Reading!
That’s a wrap for this month. As always, let us know if you think we’ve missed something, or share the link with your colleagues or partners who may benefit from some or all of this information. You can also sign up to receive these accessibility updates via email.
Interested in More Information About QualityLogic?
Let us know how we can help out – we love to share ideas! (Or click here to subscribe to our monthly newsletter email, free from spam.)