Why check more than one page
Most accessibility problems aren't on one page: they're in the parts every page shares. An icon-only menu button without a name, a search box without a label, social icons in the footer with no text, a cookie banner that traps keyboard focus. Fix them once in the theme and every page improves. Checking a sample of pages shows which problems are template-wide and which are one-offs in the content, so the work can be split between the developer and the content team.
The UK accessibility regulations expect testing on a representative sample of pages, and this is a quick way to get the automated part of that done. Follow it with manual testing using a keyboard and a screen reader on the same pages.
Questions agencies ask
Enough to cover every template and type of content: the homepage, a typical content page, a listing page, a product or service page, forms, search results and anything interactive. For most sites that's 10 to 25 pages. The UK government suggests a representative sample rather than every page.
It reads the sitemap, groups the URLs by their first folder (blog, products, services and so on), then takes the homepage and one page from each group in turn until it has 25. That way every section, and usually every template, gets checked. You can edit the list before running it.
The issue appears on at least 70% of the pages checked, which almost always means it's in something shared, like the header, menu, footer or page template. Fixing it once fixes it everywhere.
No. Automated tools find roughly a third of accessibility problems. They're a fast way to clear the obvious issues across a site, but you still need to test with a keyboard and a screen reader, and ideally with disabled users.
Yes. When a bulk check finishes, its issues are saved in your browser, and the accessibility statement generator can import them.
Each page result is cached for 15 minutes so a recheck is quick, then discarded. Nothing else is kept.
Template-wide accessibility fixes?
Theme-level accessibility fixes are where a developer saves the most time: one change to the header, menu or product template fixes hundreds of pages. I do this for agencies on WordPress, WooCommerce and Laravel sites.
- White-label, under your brand, or alongside your team
- Laravel, WordPress, WooCommerce, integrations and tracking
- Inherited and half-finished sites taken over and stabilised
- UK based, straight to the developer, no account managers