QualityLogic logo, Click to navigate to Home
QualityLogic logo, Click to navigate to Home

Accessibility Industry Update: April 2026

Home » Blogs/Events » Accessibility Industry Update: April 2026

From the Desk of the Editor

With conference season mostly behind us, it’s time to get back into the swing of things. The first major compliance deadline for the ADA Title II web and mobile app rule was set to hit at the end of the month, but the DOJ stepped in at the last minute with an Interim Final Rule pushing it back by a year. More on that below. In the meantime, WebAIM dropped their WebAIM Million report analyzing the top 1 million websites for accessibility. The results are not particularly flattering. So why are we still stuck? This month, we unpack the report to try to answer that question, look at the renewed wave of legal pushback against serial filers, and share some of the best writing we found on the web. Let’s get into it.

If you are new here, welcome. We compile this update every month to keep you informed on the changing landscape of digital accessibility in the time that it takes to drink a cup of coffee. Whether you are a developer, leader, product manager, or compliance officer, we want to give you the context you need to make better decisions without overwhelming you in the process.

As always, let us know 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 testing updates via email.

– The QualityLogic Editorial Team

What’s Inside

Upcoming Conferences and Events

  • National ADA Symposium: Virtual, May 4-6. A leading conference on the Americans with Disabilities Act (ADA), bringing together nationally recognized experts to share information, practical guidance, and best practices on accessibility. Lots of legal and hardware stuff here.
  • John Slatin AccessU 2026: Austin, Texas, May 11-14. A hands-on digital accessibility training conference built to turn principles into skills you can apply immediately across design, development, content, and leadership. One of our favorite in-person events due to the community it draws. While far from the largest turnout, you get access to some of the industry’s foremost thought leaders and practitioners in a great setting.
  • Microsoft Ability Summit: May 19-20, Virtual. A 2-day digital event exploring how technology, AI, and inclusive design can create a more accessible future.
  • Global Accessibility Awareness Day (GAAD): May 21, Global. The 15th annual GAAD focuses on digital access and inclusion for people with different disabilities.

The 2026 WebAIM Million

For the 8th consecutive year, WebAIM evaluated the accessibility of the top 1 million homepages on the internet and published their findings in a report they call the WebAIM Million. The sites come from the Tranco ranking, which is a popular (supposedly unbiased) dataset cataloging the internet’s top 1 million domains. Each was loaded into WAVE using the stand-alone WAVE API, after which the output was cataloged and later analyzed.

The headline number for 2026? A staggering 95.9% of homepages still have detectable WCAG failures, with an average of 56.1 errors per page.

The top issue was easily low-contrast text (found on 83.9% of sites) followed by missing alternative text for images (53.1%) and missing form input labels (51%).

After nearly a decade of heightened awareness, legislation, skyrocketing lawsuits, not to mention the integration of accessibility tools into almost every design platform… an effective 96% failure rate is quite the disappointing metric. It’s technically a decrease from 97.8% in 2019, but it’s also the first time in the past six years that the web has gotten worse. Typically, we hope to see at least a slight decrease in issues overall. So, what is going on? A few theories.

GenAI-augmented software development has been the headline over the past six months and is something we’ve covered extensively in previous editions of this newsletter. Based on benchmarks like the AI model Accessibility Checker (AIMAC) and Microsoft’s a11y-llm-eval, it is not a question that AI models struggle to spit out accessible code without explicitly being instructed to do so. Given that around 42% of the web’s code is written by AI (per most estimates), it is not a stretch to assume this could be a contributor to the problem. WebAIM points to the same thing in their own analysis, calling out “vibe coding” (semantically not the same but also not dissimilar from AI-augmented development) as a likely factor.

It could also be in part because pages just keep getting heavier. The average home page now contains 1,437 elements, up 22.5% in just the last year and nearly double the count from 2019. The more moving parts you have, the harder it becomes to keep a site accessible.

Pages that use ARIA averaged 59.1 errors compared to 42 on pages without it. ARIA usage on the web is up 27% in the past year and is now around six times what it was in 2019. It seems like a lot of teams are reaching for ARIA when they shouldn’t be or applying it incorrectly when they should. This lines up with the AI theory since models tend to throw role attributes, aria-hidden, and tabindex at problems that better HTML would solve naturally.

Finally, we could see the primary bottleneck shifting from awareness to execution. Tooling and testing are better than ever, but there continues to exist a fundamental disconnect between design intent and engineering output. All too often, accessibility requirements don’t make the jump from the design spec into development. Sometimes when they do, the biggest issues are only found during the final QA pass, at which point resolution is costly and might turn into a conversation around risk assessment.

For some good news, government and education domains are well ahead of the rest of the web. Sites on .gov averaged 18.5 errors per page (67% below the overall average) and .edu averaged 23.0 (59% below). Whatever shape the ADA Title II timeline ultimately takes (more on that below), the public sector has a real head start.

New from the QualityLogic Blog

Our huge post recapping everything we learned and/or heard about at the 41st CSUN conference is now live! We are admittedly a bit biased, but we think it’s a good read if you are interested in hearing more about what transpired at the event, and the latest and greatest across assistive technology and accessibility as a whole. Even if you were there, it’s incredibly easy to miss things amidst everything going on at once.

