What website accessibility means in practice
Website accessibility is about removing barriers. Picture a blind solicitor's client navigating with a screen reader, a retired engineer with tremors who uses only a keyboard, someone with low vision who zooms text to 200 percent, or a deaf customer watching your explainer video. Each of them should be able to find information, complete a form and buy or book without help.
It also helps anyone with a broken wrist, a phone in bright sunlight, a slow connection or dyslexia. The guidelines rest on four principles. Content must be:
- Perceivable: available to people who cannot see or hear part of it, through text alternatives, captions and sufficient contrast.
- Operable: usable with a keyboard and other input methods, with enough time and no traps.
- Understandable: written clearly, with predictable navigation and forms that explain errors.
- Robust: built with sound code that assistive technologies can interpret reliably.
WCAG versions and levels, explained
The Web Content Accessibility Guidelines are published by the W3C, the body that maintains web standards. They consist of testable success criteria grouped into three levels:
- Level A: the essentials. Without them, some people cannot use the site at all.
- Level AA: the level generally used as the benchmark in law, procurement and policy. It includes adequate colour contrast and a visible keyboard focus.
- Level AAA: the most demanding level, rarely realistic for an entire site and not usually expected.
WCAG 2.2 is the current W3C recommendation and builds on 2.1. It adds criteria such as focus that is not hidden behind other elements, minimum target sizes for buttons and links, alternatives to dragging and accessible authentication that does not depend on memory tests. A site that meets 2.2 AA also meets 2.1 AA. The W3C's WCAG overview is a good plain-English starting point.
Is website accessibility a legal requirement in the UK?
This is general information, not legal advice; check with a solicitor if you need certainty about your position.
The Equality Act 2010
The Equality Act 2010 applies in England, Scotland and Wales and prohibits discrimination by those who provide services to the public. It includes a duty to make reasonable adjustments for disabled people. The Act does not name websites or WCAG, but a website is often how a service is offered, and GOV.UK guidance states that all UK service providers have a legal obligation to make reasonable adjustments. In Northern Ireland, the Disability Discrimination Act 1995 plays the equivalent role. In practice, building to WCAG AA is the most sensible way to show you have taken accessibility seriously.
Public sector bodies
Central and local government, and many other public sector bodies, must meet the Public Sector Bodies (Websites and Mobile Applications) Accessibility Regulations 2018. The government's guidance on accessibility requirements for public sector websites and apps currently points to WCAG 2.2 AA and requires an accessibility statement. Some organisations are exempt or partly exempt, so the guidance is the place to check.
The European Accessibility Act, if you sell into the EU
The European Accessibility Act is EU law and does not apply in the UK as such. It has applied in EU member states since 28 June 2025 to certain products and services offered to consumers, including ecommerce. A UK business selling to EU consumers, for example an online shop shipping to Ireland or France, may fall within it for those sales. Very small service businesses are largely exempt under the directive. If EU sales matter to you, take advice on whether and how it applies.
| Your situation | Rules to be aware of | What it usually means in practice |
|---|---|---|
| Private business serving the public in Great Britain | Equality Act 2010, duty to make reasonable adjustments | Remove barriers disabled customers face; WCAG AA is the practical benchmark |
| Business in Northern Ireland | Disability Discrimination Act 1995 | A comparable duty; take local advice on the detail |
| Public sector body | Public sector accessibility regulations 2018 | Meet the WCAG level set in government guidance and publish an accessibility statement |
| UK business selling to EU consumers | European Accessibility Act, as implemented in each member state | In-scope services such as ecommerce may need to meet EU accessibility requirements for those sales |
| Organisation bidding for public contracts | Procurement requirements set by the buyer | Tenders often ask for evidence of WCAG conformance |
Why accessibility pays off beyond compliance
- More people can buy from you. A meaningful share of any audience has a visual, hearing, motor or cognitive impairment, permanent or temporary.
- Better usability for everyone. Clear headings, good contrast, simple forms and generous touch targets help every mobile visitor.
- Stronger search foundations. Logical headings, descriptive link text and text alternatives help search engines and AI assistants understand your content. Accessibility and speed often improve together.
How we test website accessibility
Accessibility testing has two halves, and automated tools alone are never enough.
Automated checks
A checker scans pages for issues visible in the code: missing text alternatives, low contrast, unlabelled form fields, empty links. Useful as a first pass, but whether alt text is meaningful, reading order makes sense and error messages are clear needs human judgement.
Manual checks
- Working through the whole site with a keyboard only: can you reach everything, and can you always see where focus is?
- Testing key pages and forms with a screen reader, such as NVDA on Windows or VoiceOver on Apple devices.
- Zooming to 200 percent and reflowing on a narrow screen to confirm nothing is lost.
- Checking video captions, transcripts and whether PDFs are usable.
The W3C's guidance on evaluating web accessibility describes this layered approach. The outcome is a prioritised list: what blocks people completely, what makes tasks harder, and what is a minor improvement.
The fixes that come up on almost every site
- Colour contrast. Pale grey text on white, or white text over photos, is unreadable for many people.
- Text alternatives. Informative images get a meaningful description; decorative ones get an empty alt attribute.
- Keyboard access. Menus, buttons, pop-ups and carousels must work without a mouse, with a clearly visible focus style.
- Heading structure. One main heading and a logical hierarchy, so screen reader users can scan the page.
- Forms. Visible labels, clear required fields, and error messages that say what went wrong and how to fix it.
- Link text. "Read more" and "click here" mean nothing out of context; say where the link goes.
- Media. Captions on video and transcripts for audio where needed.
- Documents. PDFs are frequently inaccessible; important information is usually better as a web page.
Overlays are not a shortcut
Accessibility overlay widgets promise compliance with a line of script. They do not repair the underlying code, can interfere with the assistive technology people already use, and are widely criticised by disabled users and specialists. Fixing the site itself is the reliable route.
Accessible web design for law firms and professional services
Solicitors, accountants, clinics and financial advisers often serve clients at vulnerable moments, and many clients are older or have health conditions. A law firm website that cannot be used with a screen reader, or an enquiry form that fails for keyboard users, turns people away at the point they need help.
For law firm website accessibility, we pay particular attention to plain language in practice area pages, accessible fee and service information, enquiry forms with clear labels and error handling, readable profile pages for named solicitors, and documents offered as accessible pages rather than scanned PDFs. Accessibility work sits comfortably alongside SEO for law firms, because both reward clear structure and clear writing.
Accessibility statements
An accessibility statement explains how accessible your website is, which parts do not yet meet the standard, what you are doing about it and how visitors can report a problem or ask for information in another format. For public sector bodies it is required, and GOV.UK publishes a sample accessibility statement. For private businesses it is good practice and a clear signal of intent.
A good statement is honest: no claim of full conformance unless true, a note of what was tested and when, what was found and what is planned, and a link from every page, typically in the footer.
Build it in, or fix it afterwards
Accessibility is cheapest when it is part of the design from the start: colours chosen with contrast in mind, components that work with a keyboard, forms with proper labels. Retrofitting means changes to design, code and content in many places at once.
The main cost drivers are the size of the site, the number of distinct page types and components, interactive features such as filters, configurators and checkouts, the volume of video and documents, and whether you need a formal audit with a written report. For a site with deep-rooted problems, a website redesign can be more economical than repairing page by page. For online shops, especially those selling into the EU, we treat accessibility as a fixed part of ecommerce website design.
How we work
At Kaptein Beacon, accessibility is a starting point in every website we build, not an optional extra. We design for contrast and focus, build with semantic code and test with keyboard and screen reader. On a custom website, the building blocks are set up so new pages inherit the same foundations. We are not lawyers and do not advise on whether a particular law applies to you; we point to the primary sources and your own adviser. Every engagement starts with the paid Beacon Strategy Session: 50 minutes with the founder, £225 excl. VAT, a conversation about your ambition, your market and whether we fit.