Frequently asked questions
Does an agent readiness check replace an accessibility audit?
No. Raw HTML can reveal controls that appear to lack names. Keyboard behavior, dialogs and the rendered accessibility tree require browser testing.
Use the Agent Readiness Checker to inspect native HTML controls, labels and semantic signals before a rendered accessibility audit.
A successful fetch from AI Crawl Score means our generic client received a response. It does not establish how a verified crawler will be treated by your server or CDN. The crawler matrix interprets the page’s robots rules; it does not claim to observe real crawler visits.
Check failed findings first, then examine unknown or untested signals. Open each finding for its weight, evidence and recommended action. Keep deliberate exclusions intact on pages that should remain private or undiscoverable.
No. Raw HTML can reveal controls that appear to lack names. Keyboard behavior, dialogs and the rendered accessibility tree require browser testing.
Source records reviewed . Operator documentation defines crawler behavior; the report describes our observations.