Most accessibility problems on small business sites are not exotic. They are pale grey text on white, a menu you cannot reach with the keyboard, a form whose fields have no labels, icons with no names and a cookie banner that traps focus. A website accessibility checklist turns all of that into a list you can work through, fix and retest, without needing to read the whole standard first.
This website accessibility checklist targets WCAG 2.2 Level AA, which is the level most laws and contracts point to. It is written for owners and the people who build their sites, with notes on WordPress and Elementor where they are the usual cause.
WCAG 2.2 in two minutes
The Web Content Accessibility Guidelines (WCAG) are published by the W3C. Version 2.2 became a W3C Recommendation in October 2023 and is backwards compatible with 2.1: a site that meets 2.2 AA also meets 2.1 AA. The guidelines are grouped under four principles — content must be perceivable, operable, understandable and robust — and each testable rule (a “success criterion”) has a level:
- Level A — the most basic barriers. Necessary but not sufficient.
- Level AA — the realistic target for business sites, and the level most regulation refers to.
- Level AAA — the strictest level, useful for specific pages or audiences but not expected for an entire site.
Web accessibility is not only about blind users with screen readers. It covers people with low vision, colour blindness, motor impairments who use a keyboard or switch device, deaf and hard-of-hearing visitors, and people with cognitive or learning disabilities.
Who has to care, legally
| Region | What applies |
|---|---|
| EU (and businesses selling into it) | The European Accessibility Act applies from 28 June 2025 to many consumer-facing digital services, including e-commerce. Microenterprises providing services are exempt. The related European standard is built on WCAG. |
| United States | The ADA has been applied to private business websites in a large number of lawsuits. There is no single technical rule for private businesses, but WCAG AA is the usual benchmark. |
| United Kingdom | The Equality Act 2010 requires service providers to make reasonable adjustments, which covers websites. Public sector bodies have their own accessibility regulations. |
| Australia | The Disability Discrimination Act 1992 applies to services, and WCAG is the standard commonly referred to. |
This is guidance from someone who builds and audits sites, not legal advice. If you sell into the EU or work in a regulated sector, have your obligations checked by a lawyer. Whatever the legal position, an accessible website is simply easier for everyone to use.
The website accessibility checklist
Work through each group in turn. Every item maps to one or more WCAG success criteria at Level A or AA, so this doubles as a plain-English WCAG checklist.
Structure and content
- Every page has a unique, descriptive
<title>. - The page declares its language with the
langattribute on the<html>element (for examplelang="en-GB"). - One H1 per page, then H2 and H3 in a logical order. Headings describe the content below them; they are not chosen for their font size.
- Link text makes sense on its own: “View our boiler repair prices”, not “click here” or “read more” repeated six times.
- Menus and repeated blocks are consistent from page to page, and there is a “skip to content” link at the top.
Images and media
- Informative images have alt text that says what the image communicates in context. A team photo on the About page might be “The four-person team outside the Leeds workshop”.
- Decorative images have empty alt text (
alt="") so screen readers skip them. - Icon-only buttons and links (search, menu, social icons, close) have an accessible name, usually via visible text or an
aria-label. - Videos have accurate captions. Auto-generated captions need checking before you rely on them.
- Nothing plays audio automatically, and carousels or animations that move for more than five seconds can be paused.
Colour, text and layout
- Body text has a contrast ratio of at least 4.5:1 against its background; large text (roughly 24px regular or 18.66px bold and above) at least 3:1.
- Buttons, form field borders, focus indicators and icons that carry meaning have at least 3:1 contrast against what is next to them.
- Colour is never the only signal. Error fields get a message, not just a red border; links in body text are underlined or otherwise distinguishable.
- Text can be zoomed to 200% without content being cut off or overlapping.
- At a width of 320 CSS pixels the page reflows into one column without horizontal scrolling (data tables and maps excepted).
Keyboard and focus
- Every link, button, menu, form field, tab and modal can be reached and used with the keyboard alone.
- Focus moves in a logical order and never gets stuck (no keyboard traps, including in pop-ups and chat widgets).
- The focused element always has a visible focus indicator.
- The focused element is not hidden behind a sticky header, a chat bubble or a cookie banner.
- Dropdown menus open on keyboard focus or Enter, not only on mouse hover.
Forms
- Every field has a visible label tied to it in the code. Placeholder text is not a label.
- Required fields are marked in text, not only by colour or an unexplained asterisk.
- Errors are described in words next to the field, with a hint on how to fix them, and the message is announced to screen readers.
- Name, email, phone and address fields use the correct
autocompletevalues so browsers can fill them. - Users are not asked to type the same information twice in one process unless it is essential.
- Logins do not rely on a memory or puzzle test alone. Allow paste and password managers, and offer an alternative to image-based CAPTCHAs.
Overlays are not a fix: accessibility toolbars and “one line of code” overlay products cannot repair missing labels, broken heading structure or keyboard traps in your theme, and they can clash with the screen readers and zoom tools people already use. Budget the time for real fixes instead.
What is new in WCAG 2.2
If your site was audited against 2.1, these are the additions to check. The table lists the new criteria at Levels A and AA; 2.2 also adds three at AAA and removes the old 4.1.1 Parsing criterion.
| Criterion | Level | What it means in practice |
|---|---|---|
| 2.4.11 Focus Not Obscured (Minimum) | AA | Sticky headers, cookie bars and chat widgets must not completely hide the focused element |
| 2.5.7 Dragging Movements | AA | Anything done by dragging (sliders, sortable lists, maps) has a single-pointer alternative such as buttons |
| 2.5.8 Target Size (Minimum) | AA | Click and tap targets are at least 24 by 24 CSS pixels, or spaced so they do not crowd each other, with some exceptions |
| 3.2.6 Consistent Help | A | Help options such as phone, chat or contact links appear in the same place across pages |
| 3.3.7 Redundant Entry | A | Information already entered in a process is filled in or selectable, not retyped |
| 3.3.8 Accessible Authentication (Minimum) | AA | No cognitive test to log in unless there is an alternative; allow paste and password managers |
Testing your site in about an hour
-
Pick the pages that matter.
Homepage, one service or product page, the contact page, any booking or checkout flow, and a blog post.
-
Run an automated scan.
Use WAVE, axe DevTools or the Lighthouse accessibility audit in Chrome DevTools. Fix contrast errors, missing alt text, empty links and unlabelled fields first. A clean automated score does not mean the site is accessible; these tools only catch part of the issues.
-
Unplug the mouse.
Use Tab, Shift+Tab, Enter, Space and the arrow keys to get through the menu, open dropdowns, submit the contact form and dismiss the cookie banner. Note anywhere focus disappears, jumps around or gets stuck.
-
Zoom and narrow.
Zoom the browser to 200%, then make the window as narrow as a small phone. Look for overlapping text, cut-off buttons and sideways scrolling.
-
Listen to one page.
NVDA is free on Windows and VoiceOver is built into Mac and iPhone. Move through the headings and links lists. If the headings do not outline the page, or links all read “learn more”, you have found the next fix.
-
Submit a form with mistakes.
Leave required fields empty and enter a bad email. Check the errors are described in text and announced.
-
Record and publish.
Keep a simple log of issues, fixes and dates, and publish an accessibility statement saying what standard you aim for, known limitations and how to contact you if something does not work.
WordPress accessibility: where it usually goes wrong
WordPress itself has a dedicated accessibility team and the core admin is built with accessibility in mind. Most problems come from themes, page builders, plugins and content choices:
- Removed focus outlines. Many themes and custom CSS strip
outlineon links and buttons because it “looks messy”. Put a clear focus style back in the child theme. - Headings picked by size. In Elementor it is easy to make a heading widget an H2 because it looks right, then use an H5 for a big tagline. Set the HTML tag for structure, then style it.
- Alt text in the wrong place. Alt text set in the media library is the default, but some widgets let you override it or ignore it. Check the output, not just the library.
- Sliders, tabs and popups. Check every interactive widget with the keyboard. Replace any that trap focus or cannot be paused.
- Form plugins. Most major form plugins can output proper labels and error messages, but only if the labels are not hidden for design reasons. If you are wiring forms into a CRM, the guide to connecting WordPress forms to your CRM covers the integration side.
- Cookie banners. They appear on every first visit, so a banner that cannot be reached or dismissed by keyboard blocks the whole site. The cookie consent and Consent Mode v2 guide covers choosing a banner; test its keyboard behaviour before you commit.
Accessibility and performance overlap more than people expect. Lean, well-structured markup is easier for screen readers and faster to load, and the clean-up work in fixing a slow Elementor website often removes nested wrappers that confuse assistive technology too. Lighthouse reports both scores side by side, so it is worth reviewing them together with your Core Web Vitals.
Finally, accessibility drifts. A new plugin, a redesigned button or a batch of blog posts with no alt text will undo good work. Add the keyboard and contrast items from this website accessibility checklist to your WordPress maintenance checklist and run it after every significant change.
Mistakes I see most often
- Light grey body text and pale buttons chosen for brand reasons, failing contrast.
- Alt text that says “image”, repeats the file name or is stuffed with keywords.
- Placeholder text used instead of labels, so the label vanishes as you type.
- Focus outlines removed site-wide.
- Important information only in PDFs or images of text.
- Relying on an overlay plugin and treating the work as done.
- Testing once at launch and never again.
Further reading: W3C: WCAG 2.2 · How to Meet WCAG (quick reference) · What’s new in WCAG 2.2.
FAQ
Which WCAG level should a small business website aim for?
Level AA of the current version, WCAG 2.2. Level A covers the most basic barriers and is not enough on its own, while Level AAA is demanding and not expected for whole sites. AA is the level that most laws, procurement rules and accessibility standards point to, and it is achievable for an ordinary business site with sensible design and build choices.
Does the European Accessibility Act apply to my website?
It applies from 28 June 2025 to many consumer-facing digital services offered in the EU, including e-commerce, and it can cover businesses based outside the EU that sell to EU consumers. Microenterprises providing services, those with fewer than ten staff and turnover or balance sheet of no more than two million euros, are exempt. Check your own position with a legal adviser.
Can an accessibility overlay plugin make my site compliant?
No. Overlays add a toolbar or try to repair pages automatically in the browser, but they cannot reliably fix missing labels, poor heading structure, keyboard traps or unclear content, and they can interfere with the assistive technology people already use. Fixing the underlying theme, content and forms is the only dependable route to an accessible website.
How do I check my WordPress site for accessibility?
Run an automated scan with a tool such as WAVE, axe DevTools or the Lighthouse accessibility audit, then test by hand: navigate every key page using only the keyboard, zoom to 200 percent, check the layout at a narrow width, and listen to a page with a screen reader such as NVDA or VoiceOver. Automated tools only find part of the problems.
Is website accessibility a legal requirement in the US and UK?
In the US, the Americans with Disabilities Act has been applied to business websites in many court cases, and WCAG 2.1 or 2.2 AA is the usual benchmark. In the UK, the Equality Act 2010 requires service providers to make reasonable adjustments, which includes websites, and public sector bodies have specific regulations. Requirements depend on your situation, so take legal advice.
If you would rather have someone run this checklist on your WordPress site and fix what it finds in the theme rather than with an overlay, see the WordPress development service, or get in touch for an accessibility pass.