ADA Title II Keyboard Accessibility
The U.S. Department of Justice's ADA Title II web and mobile accessibility rule requires covered state and local government web content and mobile apps to conform to WCAG 2.1 Level AA. The rule covers content a public entity provides directly and content made available through contractual, licensing, or other arrangements.
DOJ extended the compliance dates in April 2026:
| Public entity | Compliance date |
|---|---|
| Population of 50,000 or more | April 26, 2027 |
| Population under 50,000 and every special district government | April 26, 2028 |
Read the DOJ Title II web rule overview and the 2026 Interim Final Rule extending the dates.
The keyboard requirement
WCAG 2.1.1 requires every function in a digital process to be operable through a keyboard interface. OpenKeyNav gives implementation teams reusable keyboard routes to detected actions, navigation targets, and configured movement outcomes:
- Click Mode provides direct keyboard selection for detected targets.
- Move Mode maps keyboard selection to application-defined sources and destinations.
- Navigation commands create direct routes through headings, scrollable regions, and page structure.
- Focused diagnostics identify actions for manual review of semantics, focus, activation, and task completion.
Implementation workflow
1. Inventory complete processes
List the services, programs, and activities delivered through each website or web app. Within every process, identify pointer actions, state changes, drag-and-drop operations, validation paths, errors, and completion outcomes.
2. Initialize OpenKeyNav across the experience
Install one instance at the persistent site or application root. Provide a visible explanation or control so users can discover the keyboard operation layer and its on/off command.
3. Verify detected actions
Exercise Click Mode in every relevant page state. Record which actions receive labels and whether label selection focuses or activates the intended target.
4. Configure specialized workflows
Map valid sources, destinations, callbacks, status feedback, and focus outcomes for movement workflows. Add application-specific keyboard routes for functionality outside OpenKeyNav's discovery and movement model.
5. Validate the complete result
Test action coverage, semantics, accessible names, roles, values, states, logical focus, visible focus, mode exits, shortcut conflicts, and programmatic feedback. Include supported assistive technologies and disabled keyboard users.
6. Preserve evidence
Maintain a workflow inventory, configuration record, browser and assistive-technology matrix, issue log, remediation decisions, and task-based user-test results. Retest after releases that change interactions or content delivery.
For vendors and platform teams
The Title II rule reaches web content and apps delivered for public entities through vendor arrangements. Agencies, SaaS providers, CMS implementers, design-system teams, and digital-service contractors can use a shared OpenKeyNav integration to standardize keyboard paths across deployments while preserving application-specific configuration.
Conformance scope
OpenKeyNav addresses a defined part of the implementation: keyboard operation for detected and configured functionality. WCAG 2.1 Level AA evaluation covers every applicable success criterion across complete pages and processes. Public entities determine their legal obligations with their accessibility, procurement, and legal teams.