R18.3: Keyboard navigation accessibility

Short answer: Interactive elements focusable via Tab and Enter/Space. If a control cannot be reached with the keyboard, some people cannot use it.

Group: Accessibility (WCAG 2.1 AA). Status: stable. Generated from the rule definitions; do not edit by hand.

Playground: https://brevio.pro/tools/agent-guard-playground?rule=R18.3

What it catches

Keyboard navigation accessibility: interactive elements focusable via Tab and Enter/Space.

Why

If a control cannot be reached with the keyboard, some people cannot use it.

A bad example

<div onClick={open}>Open</div>

A good example

<button onClick={open}>Open</button>

How it is checked

• Nothing yet. No scanner and no slice card checks it: it is a standing rule for authors and reviewers.

How to silence it

A person can silence one finding with brevio-core: ignore R18.3 -- reason on the line or the line above. Without the reason it does not count. An agent cannot silence it: the agent hook and the MCP tools never honour the comment, and a pull request that adds one is reported until a reviewer allows it. Fixing the code is still the better answer.

To change what the rule flags, edit its definition in dev_rules.py or code_rules/__init__.py. That is a code change and is reviewed like one.

Related rules

• R18.4 Contrast ratio minimum
• R18.5 No click handlers on non-interactive elements
• R18.6 Aria attributes validity
• R18.7 Visible focus rings
• Every rule