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.7: Visible focus rings

Short answer: Interactive elements retain visible focus outline for keyboard users. People who use a keyboard need to see where the focus is.

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

What it catches

Visible focus rings: interactive elements retain visible focus outline for keyboard users.

Why

People who use a keyboard need to see where the focus is.

A bad example

button:focus { outline: none; }

A good example

button:focus-visible { outline: 2px solid #1a73e8; }

How it is checked

How to silence it

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