How we test
Last updated November 2026
We test websites the way people use them: with a keyboard, screen readers, zoomed-in screens, and automated checks. A person confirms every issue we report, we retest every fix, and our founder reviews every report before it reaches you.
The standard
We test against the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA, published by the World Wide Web Consortium (W3C).
- It covers WCAG 2.1 AA. WCAG 2.2 keeps the 2.1 rules, adds six new ones at Level A and AA, and drops one outdated rule about code parsing. A website that meets 2.2 AA also meets 2.1 AA, the version many settlements refer to.
- New 2.2 rules are tagged. In your report, findings that fall only under the rules new in 2.2 are marked "2.2 only," so you and your attorney can see which issues 2.1 covers.
Who we test for
Every check stands in for a real person trying to use your website:
- Someone who uses a keyboard instead of a mouse, because of a motor disability, a tremor, or an injury, and needs to reach every link, menu, and button.
- Someone who is blind, who hears your pages read aloud by a screen reader and needs images, buttons, and forms labeled clearly.
- Someone with low vision, who zooms in and needs text and controls that stay readable and high-contrast.
- Someone who is deaf or hard of hearing, who needs captions on videos.
- Someone with a cognitive disability, or an older visitor, who needs clear instructions, forgiving forms, enough time, and buttons big enough to tap the first time.
What we test
Before we start, we agree in writing on the pages and tasks we'll test. We base the sample on the W3C's evaluation method (WCAG-EM): each kind of page on your website, plus the main tasks people come to do, tested from start to finish, because a barrier at any step blocks the whole task.
- Every website: the home page, main navigation, header and footer, a typical content page, search, and contact or quote forms
- Online stores: category pages with filters and sorting, product pages with options and images, the cart, the path into checkout, and account sign-in
- Service, professional, and software websites: booking and scheduling, sign-up and login, and key account pages
Pages behind a login are included when we agree on them and you give us a test account without real customer data. Some parts of a website belong to someone else, such as Shopify's checkout or an embedded booking, review, or chat tool. We test how your website gets people there and document what we find inside, but changes there are up to the provider.
How we test, step by step
- Automated checks. We run tools such as axe and WAVE on each page to catch common problems quickly. Automated tools find only some issues, so this is where we start, not where we stop.
- Keyboard only. We go through every page and task without a mouse, checking that everything can be reached and used, that the focus is always visible and never hidden behind a sticky header or pop-up, and that nothing traps the keyboard.
- Screen readers. We use NVDA with Chrome on Windows, and VoiceOver with Safari on Mac and iPhone, to check that images, buttons, forms, menus, and pop-ups are announced clearly.
- Zoom and small screens. We check pages at 200% and 400% zoom and on a narrow phone screen, so nothing gets cut off, overlaps, or needs sideways scrolling.
- Color and contrast. We measure text, buttons, icons, and focus outlines against the WCAG minimums: 4.5:1 for regular text, and 3:1 for large text and controls.
- Touch and pointer. We check that buttons and links are big enough to tap (at least 24 by 24 pixels, or spaced well apart), and that anything you drag also works with a simple tap or click.
- Forms and errors. We check that labels, instructions, and error messages are clear and announced, that people aren't asked to enter the same information twice, and that signing in works with a password manager or copy and paste, with no memory test or puzzle.
- Content. We check image descriptions, headings, link text, page titles, and video captions, and that help links stay in the same place on every page.
- Motion and timing. We check carousels, pop-ups, videos, and animations for pause controls, time limits, and flashing.
We may use AI coding tools to help read code and draft fixes. A person on our team checks every result by hand, and we never share passwords, access keys, or customer data with these tools. Our privacy policy explains how.
What you get
A written audit report. Each finding includes:
- Where it happens: the page and the exact element
- What goes wrong, in plain words, and who it affects
- How to reproduce it, step by step, with a screenshot of your website
- The WCAG success criterion it relates to, tagged "2.2 only" when that applies
- Severity: Blocker (stops someone from finishing a task), Serious (makes a task very hard), Moderate (makes a task harder than it should be), or Minor (an annoyance)
- Source: your code (we fix it), a third-party app or plugin (we give you the evidence its developer needs), or your content (images, text, or links your team can update)
- The recommended fix
When we fix the issues too, you also get a dated remediation log of every change and a retest report with each finding's result.
How we fix
- Limited access. You add us through your platform's normal collaborator or staff access, limited to code and content. We never need your password or any customer or payment data. You can remove our access at any time, and it's removed when the project ends.
- A copy first. When your platform allows it, we work on a staging site or a duplicate theme, never your live site. When it doesn't, we agree with you in writing on when and how each change goes live.
- Clean code. We write the fixes ourselves, or use open-source code whose license allows it, and we record the source in the remediation log.
- Retested by hand. We retest every fix with the same methods we used to find it, and record the date and the result.
- You stay in control. You review the changes, then publish them when you're ready.
What we don't do
- No overlays or widgets. We don't add accessibility toolbars or overlay scripts. We fix the underlying code.
- No legal advice. Our reports are technical reviews, not legal opinions. If you have an attorney, we work alongside them.
- No certificates or guarantees. No one can honestly certify a website as "compliant" or promise that you won't be sued. Websites change with every update, plugin, and new page, and so does their accessibility.
Keeping it accessible
Updates, new plugins, and new content can bring problems back. With monthly monitoring, we recheck your key pages, tell you when something breaks, and keep a dated record, including through a settlement period.
See what's blocking your visitors
Start with a free review of three key pages. It uses only your public website, so we don't need any access. Questions about how we test? Email contact@clearaccessfix.com.
Request a free review