A website accessibility checklist should cover page titles, headings, alt text, contrast, resizable text, keyboard use, visible focus, forms, moving content and captions. WCAG 2.2 level AA is the usual reference. You can test much of this yourself in an hour, but a passing checklist doesn't prove a site is accessible.
What should the checklist contain?
It should contain the checks a person can do without special skills, then go deeper. This list follows the W3C's Easy Checks and adds requirements from WCAG 2.2, the latest version of the standard.
| Check | How to test it | Pass when |
|---|---|---|
| Page title | Read the browser tab | It's descriptive and differs per page |
| Headings | View the page's heading outline | They're real headings, in a sensible order |
| Images | Inspect alt text | It serves the same purpose as the image |
| Contrast | Use a contrast checker | At least 4.5:1, or 3:1 for large text (level AA) |
| Text size | Zoom in the browser | Text stays readable and usable |
| Keyboard | Put the mouse away, use Tab and Enter | Everything works by keyboard |
| Focus | Tab through the page | You can always see where you are |
| Forms | Submit an empty form | Fields have labels, errors are clear |
| Motion | Watch moving content | It can be paused, nothing flashes too often |
| Video and audio | Play with sound off | Captions and transcripts are there |
| Structure | Turn off images and styles | The page still makes sense |
Which checks should you do first?
Start with the keyboard test. It takes a few minutes, needs no tools and quickly shows whether a site was built with care. Try it on the path that matters most: from the homepage to your contact form, then submit it. Menus that only open on hover, and buttons you can't reach, show up immediately.
Then check your form, because this is where accessibility and income meet. A form that can't be completed loses someone who wanted to talk to you. Next, look at contrast: light grey text on white is a common failure in otherwise polished sites.
What can't automated tools tell you?
They can't tell you if the site really works for people. The W3C says tools can only assist and can't determine accessibility, and that results can be misleading. A tool can see that alt text is missing, not whether it makes sense. It also warns that a page could pass the Easy Checks and still have significant barriers. So be careful with any product that promises instant compliance. Testing with people who use assistive technology tells you what no checklist can.
What does the European Accessibility Act mean for you?
It may apply if you sell to consumers online. The Commission lists e-commerce among the covered services, along with sectors such as banking and passenger transport. Directive (EU) 2019/882 has applied since 28 June 2025. Microenterprises that provide services are exempt from its accessibility requirements: those employing fewer than 10 people and staying under the turnover or balance sheet limit in the directive.
The directive works through national law, so details vary per country. A purely informational B2B site may not be covered, but don't assume: ask a legal adviser. This guide isn't legal advice. Whatever the law says, an accessible site simply works for more of the people you want to reach.
How do you keep a site accessible?
- Put it in the [brief](/journal/how-to-write-a-website-design-brief). Fixing it afterwards is more work than building it in.
- Add it to the [redesign checklist](/journal/website-redesign-checklist). Test before launch, not after.
- Check new content. Each new image, video and PDF can bring new problems.
- Publish a statement. The W3C's guidance says it should state your commitment, the standard you use and how people can report a problem. Be honest about known limits.
Much of this also makes your site clearer in general, for instance real headings and readable text. That's part of what makes a good website, and it helps machines read your pages too. See these 15 checks.
