Ignore system
Suppress false positives with inline comments or the ignore subcommand.
Every a11y tool has false positives. Equall lets you suppress them via comments directly in the source, so the suppression lives with the code, not in a separate config.
Inline: ignore a single line
Add a comment on the line immediately above the offending element:
{/* equall-ignore-next-line */}
<div onClick={handler}>Click me</div>All issues on the next line are ignored.
Inline: ignore a specific rule
Add the rule ID after equall-ignore-next-line:
{/* equall-ignore-next-line jsx-a11y/click-events-have-key-events */}
<div onClick={handler}>Click me</div>Only that rule is suppressed — other issues on the same line still surface.
File-level ignore
Add a comment in the first 5 lines of the file to suppress every issue in it:
// equall-ignore-fileUseful for generated code or vendored files.
Managing ignores with the CLI
equall ignore --list # list all ignores in the project
equall ignore src/Modal.tsx:89 # add ignore at file:line
equall ignore src/Modal.tsx:89 jsx-a11y/alt-text # scope to a rule
equall ignore src/generated.tsx # file-level ignore
equall ignore --remove src/Modal.tsx:89 # remove a specific ignore
equall ignore --clear # remove every ignore in the project
equall ignore --list --path ./apps/web # run against another project rootHow ignored issues appear in output
Ignored issues are excluded from the score, the violation counts and the verdicts, but never hidden. The terminal Summary states how many were suppressed (N issues suppressed via equall-ignore); pass --show-ignored to list them, each with a ⊘ marker. --json includes them with ignored: true, and each criterion's verdict carries accepted_exceptions — the number of suppressed issues on it — so the JSON never presents a criterion with suppressed findings as a bare pass (see Output format).
When NOT to ignore
An ignore comment is a statement that you've considered the issue and decided it's a false positive. Use it when:
- The rule is structurally wrong for your component (e.g. a button styled as a link)
- The issue requires runtime context the scanner can't see (e.g. ARIA labels coming from an upstream library)
Do not use it to silence issues you haven't understood. A review of your ignore list is a valid pre-release check.