Khizar Seo
One evening in the early 1970s, a man named Michael Pachovas and a few friends wheeled up to a curb in Berkeley, California, poured wet cement into a rough ramp shape, and rolled off into the night. The police threatened to arrest them. They didn’t. In 1972 the city installed its first official curb cut, on Telegraph Avenue, and a local advocate later called it the slab of concrete heard round the world.
Here’s the part I find funnier than it should be. Curb cuts weren’t even new. The first ones appeared in Kalamazoo, Michigan, back in 1945, put in to help disabled veterans get to work. Nobody noticed for twenty-seven years.
And once they spread, look who actually uses them: parents with strollers, delivery workers with hand trucks, anyone hauling a suitcase, cyclists, skateboarders, people with bad knees. Angela Glover Blackwell named this pattern the curb-cut effect in a 2017 essay for the Stanford Social Innovation Review. Design something for a group that’s been locked out, and the benefit leaks sideways into everyone’s life.
The web version of this keeps getting sold as a legal obligation. Which is a shame, because the legal argument is the least interesting one available.
How Many People You’re Losing Right Now
The World Health Organization puts it at roughly 1.3 billion people — about 16% of everyone alive — living with a significant disability. That’s not a niche. That’s one in six of your potential customers, and the figure only rises as populations age, because most disability isn’t something you’re born with. It’s something that happens to you.
Now the awkward number. WebAIM scans the home pages of the top one million websites every year. In the February 2026 edition, 95.9% had detectable WCAG failures — up from 94.8% the year before, reversing six straight years of slow improvement. Average errors per page climbed 10.1%, to 56.1.
That’s automated detection only, which means it’s a floor. Automated tools can’t tell whether your alt text is useful or whether your tab order makes sense. Real conformance is below 4.1%.
But the more interesting finding is why it got worse. WebAIM points at page complexity: the average home page now runs about 1,437 elements, up more than 22% in a single year, with ARIA code up 27% in the same span. Their read is that this reflects heavier reliance on third-party frameworks and AI-assisted coding. Generated markup is fast, and it’s frequently semantic nonsense wrapped in a div.
So the web is getting less accessible at the exact moment it’s getting easier to build. Think about that for a second.
Accessibility as a Side Upgrade for Everyone
Six failure categories account for 96% of everything WebAIM detects, and they’ve topped the list for seven consecutive years. Not exotic edge cases. These:
Low contrast — on 83.9% of home pages, and the fastest-growing failure of the six. It’s also the one that hits you personally, every time you try to read your phone at a bus stop in bright sun.
Missing alt text — 53.1%. The same text a screen reader announces is the text a crawler reads and the text that shows when an image fails to load.
Missing form labels — 51%. A label makes the input’s tap target bigger, which helps every thumb on every phone.
Empty links and buttons — 46.3% and 30.6%. A button whose accessible name is blank is a button nobody can describe, including your own support team on a phone call.
Missing document language — 13.5%. One attribute. It’s how a screen reader knows not to read English text with Spanish pronunciation, and it takes about four seconds to add.
The pattern repeats up and down the standard. Captions get built for deaf users and end up watched by everyone scrolling in a quiet office. Keyboard navigation gets built for people who can’t use a mouse and ends up being how power users move through your admin panel three times faster. Clear focus states get built for accessibility and quietly fix the “wait, where am I?” problem for everyone.
WCAG makes a genuinely decent quality checklist if you stop reading it as a legal document. Version 2.2 is the current published one; W3C put out a working draft and explainer for WCAG 3 in March 2026, so the next generation is coming, slowly, the way standards do.
The Legal Side, and the SEO Side
The US litigation picture in 2025: Seyfarth Shaw counted 3,117 federal website accessibility lawsuits, up 27% from 2,452 the year before, making up 36% of all federal ADA Title III filings. UsableNet, which tracks state courts too, put the combined total above 5,000. Of those, 1,427 hit companies that had already been sued once — in federal court, repeat defendants were around 46% of cases.
Read that last figure twice. Almost half of this litigation lands on people who already paid to settle, patched the surface, and moved on.
Which brings me to overlay widgets, the one-line script that promises instant compliance. In April 2025 the FTC finalized a $1 million order against accessiBe over claims that its automated product could make any website WCAG-conformant. Roughly 22% of accessibility suits in the first half of 2025 targeted sites that had an overlay installed. An overlay is a wheelchair ramp painted onto a staircase. It photographs well.
Government deadlines have moved, and it’s worth being precise. DOJ’s 2024 Title II rule adopted WCAG 2.1 Level AA for state and local government sites. On April 20, 2026 — four days before the original deadline — DOJ pushed compliance to April 26, 2027 for larger jurisdictions and 2028 for smaller ones. The extension changed the date and nothing else; the underlying nondiscrimination obligations never paused, and private plaintiffs can still sue during the delay. Meanwhile the HHS Section 504 rule kept its May 2026 deadline, and in Europe the Accessibility Act has been enforcement-active since June 28, 2025.
On the search side, I want to be careful, because this gets oversold. There is no accessibility ranking factor. What’s true is narrower and still useful: the semantic structure that assistive technology depends on is the same structure a crawler parses. Real heading hierarchy, descriptive link text instead of “click here,” alt attributes, landmark elements, valid language declaration. Do accessibility work properly and you incidentally clean up a pile of technical SEO debt. Nobody planned it that way. It just falls out.
There’s a reputational dimension too, and it’s the part clients underestimate. Work that gets held up as award winning web design gets examined by people who tab through it — juries, peers, other practitioners poking at the interaction model to see how it was built. A site that traps keyboard focus in a modal doesn’t survive that kind of attention. Teams competing at that level build accessibility in from the start, not because a regulation told them to, but because a broken focus state in front of a room of designers is embarrassing in a way a lawsuit somehow isn’t.
Where to Start Without a Budget
Run Lighthouse. It’s already in Chrome DevTools, it takes ninety seconds, and it’ll catch contrast and alt text failures immediately. Then try WAVE or axe DevTools for a more thorough pass.
Fix the six. Contrast, alt text, form labels, empty links, empty buttons, language attribute. That’s 96% of detected errors across a million sites, and none of it requires specialist knowledge or a design overhaul.
Unplug your mouse. Try to complete your own primary conversion flow using only Tab, Enter, and arrow keys. Most people don’t get past the cookie banner. This test costs nothing and will tell you more than any report.
Turn on VoiceOver or NVDA and listen to your home page for five minutes. It’s uncomfortable. That discomfort is the point — you’re hearing what your markup actually says, as opposed to what it looks like it says.
Then write it into your definition of done, because everything above decays. Accessibility isn’t a project you complete; it’s a property of a page that any deploy can break.
The thing that gets me is that the six most common failures on the web have been the same six for seven years running. Not hard problems. Not expensive ones. Just nobody’s job.
Somebody in your organization is going to own this eventually, either by choosing to or by being handed a legal filing. One of those routes is considerably cheaper, and you already know which.
