WCAG 2.2 Accessibility Testing Checklist for UK Websites
WCAG 2.2 Accessibility Testing Checklist for UK Websites
For teams shipping digital services in Britain, a reliable WCAG 2.2 accessibility testing checklist for UK websites turns a fuzzy compliance goal into clear test steps. This article translates the latest success criteria into hands-on checks you can run across real journeys—sign-in, search, payments, and support—covering both manual and automated techniques.
You will learn how to scope an audit, which tools to use when, and how to validate new WCAG 2.2 items such as focus visibility, dragging alternatives, target size, consistent help, redundant entry, and accessible authentication. We include quick wins specific to common UK patterns like cookie banners, PDFs, and public-sector style pages, plus simple test cases you can repeat in sprints.
The goal is practical confidence: identify barriers that affect keyboard, screen reader, and magnification users; reduce audit risk; and make content easier to use. This is guidance for testers, developers, and content designers—not legal advice—and it is written to help you run better checks today and plan smarter fixes tomorrow.
Practical WCAG 2.2 accessibility testing checklist for UK websites
Quick start: Test journeys, not just pages. Cover at least: home, one key content page, a search or filter, a form with validation, authentication, and a checkout or submission confirmation.
Scope and setup
- Browsers and devices: test desktop with keyboard, 400% zoom, and at least one mobile or responsive view.
- Assistive tech: NVDA on Windows and VoiceOver on macOS or iOS for at least one end-to-end flow.
- System preferences: enable reduced motion; try Windows High Contrast Mode if available.
- Automation first pass: run an axe or Lighthouse scan on each template; fix crashes and obvious contrast/label issues early.
- Sample content: include pages with video, maps or embeds, tables, and PDFs or downloadable documents.
Perceivable: text, media, and contrast
Key checks
- Images: meaningful alt for informative graphics; decorative images use empty alt; avoid images of text.
- Forms: every input has a visible label and a programmatic label; icons have accessible names.
- Media: captions for video; transcripts for audio; review auto-captions and fix errors.
- Contrast: body text around 4.5:1 and large text around 3:1; UI components and icons are distinguishable against backgrounds.
- Reflow and zoom: at 320 CSS px width and up to 400% zoom, content does not require two-way scrolling and retains functionality.
Helpful tools
- axe DevTools or WAVE for fast automated issues.
- Colour Contrast Analyser to verify text and UI contrast.
- Browser Accessibility tree/inspector to confirm names, roles, and states.
- Lighthouse Accessibility for a quick baseline report.
Operable: keyboard, focus, and navigation
What to test
- Keyboard access: all interactive items (menus, modals, tabs, carousels, custom widgets) are reachable and operable without a mouse.
- Focus order: tab moves in a logical sequence; focus is never trapped; Escape closes modals; focus returns to the trigger.
- WCAG 2.2 focus: focus is clearly visible and not hidden under sticky headers or overlays; the indicator has strong contrast and sufficient size.
- Target size: primary touch/click targets meet a sensible minimum hit area (around 24 x 24 CSS px) or have adequate spacing.
- Pointer gestures: dragging has an alternative (for example, click or buttons) so tasks do not rely on drag-only input.
- Bypass blocks: provide a visible-on-focus skip link and/or landmarks for quick navigation.
- Motion and flashing: respect reduced-motion settings; avoid flashing content.
Mobile nuance: Check off-canvas menus, sticky bars, and cookie banners for focus visibility, target size, and scroll prevention that may trap keyboard focus.
Understandable: forms, errors, and help
Form essentials
- Labels and instructions are visible; placeholders do not replace labels.
- Error messages appear next to fields and in a summary at the top; links take focus to the first error.
- Input assistance: use clear hints and autocomplete attributes where appropriate.
- Redundant Entry (2.2): previously provided data is retained or auto-filled; do not make users retype it.
- Accessible Authentication (2.2): allow paste and password managers; provide a show password option; avoid cognitive tests like solving puzzles.
Consistent support
- Consistent Help (2.2): a support link, chat, or phone number appears in a consistent location across similar pages.
- Clear language and formats: use plain English, clear date formats, and consistent error phrasing.
Robust: code quality and compatibility
Foundation checks
- Use native HTML controls where possible; add ARIA only when needed and correctly.
- Ensure accessible name, role, and value for custom widgets; update on interaction.
- Unique IDs; valid HTML; proper headings and landmark regions for structure.
- Dynamic updates announce via live regions when essential (for example, cart updates).
- Test with NVDA + Firefox or Edge, VoiceOver + Safari, and TalkBack + Chrome for core flows.
- Verify Windows High Contrast Mode and reduced-motion compatibility where relevant.
WCAG 2.2 additions at a glance
| WCAG 2.2 criterion | Simple manual test | Helpful tool |
|---|---|---|
| 2.4.11 Focus Not Obscured (Minimum) | Tab through a page with sticky headers/pop-ups; ensure the focus indicator is not covered. | Accessibility Insights focus order; devtools overlays |
| 2.4.13 Focus Appearance (Minimum) | Check that focus is clearly visible with strong contrast and adequate size on all controls. | axe rules for focus indicator; manual visual check |
| 2.5.7 Dragging Movements | Complete any drag task using click or buttons instead of dragging. | Manual keyboard and pointer test |
| 2.5.8 Target Size (Minimum) | Verify primary targets are comfortably tappable or spaced to avoid accidental taps. | Ruler/measure overlay; mobile device test |
| 3.2.6 Consistent Help | Confirm the same help option appears in the same place across related pages. | Visual compare across templates |
| 3.3.7 Redundant Entry | Progress through a multi-step form; ensure prior answers are retained or auto-filled. | Manual form journey test |
| 3.3.8 Accessible Authentication (Minimum) | Paste passwords; use a password manager; complete sign-in without solving a memory puzzle. | Manual; password manager check |
UK-specific considerations and quick wins
Audit-friendly practices
- Publish a clear accessibility statement with known issues and a contact route for feedback.
- Test cookie/consent banners for keyboard access, focus order, and visible focus; avoid trapping users before content.
- Provide HTML alternatives for key PDFs and office documents where practical.
- Plan for third-party widgets (maps, video players, captchas); configure accessible modes or provide alternatives.
Content and pattern tips
- Use clear UK date, time, and currency formats consistently.
- Keep headings meaningful and in order; use lists and tables semantically.
- For public services, align patterns with widely used UK design guidance to reduce friction.
Suggested test passes you can run this week
Quick Win Triage pass (30–45 minutes)
Best for: Rapid risk snapshot on key templates
Includes: axe/Lighthouse scan, keyboard tab pass, contrast spot-check
Tools: axe, Lighthouse, Colour Contrast Analyser
Thorough AA deep pass (2–3 hours)
Best for: Sprint-ready backlog items with evidence
Includes: Full P/O/U/R checks, zoom/reflow, reduced motion, mobile nav
Tools: Accessibility Insights, axe, NVDA, device testing
Real‑World Assistive tech pass (60–90 minutes)
Best for: Validating name/role/value and focus management
Includes: Screen reader journey for sign-in and one form
Tools: NVDA on Windows, VoiceOver on macOS or iOS
Mistakes to avoid
- Removing default focus outlines without a clear, visible replacement.
- Using placeholders as labels or hiding labels visually.
- Blocking zoom or breaking layouts at 320 px width.
- Relying on drag-only interactions or small targets on mobile.
- Launching modals or banners that trap focus or hide the focus indicator.
- Publishing video without captions or audio without transcripts.
- Forgetting redundant-entry and accessible-authentication behaviours in forms.
Final advice
Treat WCAG 2.2 AA as a practical baseline for everyday quality, not a once‑a‑year audit event. Start with your core journeys, blend automated checks with careful keyboard and assistive-technology testing, and document clear steps to reproduce issues. Prioritise fixes that unblock tasks, improve focus visibility, and reduce form friction. Re-test after each change, keep your accessibility statement current, and build accessibility checks into your definition of done.
Turn what you just learned into a real IT career move
Whether you want to build job-ready skills, follow a structured career path, or get expert advice before choosing a course, Codionix IT Training UK can help you move forward with confidence.
Explore IT Courses
Browse instructor-led training across cloud, cybersecurity, networking, data, support, digital skills, and more.
View CoursesView Career Paths
See structured pathways designed to help you progress toward roles like helpdesk technician, network engineer, ethical hacker, and beyond.
Explore Career PathsBook Free Consultation
Not sure which course or path fits you best? Speak with the team and get clear, practical guidance before you commit.
Get Free AdviceRelated articles

Ecommerce Load Testing Checklist UK for Peak Season
A practical, step-by-step guide for UK retailers preparing for peak season. Covers environment setup, data strategies, and clear pass/fail criteria.

AI in Software Testing UK 2026: Safe, Effective QA Practices
A practical guide for UK QA teams on using AI for test design, data handling, and coverage in 2026. It covers guardrails for privacy and human oversight.

Fix Flaky UI Tests in CI: Proven End-to-End Testing Patterns
Learn practical, tool-agnostic patterns—synchronisation, test isolation, contracts, and observability—to stop flaky UI tests in CI. Designed for UK automation teams, with actionable guidance you can apply today.
Free IT Training Consultation
Use the calendar to book your free one-to-one course advice session with a Codionix IT training expert. Get personalized career guidance to help you choose the best online IT course in the UK for your goals. We’re happy to answer any questions you may have and help you determine which of our training programs best fit your needs.
How it works?
You schedule a call at your convenience
We do a free discovery and consulting meeting
We guide you towards the best career path for you
Your benefits:
- Personal Guidance
- Course Clarity
- Career Focus
- Honest Advice
- Stress-Free
- Clear Direction




































































