Website accessibility checklist guide for UK businesses
TL;DR:
- Website accessibility guidelines help businesses identify and fix barriers for disabled users by meeting standards like WCAG 2.2 Level AA. Achieving compliance involves combining automated scans with manual testing and proactive adjustments under the Equality Act 2010. Regular reviews and transparent accessibility statements are essential for maintaining inclusivity and legal compliance.
A website accessibility checklist guide is a structured set of criteria that helps business owners and website managers identify and fix barriers that prevent disabled users from accessing their content. In the UK, the recognised standard is WCAG 2.2 Level AA, published by the W3C. The Equality Act 2010 places an anticipatory duty on businesses to proactively remove accessibility barriers rather than waiting for a complaint. The Public Sector Bodies Accessibility Regulations 2018 extend those obligations further for public sector organisations. Whether you run a small business website or manage a large public-facing platform, this guide gives you the practical steps to get compliant and stay there.
What are the key accessibility standards and legal requirements for UK websites?
WCAG 2.2 Level AA is the de facto standard for UK website accessibility. It sets measurable criteria across four principles: websites must be perceivable, operable, understandable, and robust. Meeting these criteria satisfies the technical side of your legal obligations under both the Equality Act 2010 and the Public Sector Bodies Regulations 2018.
The Equality Act 2010 anticipatory duty requires businesses to make reasonable adjustments before a disabled person asks. That means you cannot wait for a complaint to act. Legal analysts confirm that treating accessibility as a routine business process significantly reduces litigation risk. This applies to private businesses, not just public bodies.
The Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018 go further. Public sector bodies must comply with WCAG 2.2 Level AA and publish updated accessibility statements annually. Government audits actively check compliance, so this is not a box-ticking exercise.
Key legal and standards requirements to address:
- Meet WCAG 2.2 AA criteria across all public-facing web pages and mobile applications
- Publish an accessibility statement that lists known issues, your remediation plans, and contact details for users who need help
- Update that statement at least once a year to reflect current compliance
- Apply the anticipatory duty under the Equality Act 2010 by auditing proactively, not reactively
- Review accessibility after any major redesign or content update
Publishing an accessibility statement with known issues and remediation plans is a legal requirement for public sector bodies and strongly recommended best practice for all businesses. It signals good faith and gives users a clear route to request help.
Which tools do you need to assess your website’s accessibility?
Automated tools are the fastest starting point, but they are not the whole answer. Tools such as axe, WAVE, and Google Lighthouse scan your pages and flag common issues like missing alt text, low colour contrast, and absent form labels. Automated tools detect only about 30–40% of accessibility issues. That means the majority of real barriers require a human to find them.
Manual testing fills the gap. The most dependable techniques are keyboard-only navigation and visible focus indicator checks. Try using your website without a mouse. Press the Tab key to move between interactive elements and check that each one receives a clearly visible focus outline. If you cannot see where the keyboard focus is, neither can a keyboard-dependent user.
Screen reader testing adds another layer. Tools like NVDA (free for Windows) and VoiceOver (built into macOS and iOS) read page content aloud. Testing with a screen reader reveals whether your headings, links, and form fields make sense when heard rather than seen.
| Testing method | What it finds | Limitation |
|---|---|---|
| Automated scan (axe, WAVE, Lighthouse) | Missing alt text, contrast failures, absent labels | Misses 60–70% of real issues |
| Keyboard navigation | Focus order, trapped focus, missing skip links | Requires manual effort |
| Screen reader testing | Heading structure, link context, form announcements | Needs familiarity with the tool |
| Colour contrast checker | Text and background contrast ratios | Does not test interactive states |
Pro Tip: Prioritise your highest-traffic pages first. Your homepage, contact form, and checkout process affect the most users, so start your audit there before working through the rest of the site.
Step-by-step checklist to improve website accessibility
This checklist covers the most common barriers found on UK business websites, mapped to WCAG 2.2 AA requirements. Work through it systematically and document what you find.
Add descriptive alt text to images. Every image that conveys information needs an alt attribute describing what it shows. Decorative images, such as background patterns, should use an empty alt attribute (
alt="") so screen readers skip them entirely.Check colour contrast ratios. Normal text requires a contrast ratio of at least 4.5:1 against its background. Large text (18pt or 14pt bold) requires 3:1. Use a free contrast checker to test every text and background combination on your site.
Verify focus indicators meet the minimum standard. WCAG 2.2 requires focus outlines of at least 2px solid with a 3:1 contrast ratio against adjacent colours. Many websites remove focus outlines with CSS to improve visual appearance. This breaks keyboard accessibility entirely.
Check interactive element sizes. Buttons, links, and form controls must meet a minimum target size of 24×24 CSS pixels. Small tap targets cause problems for users with motor impairments and on touchscreen devices.
Test all forms for labels and error messages. Every form field needs a visible, programmatically associated label. Error messages must describe the problem clearly and be announced to screen reader users automatically. “Invalid input” is not an acceptable error message. “Please enter a valid email address” is.
Review your authentication process. Accessible authentication avoids memory-based tests by allowing password manager autofill, copy-paste login, or one-time codes. WCAG 2.2 criteria 3.3.7 and 3.3.8 specifically address this. If your login form blocks paste or autofill, fix it.
Add skip navigation links. A “Skip to main content” link at the top of every page lets keyboard users bypass repeated navigation menus. It is one of the simplest fixes and one of the most impactful for keyboard-dependent users.
Check heading structure. Headings should follow a logical hierarchy: one H1 per page, followed by H2 for main sections, H3 for subsections. Screen reader users navigate by heading, so a broken hierarchy makes the page nearly impossible to scan.
Pro Tip: After fixing issues, retest with both an automated tool and keyboard navigation. Fixes sometimes introduce new problems, particularly with focus management in dynamic content like modals and dropdowns.
For a broader view of accessible design principles and how they apply to marketing websites, MB Web has published practical guidance worth reading alongside this checklist.
How do you maintain accessibility compliance over time?
Accessibility is not a one-time project. Websites change constantly, and each change can introduce new barriers. Regular accessibility reviews after major content updates or system redesigns are the most reliable way to maintain compliance and protect user experience.
A practical ongoing programme looks like this:
- Run automated scans monthly using axe or WAVE to catch regressions after content updates
- Conduct a full manual audit at least once a year, covering keyboard navigation, screen reader testing, and contrast checks
- Update your accessibility statement annually to reflect your current compliance level and any outstanding issues
- Assign a named person or team responsibility for accessibility, so it does not fall through the gaps during busy periods
- Brief content editors and developers on the most common issues: missing alt text, poor contrast, and unlabelled form fields account for the majority of failures
The Equality Act requires anticipatory adjustments, which means accessibility must be integrated as a routine business process rather than a one-time fix. Building accessibility checks into your content publishing workflow is far more effective than scheduling a single annual audit.
Even small businesses benefit from a proactive approach. Clear communication, a published accessibility statement, and regular reviews demonstrate good faith under the Equality Act, even if full WCAG 2.2 compliance is still a work in progress.
If you are preparing for a regulatory audit or simply want to understand where your site stands, MB Web’s guide on why accessibility matters for Sussex businesses covers the compliance landscape in plain language.
Key takeaways
A website’s accessibility compliance depends on combining automated testing with regular manual audits, mapped to WCAG 2.2 AA criteria and the anticipatory duty under the Equality Act 2010.
| Point | Details |
|---|---|
| WCAG 2.2 AA is the UK standard | All UK businesses should target WCAG 2.2 Level AA as the minimum compliance benchmark. |
| Automated tools have limits | Automated scans find only 30–40% of issues; manual keyboard and screen reader testing is essential. |
| Fix the most common barriers first | Alt text, colour contrast, focus indicators, and form labels cover the majority of accessibility failures. |
| Accessibility statements are required | Public sector bodies must publish and update statements annually; private businesses should follow suit. |
| Treat accessibility as ongoing | Build monthly automated checks and annual manual audits into your standard website management process. |
My honest view on accessibility compliance
I have worked on enough websites to know that accessibility is the area most business owners feel guilty about but do not know where to start. The honest truth is that the technical requirements are not as frightening as they look. Most of the issues that fail real users, missing alt text, invisible focus indicators, unlabelled form fields, are genuinely straightforward to fix once you know what to look for.
What I find most businesses get wrong is relying entirely on automated tools. Running Lighthouse and seeing a high score feels reassuring. It is not. Manual audit techniques, particularly keyboard-only navigation and focus indicator checks, remain the most dependable method for finding real barriers. Automated tools will not tell you that your modal traps keyboard focus, or that your error messages are announced too late for screen reader users to act on them.
The authentication issue is one I see repeatedly. Businesses block copy-paste in password fields thinking it improves security. It does not. It breaks accessibility and violates WCAG 2.2 criteria 3.3.7 and 3.3.8. Enable autofill, allow paste, and offer one-time codes. That is the right approach.
My practical advice: pick your five highest-traffic pages, run a keyboard-only test on each one, and fix what you find. That single exercise will surface more real issues than any automated scan. Accessibility improves when it becomes a habit, not a project.
— James Golding
How MB Web can help with accessible web design
Accessibility compliance does not have to be something you tackle alone. MB Web has spent decades helping businesses across Sussex and beyond build websites that work for every user, not just the majority.
Whether you need a full accessibility audit, help implementing WCAG 2.2 fixes, or a new site built with accessible web design at its core, we are happy to have an honest conversation about where your site stands and what it would take to get it right. We do not oversell and we do not overcomplicate. If you would like to talk through your website’s accessibility, get in touch with the MB Web team and let’s see how we can help.
FAQ
What is WCAG 2.2 and does it apply to my business?
WCAG 2.2 is the Web Content Accessibility Guidelines published by the W3C, and Level AA is the standard UK businesses are expected to meet under the Equality Act 2010. It applies to private businesses as well as public sector organisations.
How do I check my website’s accessibility quickly?
Run a free automated scan using tools like axe or Google Lighthouse, then follow up with a manual keyboard navigation test on your most visited pages. Automated scans alone find only 30–40% of issues, so the manual step is not optional.
What must an accessibility statement include?
An accessibility statement must list known accessibility issues, your plans to fix them, and contact details for users who need assistance. Public sector bodies must update their statement at least once a year.
What is the minimum colour contrast ratio for website text?
Normal body text must meet a contrast ratio of at least 4.5:1 against its background under WCAG 2.2 AA. Large text, defined as 18pt or 14pt bold, requires a minimum ratio of 3:1.
Does the Equality Act 2010 cover website accessibility?
Yes. The Equality Act 2010 requires businesses to make anticipatory reasonable adjustments for disabled people, which includes removing digital barriers on their websites before a complaint is made.