Accessibility and WCAG reports

AegisRunner exposes accessibility findings alongside page results and in WCAG reports. Use them to identify issues to investigate and verify fixes.

Review findings

1. Select the scan you want to inspect.
2. Open the page's Accessibility information or WCAG reports.
3. Review the affected element, reported rule, impact, and available evidence.
4. Fix the issue in the application.
5. Scan again and compare the affected pages.

Prioritize issues that prevent users from completing essential workflows. Check interactive states, not only the initial page view.

Keep the scope clear

Automated checks cover only the pages and states reached by the scan and the rules those checks evaluate. They do not establish complete WCAG conformance.

Include manual keyboard, screen reader, focus-order, and task-based review in your accessibility process. Keep the tested environment, scan date, and covered routes with any exported report.

See App access if protected pages are missing from the report.

Generate a WCAG evidence report

1. Select a completed scan that reached the intended public and authenticated pages.
2. Open WCAG reports and review the target and available coverage settings.
3. Start Generate WCAG report.
4. Review its completed, stopped, or coverage-incomplete state.
5. Open the report or select Download HTML when a report is available.

An incomplete coverage result can produce no report. Correct missing access or scope and run it again. The report records automated findings and examined coverage; it is not an accessibility certification. Include the manual review required by your accessibility process and the relevant WCAG standard.