brevio-core

Catches the mistakes coding agents repeat before they merge: a pull-request gate with no model call and no API key.

View the Project on GitHub Brevio-Ventures/brevio-core

R18.5: No click handlers on non-interactive elements

Short answer: Divs/spans with onClick specify role=’button’. A div with a click handler is not a button for the keyboard or a screen reader.

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.5

What it catches

No click handlers on non-interactive elements: divs/spans with onClick specify role=’button’.

Why

A div with a click handler is not a button for the keyboard or a screen reader.

A bad example

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

A good example

<div onClick={open} role="button" tabIndex={0}>Open</div>

How it is checked

How to silence it

A person can silence one finding with brevio-core: ignore R18.5 -- 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.

What the scanner already leaves alone: A div with role= after its onClick on the same line is not flagged.

A scan reads only the lines you add, so a line that was already in the file is not flagged.

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.