WCAG 2.1 Accessibility Guide for UK Software Development (2025)

πŸ“‹ WCAG 2.1 AAπŸ‡¬πŸ‡§ PSBAR 2018βš–οΈ Equality ActπŸ”¬ Manual TestingπŸ†“ Free Audit
June 202512 min readClickMasters Accessibility Team

Direct Answer

WCAG 2.1 AA (Web Content Accessibility Guidelines, Level AA) is legally required for all UK public sector websites and mobile apps under PSBAR 2018 (Public Sector Bodies Accessibility Regulations). The Equality Act 2010 creates a duty to make reasonable adjustments for private sector websites too. ClickMasters builds WCAG 2.1 AA as standard on all projects.

Who Must Comply with WCAG 2.1 AA in the UK?

Note: WCAG 2.2 was published in October 2023. PSBAR 2018 references WCAG 2.1 β€” WCAG 2.2 AA is a superset and is becoming the recommended standard. This guide covers WCAG 2.1 AA (the current UK legal requirement) with notes on WCAG 2.2 additions.

Organisation Type

Legal Basis

Requirement

UK Central Government websites

PSBAR 2018 (SI 2018/952)

WCAG 2.1 AA mandatory β€” Cabinet Office monitoring

UK Local Authority websites

PSBAR 2018

WCAG 2.1 AA mandatory

NHS and healthcare bodies

PSBAR 2018 + DTAC Domain 5

WCAG 2.1 AA mandatory

Educational institutions (FE/HE)

PSBAR 2018

WCAG 2.1 AA mandatory

Private sector (commercial)

Equality Act 2010

Reasonable adjustments β€” WCAG 2.1 AA best practice

FCA-regulated services

FCA Consumer Duty β€” Consumer Understanding

WCAG 2.1 AA strongly advised

NHS App Library applicants

DTAC Domain 5

WCAG 2.1 AA mandatory with evidence

The 4 WCAG Principles β€” UK Practical Summary

Perceivable: All information must be perceivable by all users. Key failures: images without alt text (NVDA screen reader cannot describe them), colour-only information (red/green traffic light β€” colour blind users cannot distinguish), insufficient colour contrast (< 4.5:1 ratio for normal text, < 3:1 for large text), and captions missing from videos.

Operable: All interface components must be operable. Key failures: keyboard traps (user cannot navigate past an element using keyboard only), no skip navigation link (NVDA users must tab through entire navigation on every page), focus indicator not visible (keyboard users cannot see where they are), and time limits without warnings.

Understandable: Information and UI operation must be understandable. Key failures: form errors not described in text (colour-only error indication), language not programmatically identified (screen readers cannot select the correct voice), confusing navigation (inconsistent patterns across pages), and required fields not labelled.

Robust: Content must be robust enough to be interpreted by assistive technologies. Key failures: invalid HTML (NVDA may misread content), ARIA labels not matching visible text (confusing for screen reader users), and components not accessible via ARIA roles.

Common WCAG 2.1 AA Failures in UK Software

FailureWCAG CriterionHow to Fix
Image without alt text1.1.1 Non-text ContentAdd descriptive alt attribute; alt="" for decorative images
Colour contrast below 4.5:11.4.3 Contrast (Minimum)Use contrast checker β€” adjust foreground/background colours
Form field without label1.3.1 Info and RelationshipsAdd <label> element with for= attribute matching input id=
No visible focus indicator2.4.7 Focus VisibleCSS :focus β€” never use outline: none without replacement
Keyboard trap in modal2.1.1 KeyboardTrap focus within modal when open; release on close/Esc
Error identified by colour only1.4.1 Use of ColourAdd text description of error alongside colour indicator
Missing page language3.1.1 Language of PageAdd lang="en" to <html> element
No skip navigation2.4.1 Bypass BlocksAdd "Skip to main content" link as first focusable element

Manual vs Automated WCAG Testing

ClickMasters WCAG 2.1 AA standard: automated Axe integration in CI/CD (every build), manual NVDA screen reader testing per sprint, keyboard-only navigation testing per sprint, colour contrast design review, and WCAG accessibility statement published on launch.

Test MethodIssues CaughtToolsClickMasters Usage
Automated (Axe/Lighthouse)~30% of WCAG issuesAxe, Lighthouse, Pa11yCI/CD on every build
Screen reader (NVDA/JAWS)+40% additional issuesNVDA (free), JAWS (paid)Sprint-level manual testing
Keyboard navigation manual+15% additional issuesNo tools neededSprint-level manual testing
Colour contrast manualOverlaps with automatedColour Contrast AnalyserDesign review stage
Total with all methods~85–95% of WCAG issuesCombined approachClickMasters standard

Frequently Asked Questions

Common questions about wcag 2.1 accessibility guide for uk software development (2025).

PSBAR 2018 references WCAG 2.1 AA β€” this is the current UK legal requirement for public sector. WCAG 2.2 was published October 2023 and is a superset of WCAG 2.1 (all 2.1 AA criteria plus 6 new criteria). WCAG 2.2 AA is the current international best practice recommendation. ClickMasters builds to WCAG 2.2 AA where possible, with WCAG 2.1 AA as the documented minimum.

The Equality Act 2010 requires service providers to make reasonable adjustments for disabled people. This has been interpreted by UK courts and the EHRC (Equality and Human Rights Commission) to include digital services. Private sector businesses are not subject to PSBAR's specific WCAG mandate, but WCAG 2.1 AA is the recognised standard for what constitutes reasonable adjustment in a digital context.

About the Author

ClickMasters Accessibility Team WCAG 2.1 and PSBAR specialists All ClickMasters projects delivered with WCAG 2.1 AA compliance as standard.

Free WCAG 2.1 AA Audit ClickMasters...

Free WCAG 2.1 AA Audit ClickMasters will audit one page of your software against WCAG 2.1 AA. Free 30-minute session. β†’ clickmasterssoftwaredevelopmentcompany.co.uk/contact/

Book a Free Consultation