A11y Equitas

A11y Equitas = accessibility as equity. An open, US-government-and-nonprofit-focused AI assistant for WCAG 2.2 AAA compliance under the DOJ Title II rule — with practical guidance so neurodivergent users (ADHD, dyslexia, attention/memory differences) and everyone else can actually use the services public agencies and their vendors deliver.

Every page on this site is verified by Playwright + axe-core + Alfa before deploy, and the markup follows WCAG 2.2 AAA — built with Next.js, one of the most popular React frameworks.

What the model does (AAA goals)

  • Distinguishes the legally enforceable WCAG 2.2 AA baseline from aspirational 2.2 AAA, and cites each success criterion by number and level.
  • Navigates DOJ Title II (28 CFR Part 35) and U.S. state mandates — Washington WaTech Policy USER-01 (formerly OCIO Policy 188), Oregon ADA Title II program (Oregon EIS / ODOT), California AB 434 and the Unruh Civil Rights Act.
  • Writes runnable Playwright + @axe-core/playwright + Alfa test specs and Python scripts that turn results into accessible reports.
  • Guides human-in-the-loop manual testing with Microsoft Accessibility Insights for Web (FastPass vs Assessment).
  • Explains the human impact of each requirement — including for neurodivergent users.
  • Covers Section 508 and the Rehabilitation Act for federal agencies and their contractors — including the ICT refresh (36 CFR Part 1194).
  • Generates correct ARIA authoring patterns for complex widgets: menus, dialogs, tabs, accordions, carousels, live regions, and custom form controls.
  • Verifies color contrast ratios, recommends WCAG-compliant palette adjustments, and explains which token changes fix a violation without breaking brand identity.
  • Produces accessible form markup — labels, error messages, grouping, autocomplete, and timeout warnings that satisfy SC 1.3.5, 3.3.1, 3.3.2, and 3.3.7.
  • Assists with PDF and document accessibility: tagging order, reading sequence, alt text for figures, and remediation steps for exported Office and print-to-PDF files.
  • Drafts and reviews VPAT / ACR language (WCAG 2.x and Section 508 editions) with honest conformance levels and known-gap disclosures.
  • Applies plain language and readability guidance (SC 3.1.5, Flesch–Kincaid Grade 8 target) to draft and simplify public-facing content.

How-to guides

Each guide explains a specific accessibility topic — with live examples, code patterns, and plain-language explanations for neurodivergent users and screen reader users.

  • Accessible PDFs— PDF/UA + WCAG 2.2 AA, the DOJ stance on “separate but equal,” and when HTML is the right answer.
  • Accessible tables — captions, scope, headers, and responsive design for data tables that work with every screen reader.
  • Accessible charts and maps — live Chart.js bar and doughnut charts with data tables, and an OpenStreetMap showing neurodivergent population density across WA, OR, and CA.
  • Accessible images — alt text patterns for every image type, SVG best practices, and the WCAG AAA image requirements.
  • Accessible videos — captions, audio descriptions, transcripts, and accessible player controls for WCAG 2.2 AAA compliance.
  • Accessible tech stack — why Next.js, Tailwind, Playwright, and Alfa work together for WCAG compliance at every layer.
Design system
Tailwind, not Bootstrap

Why utility-first CSS produces more accessible, WCAG-compliant interfaces than component-first frameworks.

Workplace inclusion
Reasonable accommodations for neurodivergence

WCAG 2.2 AAA compliance is the floor, not the ceiling. How to support ADHD, autistic, and dyslexic colleagues without requiring prescriber documentation.

Accessible components

Live interactive demos — every component meets WCAG 2.2 AAA.

ARIA disclosure
Accessible accordions

Keyboard-navigable expand/collapse panels with correct aria-expanded and focus management.

Roving tabindex
Accessible tabs

Tab panels with keyboard arrow navigation, aria-selected, and both auto and manual activation.

Native + ARIA
Accessible dropdowns

When to use native select and when to build a custom combobox — with full keyboard support.

HTML + CSS
More components

Alerts, breadcrumbs, cards, sidebars, hero, menus, and text areas — copy-paste recipes.