AllAccessible doesn't just check your homepage — it works to discover every page on your site and audits each one on both desktop and mobile. This guide explains the two ideas behind how your pages get found and scanned: sitemap-driven discovery (AllAccessible follows your sitemap automatically) and multi-viewport scanning (the same page is checked at both desktop and mobile sizes). It also shows where to see all of this in your dashboard, under Audits & Fixes.

Note: AllAccessible's automated scan is an informational assessment, not a conformance certification. It surfaces common, machine-detectable issues across your pages to help you prioritize good-faith remediation. Broad page coverage improves how much of your site is checked automatically, but it does not guarantee compliance or replace manual review and testing with real assistive technology.

AllAccessible builds a picture of your site from more than one source, so pages get found whether or not you've listed them anywhere. On the Coverage page (inside Audits & Fixes), the "How we found your pages" section breaks discovery into four sources:

The Coverage page even calls out the gap for you — for example, "Widget caught 12 pages your sitemap missed" — so you can see when real traffic is finding pages your sitemap doesn't declare.

📷 Coverage page "How we found your pages" strip showing Sitemap, Widget pageviews, Crawler, and Manual sources

When you run a crawl-based scan, AllAccessible works through every URL in your subdomain's sitemap rather than stopping at a single page. In the Site Crawler settings you can:

Once the sitemap is set, those pages are loaded into your Coverage view, and a crawl will audit each of them. This is why the change is sometimes described simply as: "Audit Site" now means audit site, not audit homepage.

Tip: If pages are missing from your results, the first thing to check is whether they're in your sitemap. A page that isn't declared anywhere — and hasn't received visitor traffic — may not have been discovered yet. Add it to your sitemap or visit it to bring it into coverage.

A single page can behave very differently depending on screen size. A menu that's fine on desktop might become a keyboard trap inside a mobile hamburger menu; a dialog might only appear at mobile widths. To catch these, AllAccessible scans each audited page under two viewports:

Think of it as the same page seen from two perspectives. When a scan is running, the live progress view shows a Viewport column next to each URL, labelled Desktop or Mobile, so you can see both passes happening.

📷 Live crawl progress with the Viewport column showing Desktop and Mobile rows for the same URL

Everything above lives inside the Audits & Fixes tab for your site. The relevant sub-tabs are:

Audits & Fixes → Coverage. This is your discovery and progress view. It shows:

Use Coverage to answer "how much of my site is actually being checked?"

📷 Coverage page hero showing Coverage %, Fresh, Stale, and Never audited tiles

Audits & Fixes → Scans. This is the history of crawler-driven runs — both manual Scan Now runs and scheduled scans. Each row shows the job, source, start/finish time, page count, and status, with a View audits link to the results. The description reads: "Crawler-driven scans for your site — manual 'Scan Now' runs and scheduled scans."

Audits & Fixes → Live Monitoring (the default landing page). This is where audits from real visitor traffic show up, "refreshed continuously." Its Page Details table lists one row per audited page with a Page URL column and a Live or Crawler badge showing which source produced each audit.

Plan note: The Site Crawler behind sitemap-driven Scan Now runs requires the Reporting Package add-on ($20/month). Even without it, Live Monitoring keeps discovering and auditing pages from real visitor traffic.

Q: Does AllAccessible only scan my homepage?
A: No. It discovers pages from your sitemap, from real visitor traffic, from scheduled crawls, and from pages you add manually — then audits them. Check Coverage to see how many pages have been discovered and audited.

Q: How does AllAccessible find my sitemap?
A: You can enter a Sitemap URL in the Site Crawler settings, or leave it blank and let AllAccessible auto-detect common paths like /sitemap.xml, /sitemap_index.xml, and /wp-sitemap.xml.

Q: Why did my issue count go up after a full scan?
A: Usually because more of your site is now being checked — including mobile-viewport issues and pages beyond the homepage that weren't audited before. Broader, more realistic coverage tends to surface more findings.

Q: What does the Viewport column mean?
A: Each audited page is scanned twice — once at a Desktop size and once at a Mobile size — because different issues appear at different screen widths. The Viewport column shows which pass a given row represents.

Q: A page is missing from my results. Why?
A: It may not be in your sitemap and hasn't received visitor traffic yet, so it hasn't been discovered. Add it to your sitemap (or visit it) and re-check Coverage.

Q: Does full coverage mean my site is compliant?
A: No. Coverage tells you how much of your site is being checked automatically. Automated scanning catches many common issues but can't verify everything a human reviewer would. Use coverage to make sure you're not missing pages — not as a compliance grade.

Possible causes:

Solutions:

Cause: A scan may still be in progress, or you're looking at a summary that doesn't separate viewports.

Solution: Open the live crawl progress or the per-page detail; the Viewport column distinguishes the Desktop and Mobile passes. Let the scan finish before judging coverage.

Cause: Those pages have been discovered (they're in your sitemap or were seen by the widget) but haven't been scanned yet.

Solution: Run a crawl (Reporting Package required), or wait for scheduled scans and real traffic to audit them over time.

Last Updated: July 2026
​Where: Audits & Fixes → Coverage / Scans / Live Monitoring
​Plan note: Continuous discovery from real traffic is included; crawler-driven sitemap scans require the Reporting Package add-on ($20/mo)