The a11y overlay lights up. Someone screenshots the red outlines, drops the PNG into chat, and asks the agent to “fix accessibility.” The model apologizes, rewrites a random div into a button , and misses the actual label association three lines down.
Screenshots are great for humans scanning a page. They’re a lossy encoding for agents. What the model needs is the structured report : rule id, file or selector, message, severity.
I’ve stopped pasting red-outline photography as the primary repro. I paste lint / axe JSON (or a trimmed slice of it) and point at the rule I care about.
Two different JSON shapes (don’t mix them up)
ESLint + eslint-plugin-jsx-a11y is a static pass over JSX/TSX. Run something like eslint -f json path/to/file.tsx and you get an array of file results with messages[] : ruleId , line , column , message , severity . That JSON points at source .
axe-core (Storybook a11y, Playwright @axe-core/playwright , browser extensions) is a runtime pass over the rendered DOM.…