01 / Why this talk

A serious subject that deserves a less intimidating introduction.

Years ago, I gave a presentation called How do we make Accessibility accessible to everyone? The title was deliberately a little awkward. So, unfortunately, was the experience of trying to understand accessibility requirements for some teams.

People wanted to do the right thing. But the standards were long, the tools seemed technical and nobody was quite sure whether they had done enough. Accessibility was often treated as somebody else's speciality, or something to check just before launch.

I wanted to change that conversation. Not by pretending accessibility is simple, but by making it easier to start. My slides explored why it matters, the WCAG principles, the difficulty of evaluating conformance and a practical three-step approach using the free Lighthouse tool.

I've refreshed the details for current standards here. The older slides had statistics and legal claims that need up-to-date sources and local context, so I have not repeated them as though they are timeless facts.

The starting point is not a score. It's the person trying to use the service.

02 / People, not pixels

Accessibility means removing barriers that we did not need to put there.

Consider a form with labels that disappear when you start typing. A menu that works with a mouse but cannot be opened with a keyboard. A video without captions. An error message that simply says "Something went wrong".

Now consider that this website may be someone's only way to access an important service. What feels inconvenient to one person can make the experience impossible for another.

People use websites with keyboards, screen readers, zoom, speech recognition, alternative input devices and other supports. Some barriers affect people living with disabilities; others affect someone with a temporary injury, a small screen or an unexpectedly loud environment.

It's tempting to frame accessibility only as a regulatory obligation. There are important legal and policy responsibilities, but they depend on the context and jurisdiction. I prefer to begin with the more immediate responsibility: if we create a service for people, we should avoid excluding them by design.

03 / The four principles

WCAG is easier to understand when you start with four ideas.

WCAG stands for Web Content Accessibility Guidelines, developed by the World Wide Web Consortium (W3C). The standard contains detailed testable criteria, but four principles make a helpful first mental model. You can find the authoritative explanation in the W3C WCAG overview.

P / 01Perceivable

Can people get the information? Think captions, image descriptions and sufficient contrast.

O / 02Operable

Can people use it? Think keyboard access, visible focus and controls that work predictably.

U / 03Understandable

Can people make sense of it? Think clear instructions, consistent navigation and helpful errors.

R / 04Robust

Can browsers and assistive technology interpret it? Think semantic markup, names, roles and states.

A missing description on a meaningful image is a perceivable issue. A keyboard trap is an operable issue. A form that won't tell you how to correct an error is an understandable issue. And a homemade button that assistive technology cannot recognise is a robustness problem.

We still need the technical detail to test properly. But we can now discuss the problem without starting by reciting a criterion number.

04 / 2.0, 2.1 and 2.2

The standards evolve. The intention remains familiar.

My original talk compared WCAG 2.0 and 2.1. That was useful at the time, particularly as new criteria addressed experiences on smaller screens and for people with low vision or cognitive disabilities. Since then, WCAG 2.2 has been published, with further additions around focus and interaction.

2008WCAG 2.0Foundational principles and criteria
2018WCAG 2.1Additional user needs
2023WCAG 2.2Further focus and interaction criteria
TodayYour projectCheck the applicable version and requirements

W3C encourages teams to use the most recent WCAG 2 version. These versions build on one another, with an exception for the obsolete 4.1.1 Parsing criterion in WCAG 2.2. The levels A, AA and AAA refer to sets of success criteria, not a percentage score from an audit tool. AA is a common project target, but the exact version and target should reflect the service's obligations.

For details without the need to memorise an entire standard, use the WCAG 2.2 quick reference.

05 / Why testing is hard

A green score is encouraging. It is not a certificate.

Some accessibility checks are straightforward to automate. Others depend on context and judgement. A tool may confirm that an image has alt text, but not whether the words help someone understand why the image is there.

That is why two tools can report different issues and still both be useful. They may test different things or inspect different states. A browser audit can look tidy while a person navigating by keyboard still cannot complete the task.

W3C explains what evaluation tools can and cannot do. Automated checks help you find barriers and monitor improvements, but do not establish complete accessibility or full WCAG conformance. Real people and informed manual testing remain essential.

06 / Try it yourself

Five minutes without a mouse can teach you a lot.

Before you install another tool, choose a real website and try a few of the W3C's Easy Checks.

01Put down the mouse.

Press Tab and Shift+Tab. Can you reach the controls, see focus and use the whole experience without getting trapped?

02Read the structure.

Do headings explain the content? Are the links meaningful? Do important images have useful descriptions?

03Zoom in.

Try a narrow screen and 200% zoom. Is everything still readable and operable?

04Make a mistake.

Submit an incomplete form. Does the error tell you what happened and how to fix it?

These are introductory checks, not a complete assessment. They simply help everyone on the team see the experience from a different perspective.

07 / Run a free audit

Use the same tool, then talk about what it found.

One of the best parts of the original presentation was the live Lighthouse exercise. I wanted people to see that a free tool could give them tangible evidence, instead of accessibility feeling like an abstract subject for experts.

01
Choose a real page or journey.

A service form or content page is often more revealing than the homepage alone.

Select
02
Open Chrome DevTools, then Lighthouse.

Choose the suitable audit categories and run the assessment.

Run
03
Save the evidence.

Record the page, conditions and individual issues rather than just a score.

Record
04
Understand, fix and retest.

Read why each issue matters and verify the correction with manual checks too.

Improve

You can try WAVE as another free evaluator. Don't choose whichever score looks nicest. Investigate what each tool has found. 100 in Lighthouse does not mean 100% WCAG compliant.

08 / Make it normal

Measure early, learn together and keep improving.

In my original slides I suggested three steps: understand the intention behind a guideline, start with the high-value improvements, and use a consistent tool from development through QA and user acceptance testing. I would now add one more: keep the people affected involved.

Designers can consider colour, focus and layout. Writers can make instructions and errors clearer. Developers can build accessible controls. Testers can repeat real tasks and record evidence. Product owners can make sure the issues do not vanish into the backlog.

Keep a simple record: the page, barrier, evidence, who it affects, what should change and the retest result. For deeper evaluation use W3C's assessment resources and involve accessibility specialists and people with lived experience.

If you want a guided practical exercise, the Website Performance Training Lab also covers Lighthouse, broader website quality and turning findings into actions.

We do not need everyone to memorise WCAG. We need everyone to recognise a barrier and feel able to help remove it.

Share this thought
Share on LinkedIn ↗