See your page the way an AI agent does.
AI agents do not look at your design. They read the accessibility tree, the structural version of your page made of headings, roles, labels, link text and alt text. A page can look perfect to a human and be close to unreadable to an agent. This checks the same tree an assistant walks, tells you exactly what is missing, and shows you the outline it sees. It runs entirely in your browser, no API key, nothing sent to us.
Structure an agent can follow, or gobbledygook.
Open the page you want to check, view its source (right-click → View Page Source, or Ctrl/Cmd + U), select all, copy, and paste it below. Browsers block reading another site’s HTML directly, so pasting is what keeps this free and private, the markup is parsed on your own device and never leaves it.
Parsed entirely in your browser, nothing is uploaded, logged, or stored. This checks structure, which is what agents and screen readers consume; it is not a full WCAG audit and does not measure colour contrast or keyboard order. Want this fixed for you? Talk to us.
Questions, answered.
It is the structural version of your page the browser builds from your HTML: headings, roles, labels, link text and alt text, with the visual styling stripped away. Assistive technology has always used it, and AI agents that browse read the same structure rather than the rendered pixels. If that tree is vague, the agent's understanding of your page is vague.
No, and be wary of anyone who promises that. Clear structure makes your content easier for an agent to parse and quote correctly; it does not control whether an engine chooses to cite you. Treat this as removing an obstacle, not as a ranking lever.
Browsers block one site from reading another site's HTML (the same-origin policy), and routing it through our server would mean uploading your page and paying for the fetch. Pasting keeps the tool free, private, and instant, the markup is parsed on your own device and never leaves it.
No, alt="" is the correct way to mark a decorative image, and it tells an agent to skip it. A MISSING alt attribute is the defect, because the agent has to guess. This tool counts the two separately for that reason.
An input wrapped inside a <label> inherits that label's entire text as its accessible name. If the label also contains help text, a link, or a dropdown, the field ends up announced as one long run-on string instead of its actual name. The fix is an explicit aria-label on the input. We found exactly this on our own tool pages.
No. It checks the structural signals an agent consumes, headings, names, labels, landmarks, alt. It does not test colour contrast, keyboard order, focus management, or motion, all of which matter for WCAG compliance. Use it as a readability check, not a compliance certificate.