Key takeaways

  • An accessible website can be used by everyone, including people with visual, hearing, motor and cognitive impairments.
  • Service providers have duties under the Equality Act 2010 not to discriminate, and WCAG 2.2 level AA is the recognised benchmark.
  • Common problems on accounting sites are low contrast, missing image descriptions, inaccessible forms and PDFs.
  • Accessible sites are usually easier for everyone to use and tend to perform better in search.
  • Test with automated tools, a keyboard and a screen reader, then fix and publish an accessibility statement.

Accessibility means making your website usable by as many people as possible, including people who use screen readers, magnifiers, voice control or a keyboard instead of a mouse, and people with dyslexia, colour blindness or temporary injuries. Many of your clients, or their family members who help them, will be among them.

Why it matters for accounting firms

  • Legal duty: under the Equality Act 2010, businesses providing services to the public must not discriminate against disabled people and must make reasonable adjustments. A website that cannot be used by disabled people can create risk.
  • Clients: older clients, clients with visual impairments and those with dyslexia need to find information and contact you easily.
  • Better for everyone: clear structure, good contrast and simple forms help all visitors, especially on mobile.
  • Search and AI: well-structured, descriptive content is easier for search engines and AI tools to understand.

The standard: WCAG 2.2 AA

The Web Content Accessibility Guidelines (WCAG), published by the W3C, are the accepted standard. Level AA of WCAG 2.2 is the usual target. It is organised around four principles: content must be perceivable, operable, understandable and robust.

Common problems on practice websites

ProblemFix
Light grey text, or text over imagesEnsure at least 4.5:1 contrast for body text
Images without descriptionsAdd meaningful alt text; mark decorative images as decorative
Links such as “click here” or “read more”Make link text describe where it goes
Forms with placeholder text instead of labelsUse visible labels and clear error messages
Content only usable with a mouseMake menus, sliders and pop-ups work with a keyboard, with a visible focus outline
Rate tables built from imagesUse real HTML tables with headers
Scanned PDFs of guides and formsProvide accessible PDFs or HTML versions
Videos without captionsAdd captions and, where useful, transcripts
Cookie banners that trap keyboard usersUse an accessible consent tool
Time-limited sessions or auto-playing carouselsAvoid them, or let users pause and extend

A practical checklist

  • Body text at least 16px with good contrast
  • One H1 per page and a logical heading order
  • Alt text on informative images
  • Descriptive link text
  • All forms have labels and accessible error messages
  • Everything works with a keyboard, with visible focus
  • Pages work at 200% zoom and on small screens without horizontal scrolling
  • Touch targets large enough on mobile
  • Captions on videos
  • Language of the page set correctly
  • No information conveyed by colour alone

Testing

  1. Automated checks: browser tools such as Lighthouse and axe find many issues quickly, but not all.
  2. Keyboard test: use Tab, Shift+Tab, Enter and Space to navigate every page and complete the contact form.
  3. Screen reader test: try NVDA (Windows, free), VoiceOver (Mac and iPhone) or TalkBack (Android) on key pages.
  4. Zoom test: check pages at 200% and 400% zoom.
  5. Real users: if possible, ask people with different needs to try the site.

Accessibility statement

Publishing an accessibility statement is good practice for private businesses (and a requirement for public sector bodies). It should explain:

  • the standard you aim for
  • known issues and plans to fix them
  • how to contact you for content in another format or to report a problem

Building it in from the start

Accessibility is cheapest when designed in. Include it in your brief to a web designer, choose an accessible template or theme, and check content before publishing. See also typography and mobile-friendly websites.

Frequently asked questions

Private businesses are not covered by the public sector accessibility regulations, but the Equality Act 2010 requires service providers not to discriminate against disabled people and to make reasonable adjustments, which includes how they provide services online.

What is WCAG 2.2 AA?

The current version of the Web Content Accessibility Guidelines at level AA, the widely used benchmark for accessible websites.

How can I check if my website is accessible?

Run automated tools such as Lighthouse or axe, then test with a keyboard, a screen reader and high zoom levels.

Do accessible websites rank better on Google?

Accessibility is not a direct ranking factor, but many accessible practices, such as clear headings, descriptive links and alt text, also help search engines understand your pages.

Sources

Facts and rules in this guide were checked against the sources below in October 2026. Platforms, prices and regulations change, so check the current position before acting. This guide is general information, not legal or professional advice.