Skip to content
certyn logoCertyn
Start Free
RecipesDoc

Accessibility Check of Your Key Pages

Certyn runs an automatic WCAG 2.2 AA audit on your main pages, checks keyboard and focus by hand, and files grouped issues.

For teams who want to know where their web app fails WCAG, and what to fix first.

Your setup

  • A web app on staging, with a test account.
  • A few key pages: sign-in, sign-up, checkout, settings.
  • You want the main accessibility problems found, with the elements that fail.

Say this to Certyn

Check accessibility of our sign-in, checkout and account settings pages on staging and file what blocks keyboard or screen reader users.

What Certyn does

  1. Says the run length and starts an explore run with your pages as the goal (app.run.create type explore). For a single page, it can check it on the chat's Machine while you watch.
  2. In the run, on each page, Certyn runs an automatic audit (browser.a11y.check): axe-core with the WCAG rules up to 2.2 AA. It lists failures by impact, with the elements and the measured contrast.
  3. Reads the accessibility tree (browser.a11y.get): the names and roles a screen reader would announce.
  4. Checks by hand what the audit cannot: reaching every control with Tab, Shift+Tab, Enter, Space, Escape and arrow keys; visible focus; focus in and out of dialogs; 200% zoom and a narrow screen.
  5. Files issues with the element, what fails, who it blocks, and the WCAG point (for example 1.4.3 for contrast). Many elements failing the same rule make one issue with a count and examples.

What you get

  • Issues ranked by harm: a main task a keyboard or screen reader user cannot finish is Major; one low-contrast label is Minor.
  • A run report with each page checked and what was not checked.
  • If you ask: test cases tagged a11y for these pages and a suite that runs them on a schedule.

Limits

  • Automatic rules find only part of the problems. Certyn adds keyboard and focus checks, but it does not use a real screen reader (NVDA, JAWS, VoiceOver). Test key flows with one, and with real users, before you claim compliance.
  • This is not a formal audit or a conformance report (such as a VPAT).
  • Web pages only. Mobile and desktop apps get no automatic audit.
  • The audit marks some items for manual review because it cannot decide, such as text over an image. Ask Certyn to list them, and check them yourself.
PreviousTest Your API from Its OpenAPI SpecNextPerformance Check of a Slow Page