How to run continuous WCAG audits across hundreds of websites
Auditing a large portfolio of websites requires choosing between expensive tools or massive manual resource consumption. This prevents organizations from maintaining continuous compliance across all properties without overwhelming their teams.
What people tried
Every workaround mentioned in the threads below. We haven’t tested any of them — and nobody here is claiming they worked.
Found another way around this?
Share your steps and trade-offs so fellow engineers don't have to reinvent the wheel. No account required.
- 1Using automated testing and scanning tools like WAVE, UserWay, Axe, Lighthouse, and Total validatorDid this help you?
- 2Creating reusable custom blocks audited at creationDid this help you?
- 3Using custom plugins that trigger errors for hard accessibility failuresDid this help you?
- 4Employing overlays like AccessibeDid this help you?
In their words
Unedited, grouped by where they were said, most upvoted first within each place, each linked to the thread it came from.
“We manage around 200 sites, so I’m trying to find a realistic way to continuously check them and stay on top of WCAG issues without manually auditing every site all the time.”source ↗
“For retroatively handling 200 sites, the options are either going to be expensive or resource consuming.”source ↗
Where this came up
People with this problem also raised
- 5Why do website builder tools and admin dashboards keep breaking?
- 2Why does server compliance show non-compliant after updates?
- 4Why are website builders so bloated and fiddly?
- 5Why am I spending more time on WordPress maintenance than publishing?
- 4How to avoid paying $250 a month for routine website maintenance
- 4How to handle tight airport connections with physical disabilities