accessibility-auditlisted

# Accessibility audit ## Step 1: identify the input Determine what was actually provided before checking anything: - **A screenshot or image** - proceed with screenshot-only scope (see Step 3). - **A URL** - fetch the page if a fetch tool is available, and use the rendered HTML as the source of truth. If a screenshot of the page is also available, use both. If no fetch tool is available, ask the user to paste the page's HTML instead of guessing at markup. - **HTML, JSX, or another markup/component snippet** - read it directly as the source of truth. - **Anything else** (a plain description, a Figma link with no exported image, a vague "check our app") - stop and ask for a screenshot, URL, or markup. Do not guess at a UI you cannot see. If more than one input type is given (for example a URL plus a screenshot of one of its states), use both and check against the wider scope. ## Step 2: read the checklist Before evaluating anything, read `references/wcag22-checklist.md`. It lists all 18 success criteria this audit checks, one line each: SC number, name, level, whether a screenshot alone can verify it, and what to look for. Re-read it on every audit, even a second one in the same session, so criteria don't quietly drop out of memory. ## Criteria this audit covers | SC | Name | Level | |---|---|---| | 1.1.1 | Non-text content | A | | 1.3.1 | Info and relationships | A | | 1.4.3 | Contrast minimum | AA | | 1.4.4 | Resize text | AA | | 1.4.10 | Reflow | AA | | 1.4.11 | Non-