cypher
there is no spoon.

How do you check accessibility before launch?

Combine automated scans with checks a person does. Run a tool such as axe or Lighthouse on every template, then use the site with a keyboard alone, try a screen reader, check color contrast and zoom, and review alt text and headings. Automated tools find only some problems, so the manual checks matter.

Updated

Know the target

Most organizations aim for the Web Content Accessibility Guidelines (WCAG) at level AA. WCAG has three levels, A, AA and AAA, and each version adds to the last. Legal requirements differ by country and sector, so confirm which apply to you.

Automated checks

  • Run axe or Lighthouse on every template and component, not just the homepage.
  • Fix problems in the component, so the fix reaches every page that uses it.
  • Re-run the checks after every significant change.

Checks a person does

  1. Keyboard onlyReach and use every link, button, menu and form without a mouse, with a visible focus outline.
  2. Screen readerListen to key pages and check they make sense in order.
  3. ZoomEnlarge text to 200% and check nothing breaks or disappears.
  4. ContrastCheck text and controls stand out from their background.
  5. FormsEvery field has a label, and errors say what went wrong and how to fix it.
  6. Motion and mediaMoving content can be paused, and video has captions.

Content checks

  • Images have alt text that describes their purpose.
  • Headings run in order and describe the section below them.
  • Link text makes sense on its own: no “click here”.
  • Documents such as PDFs are accessible too, or offered another way.

How Cypher handles this

The optimization playbook runs Lighthouse and axe on every representative page, and accessibility is part of the definition of done for every build. The reports come with the handover, page by page.

Questions people ask

Is an automated score of 100 enough?

No. It means the automated rules passed. Problems such as confusing focus order or unhelpful alt text need a person to find them.

Who should test with a screen reader?

Ideally people who use one every day. If that isn’t possible, a team member who has learned the basics can still catch many problems.

Do PDFs and documents count?

Yes. If they’re part of the site, they need to be accessible or available in an accessible format.

See it on your site. Thirty minutes, no slides.Book a demo