How our accessibility scans work
What an automated scan measures
We run axe-core in Chromium against the rendered page. A site scan discovers linked pages on the same origin, up to 250 pages. A scan observes one page state; it does not automatically sign in, complete purchases, open every dialog, or explore every interaction.
Network failures and skipped pages are reported separately. A page that could not be tested is not evidence that its issues were fixed.
Understanding the score
The current score starts at 100 and deducts 8 points per critical rule, 4 per serious rule, 2 per moderate rule and 1 per minor rule, with a minimum of zero. Repeated occurrences do not multiply this deduction. Use affected-element and page counts to understand the extent of a finding.
Site scores average successful page scores. Regression comparisons also consider increased affected elements, pages and changed selectors. Scores are compared only when coverage is comparable. A score is a prioritization aid, not a percentage of WCAG compliance or a legal certification.
What this scan does not cover
Keyboard operation, screen-reader experience, and full user journeys are outside this automated scan.
New completed reports preserve their findings and scoring version. Page retests create a new run and retain the original evidence. Older reports created before snapshots were available may use current catalog descriptions.
Reports and scan credits
Free single-page reports are public to people with the report link and excluded from search indexing. Saving one bookmarks it in your account. Site reports require access to the owning account.
When paid credits are enabled, one credit covers one successfully completed site page audit. Failed audits do not consume a credit. Credits are added by an administrator after an invoice is confirmed outside this app.