Scan data is a planning input, not an audit. Automated scans flag approximately 25% of issues, which is far from enough to determine WCAG conformance, but the patterns they surface can shape a smarter audit scope. Used correctly, scan output helps map your digital assets, group pages by template, identify obvious problem areas, and size the (manual) accessibility audit before it starts. The goal is to walk into the audit with a defined page list, a clear template breakdown, and a realistic budget. Scan data gets you there faster.
| Planning Step | What Scan Data Provides |
|---|---|
| Asset inventory | A crawl-level list of pages, helping confirm what exists across the site |
| Template grouping | Repeated issues across similar pages signal shared templates worth auditing once |
| Page prioritization | High-traffic and high-issue pages rise to the top of the audit list |
| Budget sizing | Page count and complexity drive the audit quote |
| Limitations | Scans only flag approximately 25% of issues and cannot determine conformance |
What Scan Data Can and Cannot Tell You
A scan crawls your site and flags issues it can detect through automation: missing alt attributes, empty form labels, low contrast ratios, missing language declarations, and similar code-level signals. These are useful indicators, but they represent a fraction of what an audit identifies.
Scans cannot evaluate keyboard operability across complex widgets, screen reader output, focus order through dynamic content, the accuracy of alt text, or whether interactive components meet success criteria like 4.1.2 Name, Role, Value. That work requires a human auditor.
So scan data is a map of the terrain, not a verdict on conformance. Treat it that way and it becomes one of the more useful planning tools you have.
Step One: Build the Asset Inventory
Most organizations underestimate how many pages they actually have. A scan crawl gives you a real count and a real URL list. From there, you can separate marketing pages, account pages, checkout flows, blog content, legal pages, and any authenticated areas the crawler missed.
This inventory becomes the foundation of audit scope. Without it, scope conversations default to guesswork. With it, you can decide what to include, what to defer, and what to retire.
Step Two: Group Pages by Template
Auditing every page individually is rarely the right approach. Most websites are built from a small number of templates, and a single product detail page tells you most of what you need to know about all product detail pages.
Scan data accelerates this grouping. When the same issue appears across hundreds of URLs, those URLs almost certainly share a template. Cluster them, then pick a representative sample for the audit. A typical breakdown might include the homepage, one product detail page, one category page, the cart, checkout, account dashboard, and a content page.
Template-based scoping keeps the audit affordable and the remediation efficient. Fix the template, fix the issue everywhere it appears.
How Do You Prioritize Which Pages to Audit First?
Two inputs drive prioritization: traffic and issue density. Pages with the most visitors carry the most legal and user-experience weight. Pages with the highest scan-flagged issue counts often hide deeper problems that only a (manual) review will surface.
Cross-reference the two. A high-traffic page with significant scan-flagged issues should sit at the top of the audit list. A low-traffic page with clean scan results can move down the priority order, but it should not be excluded from conformance scope without review.
Risk Factor or User Impact prioritization formulas can be applied here too, weighing severity against where users actually spend time. The point is to enter the audit with a ranked list, not an alphabetical one.
Step Three: Size the Audit Budget
Audit pricing tracks with page count and complexity. Once you have a template-grouped, prioritized page list, you can size the work with confidence. A 12-page audit covering all major templates often delivers more value than a 40-page audit that re-audits the same template a dozen times.
Scan data also helps flag complexity. Pages with heavy interactive components, dynamic content, or custom widgets take more auditor time than static content pages. Knowing this in advance keeps the quote accurate and the timeline realistic.
Where Scan Data Stops and the Audit Begins
Once the audit starts, scan data steps back. Auditors do not work from a scan report. They evaluate against WCAG success criteria using keyboard navigation, screen reader output, code inspection, and visual review. The scan informed the scope. The audit identifies the issues.
This separation matters. Mixing the two creates confusion about what conformance actually requires. A (manual) accessibility audit is the only way to determine WCAG conformance, and the audit report is the document that supports certification, VPAT/ACR work, and legal defensibility.
Frequently Asked Questions
Should I conduct a scan before requesting an audit quote?
It can help, but it is not required. A reputable audit provider will work with you to define scope based on your asset inventory, template structure, and priorities. Scan data accelerates that conversation, especially for larger sites where the page count is unclear.
Can scan results substitute for an audit on low-priority pages?
No. Scans flag approximately 25% of issues across any page, regardless of priority. Low-priority pages still contain issues a scan cannot detect, and excluding them from audit scope means accepting that those issues remain unknown. The right call is to scope the audit by template, which covers low-priority pages through their shared structure.
How often should I scan versus how often should I audit?
Scanning works well as ongoing monitoring between audits, catching regressions on the 25% of issues it can detect. Audits are conducted at defined intervals, after major product changes, or when a VPAT/ACR needs to be updated. The two work together: scans monitor, audits evaluate.
Does Accessible.org use scan data when scoping audits?
Accessible.org scopes audits based on the client’s asset inventory, template structure, and priorities. Scan data can support the scoping conversation when available, but the audit itself is always fully manual. To discuss scope for your project, contact Accessible.org.
Scan data is a planning tool. Treated that way, it makes the audit faster to scope, easier to budget, and more focused on the pages that matter most.