In a move that should not come as a surprise to our readers (if anyone), the Department of Justice is delaying the ADA Title II web and mobile app compliance deadlines by one year. Acting Attorney General Todd Blanche signed the Interim Final Rule on April 16, it was filed for public inspection on April 17, and it publishes in the Federal Register on April 20 (RIN 1190-AA82). Large public entities now have until April 26, 2027 to meet WCAG 2.1 Level AA. Entities with populations under 50,000 and special district governments have until April 26, 2028. Nothing else in the 2024 rule has changed.

DOJ invoked the “good cause” exception at 5 USC 553(b)(B) to skip pre-publication notice and comment. A 60-day post-publication comment window remains open.

What the preamble tells us

  • DOJ concedes it got the 2024 math wrong. The Department “overestimated the advancement and availability of technology” and says “generative AI does not yet reliably automate the remediation of inaccessible content at scale.” Interestingly, “Artificial intelligence” or “AI” does not appear anywhere in the 2024 final rule, making this claim seem confusing at best.
  • This is probably not the last move. DOJ says it will “consider issuing an NPRM” on substantive provisions during the extension, and calls WCAG 2.1’s incorporation “untenable” because its supplementary materials at w3.org can change without notice. This is essentially a warning that there is a good chance the technical standard itself may become a matter of discussion. The same WCAG structure has been the basis of DOJ settlement agreements for nearly a decade, so the sudden claim that it is “untenable” is difficult to take at face value.
  • DOJ is hardening against challenge. The IFR includes an explicit severability clause, stacks five separate rationales for the good cause exception, and floats an unusual argument that “international actors” are funding Title II litigation as “lawfare” against U.S. public entities.

What to do?

  • If you are a covered public entity: Think of this as a breather and an opportunity to build sustainable systems. WCAG 2.1 AA is still the standard, the ADA’s private right of action is still live, and plaintiffs can still sue today under the pre-2024 framework. The work that you’ve already done still counts, and the work you may have been putting off still has to happen.
  • If you are a vendor: Title II customer contracts still reference WCAG 2.1 AA. Procurement pressure is unlikely to slacken because most public-sector buyers do not want to inherit non-conformance, regardless of the deadline.
  • If you object to the delay, to the reconsidering WCAG 2.1, or just want to go on record supporting the 2024 rule: Public comment is open now and matters more than ever because a strong response may deter DOJ from following this IFR with the broader NPRM it is hinting at. Submit your thoughts by June 22, 2026, at regulations.gov, searching docket CRT150 or RIN 1190-AA82, and put “RIN 1190-AA82” in the subject line. It is important that all voices are heard, though personal accounts of accessibility barriers seem to carry more weight than general statements.

Court rulings

Most of the month’s notable decisions are collected in Converge Accessibility’s March 2026 legal update.

  • Payan v. Los Angeles Community College District (9th Cir.): The court reinstated $218,500 and $24,000 in damages for two students under Title II. Public sector accessibility failures now have a real dollar amount attached, not just the threat of an injunction.
  • Parikh v. accessiBe (SDNY): Three businesses filed a class action against accessiBe alleging breach of contract after they installed the automated widget on their websites, following claims that it would make their sites fully WCAG 2.1 AA compliant within 48 hours and protect them from lawsuits. Each of them got sued for accessibility violations. Upon reaching out to accessiBe, they were provided with a report saying their website was compliant, plus a referral to legal counsel at their expense. The court ultimately tossed accessiBe’s marketing claim that its widget would “stop any lawsuit in its tracks.” More to come on this.
  • Merrell v. Marriott International (N.D. Cal.): Dismissed for lack of standing. The court pointed to the plaintiff’s serial litigation history and excluded expert testimony from a witness who had tested sites using a mouse alongside a screen reader as methodologically unsound.
  • Jones v. Moscot.com (SDNY): Dismissed on mootness grounds after the defendant showed it had fixed the issues and the plaintiff offered nothing in response. The lesson here is that fixing the underlying bugs early, and being able to prove it, can shut a case down before it gets expensive.
  • Espinal v. Gabriella Growers (M.D. Fla., April 2): Found sufficient nexus between an online storefront and a physical store under the Eleventh Circuit’s nexus doctrine.
  • Merrell v. Tapestry (C.D. Cal.): Confirmed accessibility audits performed by AudioEye under outside counsel direction qualify for work product protection.

Everything else

Georgia’s HB 1470, which creates a cause of action against abusive accessibility lawsuits, has passed both the house and senate. A similar act in Utah (SB 68) is awaiting signature and also looks close to passing. On the enforcement side, a Florida flower shop paid $7,000 to settle a web accessibility lawsuit and the DOJ sued SeaWorld over its theme park accessibility policies. Internationally, the South Korean Supreme Court ordered Gmarket, Lotte, and other major online shopping malls to actively provide screen-reader-accessible services.

What We’ve Been Reading

Jobs and Opportunities

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.

That’s All for Now!

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.)