The Scan accessibility page summarizes accessibility evidence across the whole scan.
This page is different from the page-level Accessibility checks page. Instead of showing one page at a time, it groups Lighthouse accessibility results across every page that completed Lighthouse analysis.
Use it when you want to find repeated problems, site-wide patterns, and pages that may need priority review.
What this page is for
Use the Scan accessibility page to answer questions like:
- how did accessibility look across the whole scan?
- how many pages were checked by Lighthouse?
- which accessibility audits affected multiple pages?
- which issues appear to be isolated?
- which pages had the weakest accessibility results?
- which issue should be opened first?
This page is especially useful for larger websites because it turns many page-level Lighthouse results into one practical review queue.
Overview
The overview cards summarize the scan-wide accessibility rollup.
Average score
The average Lighthouse accessibility score across pages that produced Lighthouse accessibility results.
This is useful for orientation, but it should not be treated as a complete accessibility verdict.
Affected pages
The number of pages with at least one failed, partial, manual, or informational accessibility result recorded in the scan-wide rollup.
Failed checks
The total number of failed accessibility audit results found across the scan.
This is a result count, not a unique issue count. One audit failing on eight pages counts as eight failed checks.
Pages checked
The number of pages with Lighthouse accessibility results compared with the total scanned pages.
If this number is lower than expected, confirm that Lighthouse completed successfully for the scan.
Accessibility issues
The Accessibility issues section lists audit patterns that need attention across the scan.
Each card represents one Lighthouse accessibility audit key, such as heading order, color contrast, image alt text, form labels, or keyboard focus behavior.
Cards show:
- the Siteimp audit title
- the number of affected pages
- whether the issue failed, partially passed, required manual review, or appeared as informational evidence
- a short explanation of the check
Open a card to review that audit across all affected pages.
Scan-wide issue detail pages
Selecting an accessibility issue opens a scan-wide issue detail page.
Those pages show the selected audit across multiple pages, including:
- affected page count
- failed page count
- manual review count
- likely scope
- explanation and impact guidance
- practical checks to perform
- affected page table
This is the fastest way to hand a repeated accessibility pattern to a developer, designer, or content reviewer.
Worst pages
The Worst pages table lists pages that may deserve priority review.
It shows:
- page URL
- accessibility score
- failed audit count
- manual audit count
Open a page from this table to review its page-level Accessibility checks.
How to read this page
A good workflow is:
- Review the overview cards.
- Open the highest-impact accessibility issue.
- Inspect the affected pages.
- Open individual page-level issue details when a specific page needs closer review.
- Use the likely scope and what-to-check guidance to decide whether the problem belongs in content, templates, components, or styling.
Manual results are not failures
Manual results mean Lighthouse found checks that require human judgment.
They should be reviewed, but they are not automatically failed checks.
Examples include:
- keyboard focus behavior
- custom control behavior
- logical tab order
- whether visual and DOM order match
- whether interactive elements clearly communicate purpose and state
Manual accessibility work is where human review matters most.
Failed to load accessibility summary
If Siteimp shows Failed to load accessibility summary, the scan-wide accessibility rollup could not be loaded.
Try returning to Scan results and reopening Accessibility.
If the problem continues, rerun the scan or contact technical support with:
- the scan number
- the website being reviewed
- the exact error text shown in the app
No accessibility summary is available
If Siteimp shows No accessibility summary is available, the scan may not have produced scan-wide accessibility rollup data.
This can happen if:
- Lighthouse did not complete
- the scan was created before scan-wide accessibility rollups existed
- the accessibility derive step did not run
- the scan database is incomplete
Rerun the scan if you need the accessibility overview.