♿ Accessibility (WCAG) Check
Describe a page/UI or paste its markup and get a heuristic WCAG 2.2 review — each issue tagged with the success criterion, conformance level, who it impacts and a concrete fix.
- Tied to WCAG criteria. Every issue cites the exact success criterion and its A / AA / AAA level.
- Tells you who it hurts. Each finding names the affected users — screen-reader, low-vision, keyboard-only.
- Concrete fixes. Not "improve contrast" — the exact change to make.
See the quality — a real example
Sample only · no credits usedInput — pasted UI / markup
Login form: placeholder-only inputs with no <label>; the "Submit" control is a <div> with an onclick; body text is #999 on #fff; a carousel auto-advances with no pause button.
Output — WCAG issues
- 1.4.3 Contrast (Minimum) · AA — #999 on #fff is 2.85:1, below the 4.5:1 minimum. Hurts low-vision users. Fix: darken body text to ≥ #595959.
- 4.1.2 Name, Role, Value · A — a <div> "Submit" isn't focusable or announced as a button. Hurts keyboard & screen-reader users. Fix: use a real <button type="submit">.
- 3.3.2 Labels or Instructions · A — placeholder-only fields vanish on input and aren't reliably read. Fix: add a persistent <label for>.
- 2.2.2 Pause, Stop, Hide · A — auto-advancing carousel with no control. Fix: add a visible pause/stop button.
Sign in to use this tool
Sign in to use (30 free points on signup). Signed-in users run every tool on their account points — nothing to paste.
Sign in →