WCAG principles, levels and why they matter

0:00 WCAG principles, levels and why they matter

Here's a number worth remembering. The World Health Organization estimates that around one point three billion people, about one in six people worldwide, experience significant disability. Now add everyone with a temporary or situational limitation. A broken arm. Bright sunlight on a phone. A noisy train with no headphones. Accessibility isn't a niche. It's a large share of your customers on any given day. In this lecture, you'll learn what the Web Content Accessibility Guidelines are, the four POUR principles, the conformance levels, what's changed in twenty twenty-five and twenty twenty-six, and how to map barriers on your most important pages.

0:44 Why it matters

Why does accessibility matter for marketers? First, reach. Barriers exclude real customers. Second, usability. Accessible design is usually clearer and easier for everyone. Third, law. Accessibility is increasingly a legal requirement in many markets. And fourth, reputation. Think about curb cuts, those ramps in the sidewalk at crossings. They were designed for wheelchair users. But parents with strollers, travelers with suitcases and delivery workers with trolleys use them every day. Accessible design works the same way. Captions help people watching on mute. Good contrast helps people in sunlight. Clear errors help everyone.

1:24 The standard

The Web Content Accessibility Guidelines, WCAG, are published by the W3C and are the internationally recognized standard. WCAG two point two, published in twenty twenty-three, is the current version. It builds on two point zero and two point one, so meeting two point two generally satisfies the earlier versions too. And here's a twenty twenty-five update. In October twenty twenty-five, WCAG two point two was approved as an ISO standard, ISO slash IEC forty five hundred, colon twenty twenty-five, with identical content. That makes it easier for governments and big buyers to require it. WCAG three is still a draft, not a standard, so keep targeting two point two.

2:11 The four POUR principles

WCAG is organized around four principles, which spell POUR. Perceivable: information can be perceived through at least one sense. Think alt text, captions, sufficient contrast, and text that can be resized. Operable: the interface can be used in different ways, including by keyboard, with enough time, without seizure-inducing flashes, and with targets big enough to hit. Understandable: content and behavior make sense, with clear language, predictable interactions and helpful error messages. Robust: it works with current and future technologies, including assistive technology like screen readers, through valid, semantic code with proper names and roles for controls.

2:53 Conformance levels

Now conformance levels. Level A is the minimum. Failing it creates severe barriers. Level AA is the level most laws, policies and organizations target. It includes contrast of four point five to one for normal text, captions for prerecorded video, visible focus, and more. Level AAA is enhanced, and usually isn't required for entire sites, because some criteria can't be met for all content. So here's the practical rule for your team. Target WCAG two point two, Level AA. Put that exact sentence into every brief you write.

3:31 The legal picture (general info)

What's the legal picture? It varies by market, so treat this as general information. In the European Union, the European Accessibility Act has applied since June twenty-eighth, twenty twenty-five, to many consumer products and services, including e-commerce, usually assessed against a European standard that incorporates WCAG. In the UK, the Equality Act requires reasonable adjustments, and public sector bodies have specific website rules. In the US, private businesses face lawsuits under the ADA, and a federal rule requires state and local governments to meet WCAG two point one AA, with deadlines extended in April twenty twenty-six to twenty twenty-seven and twenty twenty-eight. Gulf markets have disability rights laws and government digital policies too.

4:20 About overlays

A warning about accessibility overlays. Some vendors sell widgets that claim to make your site compliant automatically with one line of code. Accessibility experts and disabled users widely criticize them. They often fail to fix underlying problems, and they can interfere with the assistive technology people already use. An overlay is like putting a ramp sticker on a staircase. It looks like you've done something, but nobody can get up the stairs. Fix the real design, content and code instead.

4:55 Worked example 1: creator course site

Worked example one, simple. A creator's course website gets six quick wins in one afternoon. Gray body text is darkened to reach four point five to one. Instructor and course images get meaningful alt text, and decorative images are marked as decorative. The sales video gets reviewed captions. Click here links become descriptive, like see the full curriculum. The cookie banner and sticky header are adjusted so they don't hide keyboard focus. And tiny social icons in the footer are enlarged to meet the target size guidance. None of these changes the brand. All of them widen the audience.

5:38 Worked example 2: EU-facing store (illustrative)

Worked example two, a business scenario with illustrative details. A UK online homeware store sells to customers across the EU. After the European Accessibility Act takes effect, the team maps barriers on its three most important pages: a campaign landing page, product pages and checkout. They find pale text on promotional banners, a checkout step where a custom dropdown has no accessible name, error messages that only turn fields red, and a cookie banner that traps keyboard users. They fix the highest-severity items first, add WCAG two point two AA to every agency brief, and publish an accessibility statement with a contact route.

6:23 Watch me do it: POUR barrier map

Watch me do it. I open a POUR barrier map for the pricing page. Perceivable: I run a contrast checker on the gray plan descriptions. Three point one to one. That fails. Operable: I put the mouse away and press tab. I reach the plan toggle, but I can't operate it with the keyboard. Understandable: I trigger an error in the sign-up form. It says invalid input. Robust: I open the browser's accessibility pane and inspect the custom dropdown. It has no name. Four barriers in ten minutes. I note who each affects, a fix, and the effort, then sort by severity.

7:07 Common mistakes and measures

Common mistakes. Treating accessibility as a final checklist item instead of a design requirement. Relying on overlays. Assuming few of our users are disabled, when many disabilities are invisible and people don't announce them. Ignoring situational limitations like bright sunlight or noise. And not writing accessibility into briefs, so agencies and freelancers never deliver it. How do you measure progress? Open accessibility issues by severity on key templates. The share of new pages that pass accessibility QA before launch. And feedback through your accessibility contact.

7:44 Recap and try this now

Let's recap. Accessibility affects a large share of your audience. WCAG two point two is the current standard, and it's now also an ISO standard. It's organized around POUR: perceivable, operable, understandable and robust. Target level AA. Legal requirements are growing, from the EU's accessibility act to ADA lawsuits and public sector rules. And fix real issues instead of relying on overlays. Try this now. Pick your three most important pages for conversions. For each, find one likely barrier under each POUR principle, and choose three to fix this month.