
Key points
- Accessibility follows the WCAG guidelines, built on four ideas: perceivable, operable, understandable and robust.
- Most problems come from a short list: missing alt text, low contrast, unlabelled form fields, poor headings, no keyboard access, vague links.
- Automated tools find only part of the problems. Always try the page with a keyboard too.
What accessibility means
Web accessibility is making sites usable by people with disabilities: blindness or low vision, deafness, motor impairments, cognitive differences and temporary limits such as a broken arm or bright sunlight. The standard most laws and policies refer to is the Web Content Accessibility Guidelines (WCAG), published by the W3C. Their four principles are that content must be perceivable, operable, understandable and robust.
Requirements differ between countries and sectors, so check what applies to you. Good HTML covers most of it either way.
The checklist
1. Describe images
Every meaningful image needs alt text that says what it shows or does. Decorative images get an empty alt="". See image alt text.
2. Use enough contrast
WCAG level AA asks for a contrast ratio of at least 4.5:1 for normal text and 3:1 for large text and for interface parts such as input borders and icons. Light grey on white is the usual failure.
3. Do not rely on colour alone
Errors, required fields and links should be marked by more than colour, for example an icon, text or underline.
4. Structure with headings and landmarks
- One
h1per page, thenh2andh3in order without skipping levels for styling reasons. - Use
main,nav,headerandfooterso screen reader users can jump between regions. Check your outline with the headings checker.
5. Label every form field
Each input needs a visible <label> connected to it. A placeholder is not a label, because it vanishes when typing. Make error messages specific and link them to the field.
6. Make everything work with a keyboard
- You must be able to reach and use every link, button, menu and form control with Tab, Shift+Tab, Enter and Space.
- Keep a clearly visible focus outline. Do not remove it without a replacement.
- Offer a skip link to jump past repeated navigation.
- Avoid keyboard traps, such as dialogs that cannot be closed.
7. Write meaningful link and button text
"Read the pricing guide" works out of context. "Click here" and "more" do not, since screen reader users often list links on their own. Icon-only buttons need an accessible name.
8. Set the page language and title
Use <html lang="en"> (or the correct code) so screen readers choose the right pronunciation, and give each page a unique, descriptive <title>.
9. Provide alternatives for media
Videos need captions, audio needs a transcript, and nothing should autoplay with sound.
10. Let people resize text
The page should stay usable at 200% zoom without sideways scrolling in most layouts, and zoom must not be blocked. See the mobile checklist.
11. Use ARIA carefully
The first rule of ARIA is to use a native HTML element when one exists: a real <button> is better than a div with a role. Wrong ARIA is worse than none.
How to test
- Run the accessibility checker for common HTML barriers: missing alt, unlabelled fields, empty links, landmarks and more.
- Press Tab from the top of the page and use only the keyboard to complete a task, such as a purchase or form. Is the focus always visible and the order logical?
- Zoom the browser to 200% and look for overlapping or hidden content.
- Try a screen reader on one key page: VoiceOver on Mac and iOS, TalkBack on Android, or NVDA on Windows (free).
- Run Lighthouse's accessibility audit or a browser extension, and check colour contrast with a contrast checker.
Automated checks find only a portion of accessibility problems. They cannot judge whether alt text is helpful, whether the reading order makes sense or whether the page is easy to understand. Treat a clean automated report as a starting point.
Accessibility and SEO
Accessibility is not a ranking factor on its own, but many fixes overlap with SEO: descriptive alt text, clear headings, meaningful link text, page titles and a fast, stable page. A site that is easy to navigate for assistive technology is generally easy for crawlers to understand too.
FAQ
What is WCAG?
The Web Content Accessibility Guidelines, a set of testable criteria published by the W3C. They have three levels, A, AA and AAA, and AA is the usual target for laws and policies.
Is an automated accessibility score enough?
No. Automated tools cover a part of the criteria. Manual checks, such as keyboard use and reading order, are needed for a fuller picture.
Do accessibility fixes help SEO?
Often yes, indirectly. Alt text, headings, link text, titles and good performance help both people and search engines, though accessibility itself is not a ranking factor.
What contrast ratio do I need?
For WCAG AA, 4.5:1 for normal text, and 3:1 for large text and interface components such as input borders.
Where should I start?
Fix the common issues first: alt text, labels on form fields, heading structure, contrast, focus visibility and descriptive links. Then test the main journeys with a keyboard.