Step-by-step · Maintenance and Security

How to Check Website Accessibility

An accessibility check should combine automated detection, manual interaction and review of real customer journeys. The aim is to identify barriers and verify fixes, not to produce a single score.

Information checked: 21 July 2026.

An accessibility check should combine automated detection, manual interaction and review of real customer journeys. The aim is to identify barriers and verify fixes, not to produce a single score.

In brief: Combine automation with keyboard, screen-reader and task-based human testing.

Step 1: choose representative pages

  • Home and main navigation.
  • A content article or category.
  • Contact or quote form.
  • Booking, payment or account journey.
  • Policy, download and media page.
  • Error, empty and confirmation states.

Step 2: run manual checks

  1. Navigate and complete tasks using only the keyboard.
  2. Confirm visible focus and logical order.
  3. Zoom text and inspect narrow mobile layout.
  4. Review headings, landmarks, labels and error messages.
  5. Check colour contrast and information conveyed by colour.
  6. Use a screen reader to spot-check navigation, forms and dynamic updates.
  7. Pause, stop or avoid motion where required.

Step 3: use automated tools carefully

How to handle automated findings

Definite code error
Fix and add a regression test
Potential issue requiring context
Review manually in the customer journey
Pass or high score
Continue manual testing; absence of detected errors is not proof
Third-party component issue
Escalate to supplier and provide an alternative where needed

Step 4: retest with users

For important services, involve disabled users or qualified accessibility testers. Record the task, device, assistive technology, issue, severity and evidence of resolution.

Acceptance check

A check is complete only when blocking issues are fixed or mitigated, known limitations are documented and the reporting route has been tested.

Test error and edge states

Accessibility problems often appear only after validation fails, content loads dynamically or a session expires. Include empty results, invalid input, timeout, modal dialogue and confirmation states rather than testing only the ideal page.

Records to keep

  • Page and state sample list.
  • Browser, device and assistive-technology details.
  • Issue evidence and reproduction steps.
  • Retest result and regression case.

Owner test: Deliberately submit an incomplete form with keyboard and screen reader and confirm that the error is announced, specific and easy to correct.

Sources and date checked

This practical guidance was checked against the following primary sources. Date checked: 21 July 2026.

Keep the decision under your control

Retain the relevant accounts, source material, supplier terms and recovery information. Recheck changing prices, interfaces and rules before acting.