Accessibility and WCAG Support

OpenKeyNav provides keyboard routes to detected targets and configured workflows for implementing WCAG 2.1 Success Criterion 2.1.1: Keyboard. Teams establish coverage by verifying every required action, state, and outcome across complete pages and processes.

A conforming implementation combines OpenKeyNav's operation modes with the host page's semantics, accessible names, state, focus behavior, feedback, instructions, and full workflow coverage.

OpenKeyNav's role in the implementation

Requirement	OpenKeyNav	You
2.1.1 Keyboard	Direct keyboard selection for detected targets and endpoint selection for configured movement workflows.	Every function, state, and outcome has a working keyboard route.
2.1.2 No Keyboard Trap	Escape exits temporary interaction modes; Structural Navigation has a dedicated exit command.	Users can leave every component and mode with the keyboard.
2.1.4 Character Key Shortcuts	A persistent on/off mechanism for OpenKeyNav's character commands and developer-configurable keys.	Users can find and operate the off mechanism; speech input and command conflicts are tested.
2.4.3 Focus Order and 2.4.7 Focus Visible	Real focus movement for navigation and selected targets when the target accepts focus.	Focus remains visible, meaningful, and ready for the next step.
4.1.2 Name, Role, Value	Visual target labels and mode status.	The host page exposes programmatic names, roles, values, and states for assistive technologies.
Endpoint-based movement	Source and destination selection plus an application callback.	The keyboard workflow reproduces the intended outcome and communicates selection, cancellation, errors, and completion.

Interpreting Click Mode diagnostics

The debug heuristic selects actions for focused review of semantics, focus, and activation.

• Click Mode includes each review candidate in its direct-selection labels.
• Each candidate adds a focused checkpoint to the broader WCAG evaluation.
• Record the heuristic's candidate count alongside findings from complete workflow evaluation.
• Include custom widgets, delegated event handlers, dynamic state, covered elements, Shadow DOM, and cross-origin content in the complete workflow evaluation.

For every candidate, verify the target's purpose, programmatic name, role, state, focus behavior, OpenKeyNav activation result, and place in the complete workflow. Native controls remain the clearest way to expose semantics and conventional interaction where they fit the design.

Verification workflow

1. Inventory functionality. List each pointer action, keyboard action, state change, error path, and outcome in the complete process.
2. Assign keyboard paths. Record whether each function uses conventional keyboard behavior, Click Mode, Move Mode, or another application-specific route.
3. Exercise Click Mode. Test target discovery and activation in every relevant state, viewport, route, dialog, and dynamically updated view.
4. Exercise configured workflows. Test source selection, destination selection, cancellation, invalid destinations, errors, completion, and focus after completion.
5. Verify semantics and feedback. Confirm accessible names, roles, values, states, instructions, status messages, logical focus, and visible focus.
6. Test commands together. Check OpenKeyNav keys with text entry, host-application shortcuts, browser and operating-system commands, screen readers, and speech input.
7. Test with disabled users. Include representative keyboard and assistive-technology users alongside standards evaluation.
8. Retest complete processes. Cover responsive layouts, asynchronous changes, validation errors, authentication states, and supported browser combinations.

W3C's Evaluating Web Accessibility Overview describes how automated checks, manual evaluation, and user involvement work together.

ADA Title II

The U.S. Department of Justice's Title II web and mobile rule uses WCAG 2.1 Level AA as the technical standard for state and local governments. The ADA Title II keyboard accessibility guide provides the current dates, covered delivery arrangements, and an OpenKeyNav implementation checklist.