Issue Details

Rule, failure summary, WCAG tags, selector, HTML snippet, and matching targets for a single issue.

Clicking an issue in the list opens the detail panel on the right. Everything you need to diagnose and fix one element is on this panel.

Fields in the panel

Field	What it is
Rule description	Human-readable version of the rule (e.g., "Elements must meet minimum color contrast ratio thresholds").
How to Fix	Axe-core's failure summary — why this specific element failed the rule. The panel labels it How to Fix; the API field is `failure_summary`.
Impact	Critical / Serious / Moderate / Minor. See Severity levels.
WCAG tags	All WCAG tags the rule maps to (e.g., `wcag2aa`, `wcag143`, `cat.color`).
WCAG criterion	The specific success criterion (e.g., `1.4.3 Contrast (Minimum)`).
Target selector	CSS path to the failing element on its page.
HTML snippet	The exact failing markup, syntax-highlighted.
Affected Page	Which scanned URL this issue came from, with a link that opens it in a new tab.
Page snapshot	Loads at the top of the panel with the failing element outlined — for the scan's creator only. See Element inspection.

Fields in the API only

These are stored on every issue and returned by the API, but are not rendered in the detail panel:

Field	What it is
Rule ID	Machine-readable axe-core rule identifier (e.g., `color-contrast`, `image-alt`). Shown as the group heading when the list is grouped by rule.
Category	TestKase's display-name category — `Color`, `Forms`, `Keyboard`, `Structure`, `Text Alternative`, `Aria`, `Time & Media`, `Parsing`, `Language`, `Semantics`, `Tables`, `Name, Role, Value`, `Sensory & Visual Cues`. The All Categories filter on the All Issues tab lists only nine of these.
All matching targets	Every selector on the same page where this rule fires (useful for repeated components).
Bounding box	`{ x, y, width, height }` captured at scan time. Populated for Website Scanner scans only, and always empty for reports saved from the Chrome Toolkit. Nothing in the UI reads it — the snapshot outline is drawn from the CSS selector instead.

Common actions from the detail panel

Copy CSS Selector — one click; paste into DevTools to jump to the element.
Copy HTML snippet — the exact failing markup.
Previous / Next — walk every element in the same rule group without closing the panel (Issue N of M in the header).
Open affected page — opens the live URL in a new tab.
Learn more about this issue — external link to the W3C success-criterion quickref.

There is no per-issue deep link — to point a colleague at one issue, share the scan with their team and describe the rule and selector.

Hiding an issue

An issue can be hidden — excluded from the report and from the score — for the cases where a finding is a false positive or is knowingly out of scope.

Hiding is available through the API only. There is no button in the report:

PATCH /accessibility-scans/{scanId}/issues/{issueId}/hide
{ "hidden": true }

Reports saved from the Chrome Toolkit use the same call on /analyzer-scans/{scanId}/issues/{issueId}/hide. Send "hidden": false to bring the issue back.

Only the scan's creator can hide an issue; anyone else gets 404 Scan not found.

Hiding one issue hides it everywhere:

It disappears from the issue list, the total issue count and the severity breakdown.
It stops contributing to the affected-pages and affected-components tables and to the WCAG conformance matrix — hide the last issue under a criterion and the criterion flips back to No issues found.
It is left out of the PDF, of consolidated reports and of version comparisons.
The score goes up the next time the report is opened, because the score is recalculated on read.

Nothing in the UI tells you an issue is hidden. The Hidden issues counter on the Summary tab and in the PDF is hard-coded to 0, so it stays at zero however many issues you hide. Keep your own record of what you hid and why — a hidden false positive is invisible to the next person who reads the report, and to an auditor.

How to read "failure summary"

The failure summary is axe-core's explanation of why this element failed. Typical phrasings:

"Element has insufficient color contrast of 3.12 (foreground color: #888888, background color: #ffffff, font size: 12.0pt (16px), font weight: normal). Expected contrast ratio of 4.5:1."
"Element does not have an alt attribute."
"Element is in tab order but has no keyboard-accessible name."

Items the checker could not decide read "Needs manual review" instead. They are not listed with the confirmed problems. You find them in the folded To check by hand (N) section at the bottom of the All Issues tab. In Website Scanner reports they still lower the score (Chrome extension reports: they do not) — see Summary & Score.

These messages are copy-paste-ready for bug reports.

Grouping

The issue list can be grouped:

By Rule — all instances of image-alt in one row. Best for fixing repeated components once.
By WCAG — all 1.4.3 Contrast (Minimum) failures together. Best for compliance reporting.

Switch with the segmented By Rule / By WCAG toggle at the top of the issue list.