AllAccessible continuously checks your site for accessibility issues, but you can also trigger a scan on demand whenever you want fresh results — after a redesign, a content update, or a new page launch. This guide shows you where scans live, how to run one from the Audits & Fixes section, how to read your results, and — the question we hear most — how to find out exactly which page an issue is on.

Note: AllAccessible's automated scan is an informational assessment, not a conformance certification. It surfaces common, machine-detectable issues to help you prioritize good-faith remediation. It does not guarantee compliance or replace manual review and testing with real assistive technology.

Before you scan, it helps to know there are two sources of audit data, and they show up as separate views in the sub-navigation:

Both feed the same results tables and scoring. Use Scan Now when you want to check pages proactively instead of waiting for a visitor to hit them.

Plan note: The crawler-based Site Crawler behind Scan Now requires the Reporting Package add-on ($20/month). Without it, you'll still get continuous Live Monitoring audits from real traffic, but the manual crawl option will prompt you to add the Reporting Package.

The tab opens on Live Monitoring by default — the page titled Accessibility Audits, with the sub-heading "Audits from real visitor traffic, refreshed continuously."

📷 Audits & Fixes tab open on the Live Monitoring view

You can start a crawl-based scan from either place:

When the scan starts, you'll see a confirmation that the crawl has begun and how many pages were queued (for example, "Crawl started — 42 pages queued"). The scan works through the URLs in your sitemap.

📷 The Scan Now button in the Live Monitoring filters strip

Open the Scans sub-tab to track the run. The scan history table lists each job with these columns:

While a scan is running, live progress shows each URL, its viewport, status, issue count, and finish time. Larger sites take longer — the crawler works through every URL in the sitemap.

Once the scan finishes, open the results from the View audits action in the Scans table, or head back to Live Monitoring to see the updated numbers.

The Live Monitoring page summarizes your site's accessibility at a glance with several stat cards:

Use the time-period pills (Today, Last 7 days, and longer ranges on paid plans) to change the window. To understand severity and decide what to fix first, see Understanding Audit Results and Tasks.

📷 Live Monitoring stat cards — Scan Score, WCAG coverage, Issue Breakdown

This is the single most common point of confusion, and the answer is: the page is shown, you just need to look at the right view. AllAccessible reports issues per page, and there are two places that spell out exactly which URL is affected.

Scroll down the Live Monitoring page to the Page Details section. This is a table where each row is one audited page. The Page URL column shows that page's full address (long URLs are shortened on screen — hover over the URL to see the whole thing). Each row also shows:

So the issue counts you see in the summary cards are broken down, page by page, right here.

📷 Page Details table with the Page URL column highlighted

Click a page's URL in the Page Details table to open that page's audit detail. The page's full URL appears as the heading at the top, along with the scan date, so there's no ambiguity about which page you're looking at. Below that, each issue is listed with its rule name, issue count, WCAG tags, severity (Impact), and status.

Open an individual issue to see exactly which element on the page is affected — the detail view shows the element's location (its CSS selector) plus plain-language "How to Fix" guidance. That's the element-level "where," inside the page-level "where."

Tip: "Which page?" is answered at the list level (one row per page URL in Page Details) and "which element on that page?" is answered in the issue detail. If you only ever look at the top summary cards, you'll see totals but not locations — always drop down to Page Details.

For agentic fixes, each proposed fix also enumerates every affected page — see Approving Agentic AI Fixes.

Q: What's the difference between Live Monitoring and Scans?
A: Live Monitoring audits pages automatically as real visitors browse them. Scans crawl your sitemap on demand (or on a schedule) whether or not anyone has visited. Both produce the same kind of results.

Q: How long does a scan take?
A: It depends on how many pages are in your sitemap. Small sites finish quickly; large sites take longer because every URL is crawled. Watch progress in the Scans view.

Q: I ran a scan but nothing changed. Why?
A: Give the crawl time to finish (check its Status in the Scans table). If it completed and you still don't see new data, confirm you're looking at the right subdomain and time-period filter.

Q: Why is my Scan Score not 100%, and does a high score mean I'm compliant?
A: The score is an automated, informational signal — not a compliance certification. Automated tools catch many common issues but can't verify everything a human reviewer would. Use it to prioritize, not to certify.

Q: The scan says an issue exists but doesn't tell me where.
A: It does — in the Page Details table on Live Monitoring (the Page URL column), and in each page's audit detail (the page URL is the heading, and each issue shows the affected element). See the section above.

Cause: The crawler-based scan runs through the Site Crawler, which requires the Reporting Package add-on ($20/month).

Solution: Add the Reporting Package to unlock manual and scheduled crawls. Even without it, Live Monitoring keeps auditing your pages from real visitor traffic.

Possible causes:

Solutions:

Cause: Access to a site's audits is available to the site owner and team members who have access to that site. An unexpected error usually points to an access or membership problem, not something you did wrong.

Solution: If you believe you should have access and hit an error, contact support — don't assume the error is expected behavior.

Last Updated: July 2026
​Where: Audits & Fixes → Live Monitoring / Scans
​Plan note: Continuous Live Monitoring is included; manual crawl-based scans require the Reporting Package add-on ($20/mo)