Web Accessibility: What the Law Requires and What Good Design Solves

Accessibility used to be the section of the brief nobody read past the heading. That's changed. Not because businesses had a change of heart, but because three different legal systems started enforcing web accessibility in the same eighteen-month window.

Here's what "accessible" actually means, what the law now says about it in Australia, the US and the EU, and how we build to the standard without turning every project into a compliance exercise.

What "accessible" actually means

Web accessibility has a real definition, not a vibe. The international standard is WCAG — the Web Content Accessibility Guidelines, maintained by the W3C. The current version is 2.2, published in 2023 and refined through 2025. It organises around four principles, usually shortened to POUR:

• Perceivable — people can actually detect the content, whatever their senses look like. Alt text for images, captions for video, enough colour contrast to read.

• Operable — people can navigate and interact without a mouse, without perfect vision, without fine motor control.

• Understandable — content and interface behaviour make sense. No form that fails silently. No navigation that surprises you.

• Robust — the site works with the assistive technology people already use, not just the browser your team tested in.

WCAG scores sites against three conformance levels: A, AA and AAA. AA is the level every law below references as the practical baseline. AAA covers extras — full video transcripts, stricter contrast — worth doing where they're cheap, not worth chasing everywhere.

Why it's not only a legal question

The law is the reason web accessibility reaches the top of the priority list. It isn't the only reason it belongs there.

Captions help someone in a noisy share house, not only someone who is deaf. High contrast helps someone reading a phone in direct sun, not only someone with low vision. Keyboard navigation helps someone with a broken trackpad, not only someone who can't use a mouse at all. Clear form labels help everyone who has ever filled in a form badly designed by someone in a hurry.

Accessible design is, mostly, just design that was finished properly.

What the law actually says

Australia

The Disability Discrimination Act is the legal foundation here, and it already covers websites — not through a recent amendment, but through a 2000 case: Maguire v Sydney Organising Committee for the Olympic Games, where the Human Rights Commission found the DDA applied to the Sydney Olympics website. That precedent has stood for over two decades.

Current guidance recommends WCAG 2.2 at a minimum Level AA, with Level AAA items like transcripts and clear headings encouraged where practical. The Australian Standard AS EN 301 549:2024 references WCAG throughout for digital products generally, not just websites.

United States

Two different parts of the ADA apply here. Title II covers state and local government, and the DOJ pushed those deadlines back in 2026: entities serving 50,000 or more people must comply by April 26, 2027; smaller entities and special districts get until April 26, 2028. These dates reflect the extended deadlines set by a DOJ Interim Final Rule published April 20, 2026, one year later than the original 2024 rule — worth keeping in mind if the rule is revised again.

Title III is the one that touches private business, through litigation rather than a published deadline. Courts have repeatedly treated commercial websites as "places of public accommodation," and settlements for non-compliant sites typically land somewhere between five and twenty thousand US dollars — smaller than a lawsuit, but not a rounding error for most small businesses. WCAG 2.1 AA is the standard referenced in most of that litigation, though building to 2.2 AA is the more future-proof move.

European Union

The European Accessibility Act started being enforced on June 28, 2025, and it doesn't care where your business is registered — it applies to anyone selling covered products or services to EU consumers. E-commerce is explicitly in scope.

The underlying technical standard, EN 301 549, currently incorporates WCAG 2.1 AA in full, with an update expected later in 2026 to fold in 2.2. Penalties vary enormously by country — reported fines range from roughly €60,000 in Ireland to close to €900,000 in Sweden — and non-compliant products can simply be pulled from the market. The first EAA lawsuits were already filed in France by November 2025.

Where most websites actually fail

Not from one dramatic flaw. From a handful of small, repeated ones:

• Text on backgrounds that fail contrast ratios the moment you check them properly

• Images with no alt text, or alt text that just says "image"

• Forms with placeholder text standing in for a real label

• Buttons and links that say "click here" or "read more" with no context for what they do

• Video with no captions

• Interactive elements that can't be reached or operated with a keyboard alone

None of these require a redesign. They require someone to actually check.

How we build for it in Wix Studio

Wix Studio has a built-in Accessibility Wizard, and it does most of the mechanical checking for you. One scan flags heading structure problems, missing alt text, and contrast failures — site-wide and per page. It includes an AI alt text generator for anything you've missed, and it separates what it can fix automatically from what still needs a human: descriptive link text, whether content still works at 200% zoom, whether autoplaying media has a pause control.

Automated tools catch most of the mechanical failures. They don't catch bad judgment, which is where the manual review list above still matters.

Our process at Olya Black

We check accessibility as we build, page by page. This way we catch issues early, before they carry through to the rest of the site — and we save time by not fixing the same problem repeatedly across similar content.

We run Wix Studio's built-in Accessibility checker on each page as we go. It surfaces what can be improved or adjusted, and we act on it in the moment rather than at the end of the project.

Where an accessibility fix would affect a design decision or change something visible to the client, we communicate it directly. No surprises at handover.

The bottom line

Web accessibility stopped being optional somewhere in the last two years, in three different legal systems at once. The good news is that meeting the standard and building a well-made site are, most of the time, the same job. Do the second one properly and you've mostly done the first. If you're thinking about how this fits your broader online presence, it's worth reading how SEO and branding work together — an accessible, well-structured site earns on both fronts.