An accessible website is one that people can use regardless of disability, device or situation: someone with low vision, someone who cannot use a mouse, an older customer on a small phone, or anyone reading in bright sunlight. Accessibility is often treated as a specialist topic, but most of it comes down to good design habits that also make a site clearer, faster and easier to use for everyone.

This checklist covers the practical basics for business websites, based on the Web Content Accessibility Guidelines (WCAG), the international standard published by the W3C. The current version, WCAG 2.2, became a W3C Recommendation in 2023.

Why it matters for a business

  • More customers can use your site. Disability is common, and many more people have temporary or age-related difficulties with vision, hearing or movement.
  • Better experience for everyone. Clear text, good contrast and simple forms help all visitors, especially on phones.
  • Search engines benefit too. Descriptive headings, link text and image descriptions help search engines understand your pages.
  • Requirements are growing. Accessibility is increasingly expected in tenders, corporate procurement and some overseas markets, so it is worth building in from the start.

1. Text and colour

  • Contrast: normal text should have a contrast ratio of at least 4.5 to 1 against its background, and large text at least 3 to 1. Light grey text on white often fails. Free contrast checkers show the ratio instantly.
  • Do not rely on colour alone. Error messages, required fields and links should be identifiable by text or icons as well as colour.
  • Readable size and spacing. Body text that is comfortable on a phone without zooming, with enough line spacing.
  • Text that can be enlarged. The page should still work when the visitor zooms to 200 percent.

2. Images and media

  • Give meaningful images alt text that describes what matters in the image: "Completed open-plan kitchen with white quartz island" rather than "image1.jpg".
  • Leave alt text empty for purely decorative images, so screen readers skip them.
  • Do not put important text inside images; it cannot be read by screen readers, translated or found by search engines.
  • Provide captions for videos with speech, and avoid content that autoplays with sound.
  • Animation should not flash rapidly, and visitors who prefer reduced motion should be able to turn it off or see a calmer version.

3. Keyboard and focus

Some people navigate with a keyboard, switch device or voice control rather than a mouse.

  • Every link, button, menu and form field should be reachable with the Tab key, in a logical order.
  • The currently focused element should have a visible focus outline. Removing it for appearance is a common mistake.
  • Menus, pop-ups and image galleries should open, close and work by keyboard, and should not trap the focus.
  • Provide a "Skip to content" link so keyboard users do not have to tab through the whole menu on every page.
  • Use one H1 per page, then H2 and H3 headings in order. Screen reader users often jump between headings to scan a page, just as sighted visitors scan visually.
  • Make link text descriptive. "Read our renovation pricing guide" is clear out of context; "click here" is not.
  • Use real lists and tables in the code for lists and tabular data, not text styled to look like them.
  • Declare the page language so screen readers pronounce the text correctly, especially on multilingual websites.

5. Forms

Forms are where accessibility problems most often cost you enquiries.

  • Every field needs a visible label, not just placeholder text that disappears when you type.
  • Mark required fields clearly in text.
  • Error messages should say what went wrong and how to fix it, next to the field: "Enter a phone number with the area code", not just a red border.
  • Do not set short time limits, and make sure any spam challenge has an accessible alternative.
  • Make buttons large enough to tap: WCAG 2.2 includes a minimum target size so controls are not too small or too close together.

6. Mobile and touch

  • The layout should adapt to small screens without sideways scrolling.
  • Floating buttons, such as chat or WhatsApp buttons, must not cover content or other controls.
  • The site should work in both portrait and landscape orientation.

How to test your site in an hour

  1. Keyboard test: put the mouse aside and use Tab, Shift+Tab and Enter to navigate the homepage and submit the contact form.
  2. Zoom test: zoom the browser to 200 percent and check that nothing overlaps or disappears.
  3. Automated check: run Lighthouse in Chrome's developer tools, or a free tool such as WAVE, and read the accessibility issues it reports. Automated tools catch only some problems, so treat the result as a starting point.
  4. Screen reader test: try a built-in screen reader, such as VoiceOver on iPhone or TalkBack on Android, on your main page and form.
  5. Content check: review images for alt text, links for descriptive wording and headings for a logical order.

Build it in from the start

Fixing accessibility after launch costs more than designing for it. When you brief a web designer, ask how they handle contrast, keyboard navigation, form errors and alt text, and ask to see an accessibility check before launch. Our website brief template has space for requirements like these.

Accessibility checks are part of how we design and test every site. If you would like yours reviewed, ask us, and pair it with our technical SEO checklist.