For AI agents and LLMs: a machine-readable index is available at llms.txt. A plain-Markdown version of any documentation page is available by appending .md to its URL.
Skip to main content

Issue Summary

Issue Summary gives you the high-level breakdown of a completed Accessibility run before you move into issue-level triage.

Read on for the summary metrics surfaced after each run. Each signal is meant to help you prioritize remediation before you drill into individual issues, so you can align fixes with severity and coverage first.

What you can review​

  • total issues
  • issue types
  • affected element groups
  • best-practice findings
  • needs-review findings
  • affected WCAG guidelines

When to use this​

Use this view when you want to understand report shape and severity before drilling into individual issues.

How to use Issue Summary (onboarding)​

  1. From Navigating the Dashboard, open a completed report.
  2. Select Issue Summary (or the equivalent tab/panel name in the UI).
  3. Read severity totals first. Critical/serious items usually block users or compliance narratives.
  4. Scan guideline or rule groupings to see which WCAG themes dominate (contrast, keyboard, forms, ARIA, etc.).
  5. Use needs-review and best-practice counts to decide how much manual validation you owe before filing engineering tickets.
  6. When a bucket looks actionable, jump to All Issues filtered or grouped by that bucket, or open the Web Rule Repository entry for the rule text.
Last updated on

Terminal First Testing With Kane CLI

Natural language browser & mobile app tests right from terminal.

×
Schedule Your Personal Demo
Kane CLI terminal

Help and Support

Related Articles