DR-014behavioral

Rule of Access

Essential interactions do not require a pointer.

Markdown · Rule index (JSON)

Requirement

Essential information and actions must be available through the supported input methods, including keyboard operation where applicable. Preserve predictable focus, a visible focus indication, and a usable route into and out of interactive disclosures. Do not make essential information hover-only.

Why

WCAG 2.1.1 addresses keyboard operation, including its path-dependent-input exception. WCAG 1.4.13 sets applicable dismissibility, hoverability, and persistence requirements; WCAG 2.4.11 addresses focused controls being entirely obscured by authored content.

Application

Provide deliberate keyboard chart inspection or an equivalent accessible data view. Use native buttons for disclosures. Make opening, activation, dismissal, and the next focus destination work without a mouse.

Exception

A genuinely path-dependent interaction may fall within the standard's exception; do not use that to exclude unrelated controls or essential data. A touch interface may expose information differently while preserving access to the task.

Review

Perform a real keyboard sequence; programmatically focusing a control does not demonstrate that Tab can reach it. Static axe results do not establish complete keyboard, touch, screen-reader, or focus-visibility behavior.

Examples

The pair isolates this rule. A good example is not approval of the entire interface.

Good for this task

Bad for this task

Review notes and sources

What this example establishes

Other valid choices

Exception

Sources and scope

    Enforcement

    behavioral is the strongest mechanism Viewrule expects for the complete rule. Partial checks can still provide supporting evidence without proving the whole requirement.

    Detection and enforcement details →