Blog · 7 min read

Website accessibility: a WCAG checklist for any site

Published

Website accessibility: a WCAG checklist for any site

Millions of people browse with screen readers, keyboards only or screen magnification. If your website is built without them in mind, they cannot use it, and you lose customers and goodwill. Accessible sites are also clearer for everyone else, and they tend to do better in search.

This checklist works on any platform, whether your site runs on WordPress, Shopify, Wix, Joomla, Magento or custom code. It is general guidance, not legal advice.

Why accessibility matters

What automatic testing can and cannot do

Automatic tools catch only a portion of problems. They are good at finding missing text alternatives, form labels, empty links and buttons, page language and heading structure. They cannot judge colour contrast reliably, keyboard focus order or whether a link's wording makes sense. Treat a clean result as a good start, not a certificate.

Step 1: run a free check

Use the website accessibility checker on your home page and on a page with a form. It checks common WCAG 2.1 problems: missing alt text, unlabelled form fields, empty links and buttons, heading order and the page language.

Step 2: fix the most common problems

1. Images without alt text

Every meaningful image needs a short description in its alt attribute, such as "Red running shoes, side view". Purely decorative images should have an empty alt="" so screen readers skip them. This is the most common problem on the web.

2. Form fields without labels

Each input needs a visible label linked to it. A placeholder alone is not a label, because it disappears when someone starts typing and many screen readers do not announce it.

3. Empty links and buttons

An icon-only button, such as a magnifier or a menu icon, needs an accessible name, for example aria-label="Search". Links reading only "Click here" or "Read more" mean nothing out of context, so describe where they go.

4. Heading order

Use one main heading (h1) per page, then h2 and h3 in order. Do not pick a heading level because of its size. Screen reader users jump between headings to scan a page.

5. Page language

Set the language on the page, for example <html lang="en">, so screen readers use the right pronunciation.

6. Colour contrast

Text needs enough contrast against its background. WCAG asks for at least 4.5 to 1 for normal text. Light grey text on white is the usual offender. Also never use colour alone to show meaning, such as red for errors with no text.

7. Keyboard use

Put the mouse aside and try your site with Tab, Shift+Tab, Enter and Space. You should reach every link, button and form field in a sensible order, see where the focus is and be able to close menus and pop-ups without a mouse.

8. Video and audio

Provide captions for videos and a transcript for audio. Do not start media automatically with sound.

Step 3: test with real tools

Step 4: make it part of the routine

Accessibility problems return when content changes. Add alt text whenever you upload an image, label every new form and re-run the check after each redesign, plugin or theme change. Also keep an eye on the rest of your site's health, such as page speed and the cookie and privacy setup, because they affect the same visitors.

Common questions

Is the automatic check a full WCAG audit?

No. It covers the checks that are possible on the page source. A full audit adds manual testing with a keyboard and screen reader.

What is the most common accessibility problem?

Images without alt text, followed by low colour contrast and form fields without labels.

Do accessibility overlays or widgets fix everything?

No. They can help a little, but they do not repair missing labels, poor structure or bad contrast in your code. Fix the underlying page.

Does it cost a lot to fix?

Most common issues take little time: alt text, labels, headings and language. They are far cheaper to build in than to repair later.

Free tools for this problem

More guides