How we use Accessibility
Auditor on squiz.net

Accessibility compliance on a large site is one of those things that never feels done. You fix a batch of issues, publish new content, and new issues creep in. Most teams deal with that through periodic audits that are expensive, slow, and often out of date the moment they're finished. But at Squiz, we run Squiz Content Intelligence on our site every month.

It scans automatically and serves up a fresh, prioritized list of issues. Our developer and I saw the latest scan results in the accessibility auditor, and he just started working through them. So this is what he saw. First, a prioritized list of suggested fixes ranked by impact. You can filter by type, code changes, content changes, so different people on the team can focus on what's relevant to them.

He filtered to code fixes and started from the top. Each fix shows you what's wrong, why it matters, and gives you an AI-generated suggestion for how to fix it. He reviewed the suggestion, opened the template in our CMS, and applied the fix. No back and forth, no guessing. But the real proof is right down here.

This is the detailed issue view. Every accessibility issue across the site filtered and categorized. Let's filter to just the critical and serious issues. And look, he's resolved virtually all of them just by working through that suggested fixes list. We didn't need an external audit or a six-week remediation project.

Content Intelligence told him exactly what to fix and how, and the critical issues are handled. And because these scans run automatically every month, this is just how we work now. New content goes live, the next scan picks it up. Anything that needs attention and the team acts on it. Even I can jump in and help.

Accessibility isn't a periodic project to run. It's just a natural part of our workflow now.