Manual Testing Workflows

Manual testing reveals real usability problems — interfaces should be experienced as users experience them.

01 — Purpose

Experience interfaces like users do

Manual testing reveals real usability problems — interfaces should be experienced as users experience them.

Automated scanners catch missing alt text and colour contrast failures. They miss confusing focus order, silent dynamic updates, and flows that technically pass but feel broken in practice. Manual testing closes that gap.

Pair with the accessibility QA checklist and screen reader testing before release.

02 — Principles

Real interaction reveals real problems

Catches real-world issues, improves usability awareness, and strengthens release quality.

  • keyboard testing — Tab, Shift+Tab, Enter, Space, Escape on every critical path
  • zoom testing — 200% and 400% browser zoom; see zoom and reflow
  • screen reader checks — at least one journey with NVDA or VoiceOver
  • mobile testing — real device or emulator with touch, not desktop-only

03 — Practice

A practical manual workflow

Repeatable steps beat ad-hoc “looks fine to me” reviews.

  • define critical journeys — sign-in, checkout, search, settings — test each release
  • run keyboard-only pass first — note focus loss, traps, invisible controls
  • run screen reader pass on same journeys — see screen reader testing
  • test touch targets on mobile — see touch target standards
  • log issues with steps to reproduce — same discipline as functional bugs

04 — Avoid

Testing theatre

Automation-only QA and visual-only review miss most interaction failures.

  • automation-only QA — axe green, product still unusable with keyboard
  • desktop-only assumptions — no touch, no zoom, no small viewport
  • visual-only review — “looks accessible” without operating controls
  • testing only happy path — errors, empty states, and loading matter too
  • one-off audits with no regression pass before ship

05 — Close

Make manual testing routine

Accessibility confidence requires real testing — not checklist theatre.

Block release on critical journey failures. Rotate who runs manual passes so the team builds shared intuition, not one specialist gate.

See screen reader testing, keyboard navigation, and accessibility QA checklist.