Accessibility Statement

A11yPath teaches accessibility, so we hold the site to the standard we teach. We target WCAG 2.2 Level AA across every page, in both light and dark themes, with manual and automated checks gating every release. The scorecard below is our current proof.

Known limitations

Some pattern pages include deliberate anti-pattern demos — broken click handlers, missing labels, low-contrast text — to show what not to ship. Those examples are clearly labeled (“Don’t”) and isolated from the accessible implementation on the same page. They’re intentional teaching tools, not site bugs.

Report an issue

If you hit an accessibility barrier on A11yPath, please tell us through GitHub Issues. Helpful details:

  • the page URL where it happened
  • a brief description of the problem
  • the assistive technology, browser, or OS in use
  • the expected behavior versus what you saw

We aim to respond within five business days.

// audited 2026-06-07

How this site measures up

We hold A11yPath to the standard we teach. These figures come from our own build pipeline — the structural audit and link check that gate every release — plus manual keyboard and screen-reader passes. The site is 23 patterns, 14 guides, and 10 checklists, all held to the same bar.

  • AA WCAG 2.2 conformance
  • 55/55 pages pass our structural audit
  • 0 broken links, of 1,916 checked
  • AA color contrast — light & dark
  • 100 Lighthouse accessibility
  • 0 axe-core violations

What we check, on every page

  • exactly one <h1> per page
  • lang attribute on every page
  • a skip link to main content
  • landmark regions (<header>, <nav>, <main>, <footer>)
  • accessible names on every button, link, and input
  • alt text on images; aria-hidden on decorative SVGs
  • no <div onclick> click handlers
  • :focus-visible indicators (never a bare removed outline)
  • a canonical URL, Open Graph tags, and Schema.org structured data

Our commitments

  • Keyboard operable. Every interaction works without a mouse, with a visible :focus-visible indicator on each control.
  • Native HTML first. We reach for ARIA only where the platform leaves a genuine gap — the approach the whole site teaches.
  • Reduced motion. Animations and transitions are wrapped in prefers-reduced-motion and disabled when you ask for less motion.
  • Light & dark, both AA. Text and UI meet WCAG AA contrast (4.5:1 / 3:1) in both themes — verified down to the smallest mono labels.
  • Resilient. Core content and navigation work without JavaScript; many patterns (disclosure, accordion, breadcrumb) use zero JS at all.
  • Cookieless. Privacy-first analytics — no cookies, no tracking, no consent wall.

Automated checks catch only part of the picture — roughly a third of real issues. We verify the rest by hand, using our own accessibility testing checklist, screen-reader testing guide, and automated testing guide. The Lighthouse and axe scores above come from a Lighthouse 13.0.2 / axe-core 4.11.0 pass on a representative page.