Most accessibility audits evaluate between 15 and 50 pages or screens. The exact number depends on the size and complexity of your website or web app, the variety of unique templates and components, and the purpose of the audit itself.
Page count is one of the first decisions in scoping an audit, and it directly affects cost, timeline, and how thoroughly WCAG conformance can be assessed. Getting it right means the audit covers enough ground to produce meaningful results without inflating the scope beyond what the content requires.
| Factor | How It Affects Page Count |
|---|---|
| Unique templates | More distinct page layouts require more pages in scope |
| Interactive components | Forms, modals, carousels, and dynamic content each need evaluation |
| Small marketing site | Typically 10 to 20 pages covers full template variety |
| Medium website | Usually 20 to 35 pages captures core content and functionality |
| Large site or web app | 30 to 50+ pages or screens, depending on feature depth |
| Audit purpose | Legal response audits may need broader scope than routine conformance checks |
What Determines the Number of Pages in an Audit Scope?
An accessibility audit does not need to evaluate every page on a site. It evaluates a representative sample. The goal is to capture every unique template, component type, and user flow so that identified issues can be applied across the entire site during remediation.
A 500-page website might only have 12 distinct page templates. A 30-page web app might have 40 unique screens and states. Template variety drives scope more than raw page count.
Pages are selected to represent the full range of content and functionality. A typical scope includes the homepage, navigation, key landing pages, forms, search results, account or login flows, and any page with unique interactive elements.
Common Scope Ranges by Site Type
For a small business or marketing website with a homepage, a few service pages, a contact form, and a blog, 10 to 20 pages usually covers the full template set. Every distinct layout gets represented.
Mid-size sites with more content types, such as e-commerce product pages, filtering interfaces, or member portals, typically call for 20 to 35 pages. This range accounts for the additional interactive patterns that need evaluation.
Large websites and web applications often require 30 to 50 or more pages. Web app accessibility projects tend toward the higher end because each distinct screen, workflow, and user state introduces different accessibility considerations.
Why More Pages Is Not Always Better
Adding pages to an audit scope increases cost and time. But it does not always increase value. If two pages share an identical template, evaluating both produces duplicate findings.
The quality of page selection matters more than quantity. A well-scoped 25-page audit that covers every template and component type will identify more unique issues than a 50-page audit filled with redundant pages.
Accessible.org scopes audits by mapping the full set of unique templates and interactive patterns first, then selecting the minimum number of pages needed to cover them all. This keeps scope tight and results actionable.
Do Scans Reduce the Number of Pages You Need Audited?
No. Automated scans and (manual) audits serve different purposes. Scans only flag approximately 25% of issues. They can detect certain code-level patterns across an entire site, but they cannot evaluate keyboard navigation, screen reader compatibility, logical reading order, or the dozens of criteria that require human judgment.
Scans can inform an audit by surfacing widespread code patterns, but they do not replace any portion of the audit scope. The number of pages in an audit is determined by content and functionality variety, not by what a scan already covered.
How Does Audit Purpose Affect Scope?
An audit conducted as part of a routine conformance review may focus on core user paths and primary templates. An audit completed in response to a legal demand or ADA compliance concern may need broader coverage to demonstrate thorough evaluation.
When the audit will inform a VPAT or ACR, scope aligns to the product’s feature set. Every documented feature needs its corresponding screens evaluated so the conformance report accurately reflects the product’s accessibility status.
The purpose does not change the methodology. It changes how wide the net needs to be.
What Should Be Included Beyond Standard Pages?
Pages are the primary unit of scope, but audits also need to account for states and conditions that appear on those pages. A login page in its default state is different from the same page displaying an error message. A product filter in its collapsed state behaves differently from its expanded state.
Component states, error conditions, modal dialogs, dropdown menus, and multi-step forms all add evaluation points within a single page. An experienced auditor accounts for these when setting scope rather than treating each page as a flat, single-state artifact.
PDFs, embedded media, and third-party widgets that appear within the audit scope also need evaluation. If a page includes a PDF download or an embedded scheduling tool, those elements become part of that page’s audit.
How to Determine the Right Scope for Your Site
Start by cataloging every unique page template on your site. Then identify every distinct interactive component: forms, navigation patterns, carousels, accordions, data tables, and media players. Each one needs representation in the scope.
Next, map your primary user flows. If a visitor can browse products, add items to a cart, and check out, every step of that path belongs in scope. If a user can create an account, manage settings, and submit support requests, those flows need coverage too.
The right number of pages is the smallest number that covers all of these elements without leaving any template or critical flow unevaluated. For most organizations, that falls between 15 and 40 pages.
Can I audit fewer than 15 pages?
Yes, if your site has fewer than 15 unique templates and limited interactivity. A five-page brochure site with one form may only need 5 to 10 pages in scope. The number is driven by content variety, not an arbitrary minimum.
Should I increase my audit scope if I plan to remediate everything?
A broader scope identifies more unique issues upfront, which can make remediation planning more efficient. But if your current scope already captures every template and component type, adding more pages will mostly produce duplicate findings rather than new ones.
How often should the scope change for recurring audits?
Scope should be revisited whenever the site changes significantly. New features, redesigned templates, or added content types all warrant updated page selection. If the site has remained stable, the same scope is appropriate for a follow-up audit.
Scoping an audit correctly is one of the most practical decisions in the accessibility process. It sets the foundation for everything that follows. Getting to the right page count means the audit delivers a complete picture of your site’s conformance status without paying for redundancy.
Contact Accessible.org to scope an accessibility audit for your website or web application.
