Up to 70% off kits30% off services
ARIA Validator for AI-Generated Code
Paste any HTML or JSX snippet and get an instant report of invalid ARIA attributes, hallucinated roles, missing names and common AI code generator mistakes. Role and attribute rules come from the ARIA 1.2 data used by axe-core and Testing Library; names follow the W3C accessible name algorithm. Built for v0, Lovable, Bolt and Claude Code output.
HTML input
Validation results
Paste HTML and click Validate to see results.
Shipping a v0, Lovable, Bolt, or Claude Code app?
AI code generators produce these exact ARIA mistakes constantly. Start from a baseline that doesn't make them. The A11y Starter Kit is a free Next.js project with WCAG AA on every component, so you can paste AI-generated code on top without breaking accessibility primitives.
Get the A11y Starter Kit →ARIA is right. Does a screen reader agree?30% OFF
Valid ARIA and correct announcements are different things. We test with NVDA, JAWS, VoiceOver and TalkBack by hand, check focus management and keyboard paths, and hand your developers a report mapped to WCAG criteria with severity and reproduction steps. From $349$499.
Frequently asked questions
Common questions about the ARIA validator.
It checks against ARIA 1.2 (including the DPUB and Graphics roles): invalid and abstract roles, fallback role lists, unknown ARIA attributes, required states for each role, prohibited and unsupported attributes, attribute values (true/false, tokens such as aria-live and aria-current, numbers, ID references), ID references that point at nothing, controls and form fields without an accessible name, aria-hidden on focusable content, redundant roles, clickable divs without keyboard support, and images without alt. Accessible names are computed with the W3C accessible name algorithm, so labels, aria-labelledby and image alt text inside links and buttons all count.
We have audited hundreds of AI-generated React apps. The same ARIA mistakes show up over and over: hallucinated roles like "container" or "label", boolean values like aria-pressed="yes", clickable divs, missing form labels. This validator is tuned to catch these specific patterns alongside the standard spec checks.
Yes. JSX and TSX are parsed with Babel and converted to HTML first, so className, htmlFor and values like aria-pressed={true} are understood. Values computed at runtime ({isOpen}) are not checked, and we cannot see what your own components (<Button>) render, so only their attribute names and literal values are checked.
No. The validator runs entirely in your browser using DOMParser. Nothing is uploaded, logged, or stored.
No. It reads markup, not behaviour: it cannot see CSS, JavaScript state changes, focus management or whether a role matches what the component actually does. For WCAG 2.2 AA you also need contrast checks, keyboard testing, screen reader testing and manual review. Use this as one of several tools.