Scaling agentic A11y with browser-side scans

Fanning out agents to read every component file is a tempting shape for accessibility review. It demos well in a small project. In a real codebase with hundreds of components, multiple routes, and several active branches, it's a budget problem. You're paying LLM rates for work a deterministic audit engine does in JavaScript. The asymmetry is the point. Rule checks against a rendered DOM are deterministic JavaScript, not LLM tokens. The agent's leverage is in the judgment: choosing the right alt