Carla G.

The strict final A11Y Cat Chrome Web Store submission prompt I use to test the MV3 extension package, scanner trust, privacy, documentation, UI, and release process…

What I learned while debugging an accessibility scanner with AI agents, and why evidence matters more than pass/fail theatre.

A practical look at WAVE API, axe-core, Playwright, Pa11y, IBM Equal Access, and why a local scanner is the more honest foundation for A11Y CAT.

Why I built Cat Crawler, what it is good at, what it taught me, and the improvements I would make next.

What it takes to use agents without letting the work slip into vague claims, fake certainty, or sloppy release habits.

A look at the way people are talking about WordPress and AI, and why accessibility still gets flattened or ignored in that conversation.

A plain account of where the project stands now, what it can actually prove, and where the limits still are.

Why the project started leaning harder on rules, release discipline, and explicit boundaries instead of good intentions.

Packaging, release handoff, and build cleanup stopped being side work once the project got big enough to ship properly.

This was probably inevitable. The only question was whether I was going to admit it early enough. By mid-April, A11Y Cat’s runtime had become too large…