♿

AccessDojo

Every screen you build is used by someone who can’t see it. Learn to hear your own app.

🔮 Open the audit console →

Accessibility is not opinion — it’s an audit you can run

A screen reader turns your interface into a stream of spoken lines. If a button is just an icon with no label, it says “button” and the user is lost. If text is too faint, low-vision readers can’t make it out. If headings skip a level, the outline breaks. AccessDojo runs the exact checks a professional auditor runs — on synthetic screens, right on your device — so you learn to hear your own code.

  1. Read. Here is a screen, written as code — buttons, images, headings, text.
  2. Predict. What does VoiceOver announce? How many problems will the auditor find?
  3. Reveal. See every WCAG finding — missing name, low contrast, skipped heading — with the fix.
  4. Fix. Patch the screen in the Fix-it lab and watch the problem count fall to zero.

Everything runs on your device — no internet, no accounts.

The four rules you’ll master

  • Name it. Every control needs an accessible name — an icon is invisible to a screen reader (WCAG 1.1.1 / 4.1.2).
  • Contrast it. Normal text needs 4.5:1, large text 3:1 — anything less fails AA (WCAG 1.4.3).
  • Structure it. Headings are the outline; never skip a level, h1 → h2 → h3 (WCAG 1.3.1 / 2.4.6).
  • Quiet the decoration. A purely decorative image gets an empty alt so the reader skips it.

AccessDojo is text-forward (ages 15–18) — the rules themselves are the cast.