Accessibility is a habit, not a checkbox (and now the law)

26 June 2026

Ask a room of website owners what accessibility means and you'll usually get one of two answers. Something about screen readers, or something legal wants us to sign off on. Both are true, and both miss the point.

Accessibility is about whether your website works for the people who show up. All of them.

Who accessibility is actually for

The World Health Organization estimates that 1.3 billion people live with a significant disability. That alone should settle the question. But the group who benefit from an accessible website is far larger, because ability isn't a fixed property of a person. It changes with situation and time:

• Permanent: someone who is blind, deaf, or has limited motor control.
• Temporary: a broken wrist, an eye infection, recovering from surgery.
• Situational: bright sunlight on a phone screen, a noisy train, holding a baby in one arm, a slow connection that never loads your icon font.

Design for the first group and the other two get a better website for free. Good contrast helps the person with low vision and also the person in the sun. Captions serve the deaf visitor as well as the commuter without headphones. Keyboard navigation helps someone who can't use a mouse, and the power user who simply won't.

The legal picture, briefly

If you've been treating accessibility as optional, the law has moved on:

• Public sector: the EU Web Accessibility Directive has required public-sector websites and apps to be accessible since 2019, following the WCAG guidelines via the European standard EN 301 549.
• Private sector: the European Accessibility Act applies since 28 June 2025. It covers, among other things, e-commerce, banking services, e-books and transport booking, which means a large share of ordinary commercial websites now carry a legal duty to be accessible, on top of the moral one.

Outside the EU the wording differs but the destination doesn't: the ADA and Section 508 in the US, the Public Sector Bodies Accessibility Regulations in the UK, the Accessible Canada Act and Ontario's AODA, the Disability Discrimination Act in Australia. Accessibility law goes global walks through each of them.

WCAG, the Web Content Accessibility Guidelines, is the shared measuring stick behind all of it. It's a long document, but its spirit fits in one sentence. Content should be perceivable, operable, understandable and robust for everyone.

What automated testing can and can't do

Automated testing does not catch every accessibility problem, whatever other tools may imply. No tool can tell you whether your alt text is meaningful, only whether it exists. No tool can judge whether your page makes sense read aloud.

What automated testing does brilliantly is the other part:

• It catches mechanical failures such as missing labels, broken heading order, insufficient contrast, missing alt attributes and keyboard traps, which make up a large share of real-world barriers.
• It checks every page, every time, which no human review can afford to do.
• It catches regressions, like the accessible component a redesign quietly broke, or the template change that removed a label from four hundred forms at once.

The reasonable setup uses both. Automated, continuous auditing as your safety net, and periodic human review (ideally involving people who actually use assistive technology) for the judgment calls. That's people before tools, applied to accessibility.

Continuous matters more here than anywhere, because accessibility has a cruel property. The people it fails are the least likely to file a bug report. A visitor who can't get past your cookie banner with a keyboard doesn't email you. They leave. Which means accessibility regressions can sit unnoticed for months while every analytics dashboard looks normal. A one-off accessibility audit is a photograph. Your website is a video. Continuous testing of every page, after every release, is the only way to know the photograph is still true.

Where to start with WCAG

1. Get a baseline. Find out where you actually stand across the whole site, not just the homepage. (Our baseline report and Webperf Audit were built for this.)
2. Fix templates before pages. One heading-order fix in a template can repair hundreds of pages at once.
3. Watch for regressions. Automated tests after each release mean a broken label is a ticket this week, not a legal exposure next year.
4. Bring in real people. When the mechanical issues are handled, usability testing with assistive-technology users will teach you things no score can.

Accessibility done this way stops being a compliance scramble. It becomes part of how you ship, which is what it should have been all along.

Automated WCAG checks run on every page in every plan. Compare them, or ask us at hello@webperf.cloud where your site stands today.