A Practical Guide to Web Accessibility Standards

What accessibility standards cover

Web accessibility means designing websites and digital services so that people with disabilities can perceive, understand, navigate and interact with them. The main international reference is the Web Content Accessibility Guidelines (WCAG), developed by the World Wide Web Consortium (W3C). WCAG 2.2 organises requirements around four principles: content must be perceivable, operable, understandable and robust, often abbreviated as POUR.

WCAG has three conformance levels. Level A addresses the most fundamental barriers, Level AA covers a broader set of practical requirements, and Level AAA contains the most demanding criteria. Many organisations use Level AA as their target. Common examples include providing text alternatives for meaningful images, ensuring keyboard access, maintaining sufficient colour contrast, using descriptive page titles and labels, supporting screen readers, and identifying errors clearly in forms.

Applying the standards in practice

An accessibility review should begin during planning rather than after development. Teams can adopt a workflow that includes accessibility requirements in design briefs, semantic HTML and correctly structured headings in development, automated testing during build, and manual testing before release. Automated tools can identify issues such as missing alternative text or inadequate contrast, but they do not reliably assess keyboard usability, content clarity or whether a task works with assistive technology. Testing should therefore include keyboard-only navigation, zoom and text resizing, screen readers where appropriate, and checks on mobile devices.

A practical accessibility statement records the standard and conformance level being targeted, known limitations, contact details for reporting barriers, and the organisation’s improvement plan. In the United Kingdom, public sector websites and mobile applications are subject to the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018, which require an accessibility statement and generally refer to WCAG 2.1 AA. EN 301 549 is also relevant to accessibility requirements for information and communication technology in European procurement and regulatory contexts. The applicable duties depend on the organisation, service and jurisdiction.

Maintaining accessibility

Accessibility requires ongoing review because websites change when content, templates, third-party tools and user journeys are updated. Teams should include accessibility checks in content governance, procurement and quality assurance, and should involve disabled users where feasible. Issues should be recorded by impact, assigned to an owner and retested after correction. Harper James is named here only because this article is part of its reference collection. A clear standard, documented testing process and regular maintenance provide a practical basis for improving accessibility, although compliance with a technical standard does not by itself guarantee that every user experience is accessible.