A 20-minute accessibility check you can run on your own website

A full accessibility audit is a proper piece of work. But most of the problems I see on small business websites aren't subtle. They're things anyone can find in about twenty minutes with a keyboard, the browser's zoom setting and a couple of free tools.

This isn't a compliance certificate. It's a quick way to find out whether people using a keyboard, a screen reader, a zoomed-in screen or a phone in bright sunlight can actually use your site, and to fix the obvious things first.

The reference behind all of this is the W3C's Web Content Accessibility Guidelines (WCAG) 2.2. You don't need to read it to run these checks, but it's where the numbers below come from.

1. Put the mouse away (5 minutes)

Open your home page, click into the address bar, then press Tab repeatedly. Work through the page and then your most important journey: the contact form, a booking, or adding something to the cart and getting to checkout.

Look for:

  • Can you always see where you are? There should be a visible outline or highlight on whatever has focus. If it disappears, that's a problem, and it's often caused by a theme or a line of CSS that removed the default outline.
  • Is anything hidden behind something else? Sticky headers, cookie banners and chat bubbles can cover the focused element. WCAG 2.2 added a specific rule about this ("Focus Not Obscured").
  • Can you open and close menus, pop-ups and accordions with Enter, Space and Escape?
  • Can you finish the job? If you can't submit the form or reach the checkout button without a mouse, some of your visitors can't either.

2. Zoom in (3 minutes)

Set the browser zoom to 200%, then 400%. At 400% on a typical laptop, the page behaves roughly like a 320-pixel-wide screen, which is the width WCAG uses for its reflow requirement.

Text should get bigger and wrap. You shouldn't have to scroll sideways to read a paragraph, and nothing important should be cut off or overlap. Fixed-height boxes, text inside images and headers that take up half the screen are the usual causes.

3. Check colour contrast (4 minutes)

Light grey text on white looks elegant in a mockup and is hard to read for a lot of people, especially on a phone outdoors.

WCAG asks for a contrast ratio of at least 4.5:1 for normal body text and 3:1 for large text. You don't have to calculate it: paste your text and background colours into the free WebAIM contrast checker. Check body text, links, placeholder text in forms, and text sitting on top of photos.

Don't rely on colour alone, either. If a form error is only shown by turning a border red, add a written message too.

4. Look at your forms (3 minutes)

Forms are where accessibility problems cost you enquiries and orders.

  • Every field should have a visible label, not just placeholder text that disappears when you start typing.
  • Error messages should say what's wrong and how to fix it ("Enter a phone number with your area code"), next to the field.
  • Buttons and links should be big enough to tap. WCAG 2.2's minimum target size is 24 by 24 CSS pixels, with some exceptions. Bigger is better on a phone.

5. Run an automated check (3 minutes)

Free tools catch a useful share of problems quickly:

  • WAVE from WebAIM shows issues directly on your page.
  • Lighthouse, built into Chrome's developer tools, has an Accessibility section.

Things they find well include missing image descriptions (alt text), empty links and buttons, missing form labels, skipped heading levels and missing page language. What they can't tell you is whether the alt text is actually useful, or whether the page makes sense to a person. That's why the keyboard and zoom checks come first.

6. Listen to one page (2 minutes)

Both major desktop systems have a free screen reader built in: VoiceOver on a Mac (Command + F5) and Narrator on Windows (Ctrl + Windows key + Enter).

Turn it on, open your home page and just listen for a minute. Do the links say where they go, or is it "click here, click here, read more"? Do images of your products or team get a sensible description? Does the page have a clear main heading? Turn it off again with the same shortcut.

What I'd fix first

If you find a lot, don't try to fix everything at once. Start with whatever blocks a task: a form you can't submit by keyboard, a checkout button hidden behind a banner, or text that's unreadable. Then work outwards to contrast, labels and alt text across the rest of the site.

I'd also be wary of one-line "accessibility widget" plugins that promise to fix a site automatically. The issues above live in your theme, content and forms, and that's where they need fixing.

Where I fit in

Accessibility is part of how I design and build sites, whether it's a WordPress or WooCommerce site, a Shopify store or a custom web app. If you've run this check and found problems you'd like a hand with, get in touch and tell me what you found.