Accessibility and agent-readiness are the same work. The tools haven't caught up.
The internet was built for human eyes. Websites use visual layouts, styled divs, and JavaScript-rendered content that humans navigate by sight. Agents don't have eyes. They parse the DOM. When a button is a styled div instead of a button element, an agent cannot find it.
This is not a future problem. Retrieval agents read the web right now. ChatGPT visits URLs. Perplexity reads pages. Google's AI Overviews pull from live sites. They arrive by the million, read your HTML, and form an impression of your page, often without ever running your JavaScript. These retrieval agents are the second audience: a different reader than the human you designed for.
Agentis Lux scans your site and reports what an agent experiences. Six categories of deterministic checks. Findings written from the agent's perspective. No fixes suggested, because suggesting fixes implies we know your codebase, your constraints, and your reasons. We don't. We know what an agent sees.
On accessibility: there's real overlap with WCAG. Semantic HTML, proper labels, ARIA roles, heading hierarchy, structured data: these help screen readers and agents alike. Building for accessibility moves you toward agent-readiness. But agents are their own audience with their own needs, not a subset of the accessibility audience. The overlap is a baseline, not the whole story.