Global Accessibility Awareness Day lands on the third Thursday of May every year. This year that's May 21, 2026 — fifteen years after the first GAAD, and one of the most consequential years for digital accessibility in living memory.
It's been twelve months of new rules (the DOJ's Title II web rule hit its enforcement deadline for large public entities in April), new lawsuits (the highest count of Title III digital accessibility cases ever filed in a single year), and new tools — including a generation of agentic AI that can do real accessibility work, not just generate plausible-looking copy.
To mark the day, we wanted to do something a little different from a typical GAAD post. Instead of walking through what GAAD is — we've covered that elsewhere — we wanted to take stock. What actually shipped in our product this past year that matters for accessibility? Not slides, not roadmaps, not "we believe in inclusion." What did we build that an end user, a compliance officer, or a developer can use today?
Here are five.
1. Human-in-the-loop agentic AI remediation ✦
For a long time, "AI-powered accessibility" tools have come in two flavors. The first kind silently injects changes into your site — alt text, ARIA labels, "fixes" — and you have no way to audit what it did or undo what's wrong. The second kind gives you a giant report and walks away.
Neither is acceptable for a serious organization. The first is a compliance and brand risk. The second isn't a product, it's a homework assignment.
We took a different approach this year. AllAccessible agents scan your site, draft a queue of proposed accessibility fixes — accessible alt text, ARIA labels, button text, form labels — page by page, locale-aware and context-aware. Your team opens the remediation review queue in the dashboard, sees each suggested change in context, and approves, edits, or skips it. Approved fixes get applied to your live site through the widget. Nothing ships without your sign-off.
This is what we mean by human-in-the-loop agentic AI remediation. Agents propose changes. Your team decides.
Why does this matter for GAAD specifically? Because it answers the most common objection we hear from accessibility-conscious teams: "I don't trust AI to make decisions about how disabled users experience my site." You shouldn't. So we built a product where AI doesn't get to make those decisions alone. It proposes; your team disposes.
The feature entered beta this month for eligible accounts. If you're on a qualifying plan, look for the banner in your dashboard.
2. Full-site coverage instead of one-page audits
A confession: for years, the dirty secret of widget-style accessibility tools — including, historically, ours — was that the headline "accessibility score" you saw on your dashboard was usually computed from a single page. Often the homepage. Sometimes a sitemap-derived sample.
The rest of your site? Maybe scanned, maybe not. Hard to tell.
This year we rebuilt the audit foundation so that every URL on your site is tracked as a first-class object. AllAccessible reads your sitemap.xml, queues every page, and processes them in parallel. We even fill in the gaps automatically — if our analytics know a page exists that the crawler hasn't audited yet, a gap-filling crawl gets scheduled.
And every page gets audited on both desktop and mobile viewports, because the issues are often different. Mobile-only modals trap keyboard users. Desktop hero carousels confuse screen readers in ways the mobile collapsed version doesn't. Hamburger menus introduce keyboard traps that don't exist at desktop breakpoints. Auditing one viewport is like proofreading half a document.
The result: the "accessibility score" you see now actually means something. It's an aggregate of every page we know about, scanned through both viewports. If a page wasn't audited, we tell you why.
See the sitemap-driven audits release and the agentic AI launch release for detail.
3. WCAG 2.2 as the default baseline
A subtle change with a big downstream effect: every new site we scan now defaults to WCAG 2.2 Level AA rather than 2.1. WCAG 2.2 is the operative standard accessibility reviewers, procurement teams, and regulators reference in 2026.
Why this matters in practice: 2.2 added nine new success criteria over 2.1, several of which catch real-world failures that 2.1 missed entirely. Things like focus appearance, target size minimums, and consistent help patterns — issues that show up immediately for mobility-impaired users but never registered against the older rule set.
Existing sites can opt in from their dashboard at any time. New sites get it automatically.
This isn't a flashy feature; it's a quiet promise. The score on your dashboard reflects the standard you'll actually be judged against — not last year's version of the rules.
4. Regression detection + industry benchmarks
Two questions customers asked us constantly this year:
- "My site looked fine last week. What changed?"
- "Is my accessibility score good?"
We didn't have great answers. So we built two features.
Regression detection watches your audit history. When scores drop more than expected for normal site changes — accessibility drift introduced by a theme update, a new plugin, a content edit gone wrong — you get an alert. We can't stop the regression from happening, but we can make sure you don't find out from a lawsuit demand letter six months later.
Industry benchmarks run nightly. Your site gets compared to anonymized aggregated scores from peers in your sector — e-commerce, healthcare, government, restaurants, real estate, you name it. The benchmark answers the "is my score good?" question with: good relative to whom?
Both features are live in your dashboard now. No setup needed. See the release announcement for detail.
5. Locale-aware AllAccessible AI labels ✦
This one is more subtle, but it matters.
For years, AI-generated accessibility labels have been the joke of the screen-reader community. "Submit" buttons everywhere. "Click here" everywhere. "Image of a man" for a photo of a doctor with a stethoscope. Generic, context-free, and often actively misleading.
We rebuilt the way AllAccessible AI generates labels so that the agents see the surrounding page context, not just the bare element. That means:
- A button that previously got labeled "Submit" now gets labeled something like "Submit registration for the May 21 webinar"
- A link that would have been "Read more" becomes "Read more about our Section 508 compliance approach"
- A vague "Click here" becomes a label that actually describes the destination
And it's locale-aware by default. If your site's primary language is Spanish, the labels are in Spanish. If you serve multiple locales with per-locale page variants, the AI generates labels in the right language for each.
For multilingual sites — which, in 2026, is most serious commercial sites — this is the difference between AI labels being useful and AI labels being a liability.
Release notes here. The same release shipped element highlighter deep-links — click any suggestion in the remediation queue, jump straight to the element on the live page. Real review, not guessing.
The bigger picture: 2026 is a year of accountability
GAAD 2026 lands at a different moment than GAAD 2025. A year ago, the EAA was still ahead of us. The DOJ Title II rule was a calendar entry. AI-generated alt text was a research demo.
Now:
- The European Accessibility Act has been enforceable for eleven months. The first cases are emerging.
- The DOJ Title II web rule hit its deadline for large public entities in April 2026. Small entities have until April 2027.
- WCAG 2.2 is the operative baseline. WCAG 3.0 working drafts continue to advance.
- Title III digital accessibility lawsuits in the US are at an all-time high.
What's changed isn't the rules. The rules have been clear for years. What's changed is enforcement, and enforcement changes what a CFO is willing to fund. Accessibility is no longer something you can defer to "phase 2." It's a current-quarter line item, and it's increasingly tied to your ability to bid on government contracts, enter European markets, and avoid demand letters.
If you're in that bucket — and most organizations now are — we'd love to help. Start a 7-day trial, or browse the full changelog for everything we shipped this year. Or just take ten minutes today to do one accessible thing on your site: run an audit, add an alt-text label, fix one button label that says "Submit."
That's how this work gets done. One label at a time. One review at a time. One sign-off at a time.
Happy GAAD.
Further reading
- What is GAAD Day? — the history of Global Accessibility Awareness Day
- WCAG 2.2 Complete Guide — every success criterion explained
- 2026 Accessibility Compliance Timeline — what's due when
- AllAccessible Changelog — every feature we shipped, dated and detailed