Review Issues And Screenshots

The issue page groups audit results by rule. It loads the issue list first and loads occurrence details only when you expand an issue, so large scans do not block the initial page load.

Triage issue groups

1. Open Issues from a scan.
2. Start with critical and serious failures.
3. Check the occurrence count before expanding a group.
4. Expand one issue group when you need selectors, HTML, screenshots, and affected URLs.
5. Use issue-specific exports when one issue group is large enough to review separately.

Expand an issue

When you expand a card, LIME loads the details for that issue group. The expanded view includes affected URLs, CSS selectors, HTML snippets, screenshot evidence, ACT guidance where available, and occurrence paging.

Needs-review checks

Needs-review items are included in the UI and reports. These are axe incomplete outcomes that need human judgment instead of automatic failure. Review them alongside failures when you are preparing an accessibility remediation backlog.

Mark false positives

1. Expand or inspect the issue group enough to confirm the finding.
2. Use Mark false positive only when the issue should be excluded from scoring.
3. LIME keeps the issue visible for audit history.
4. Score summaries update after the false-positive state changes.