Paths, not crawls.
Add the home page, a product page, checkout, the contact form. Scan one, or all of them at once.
Scan all nowAdd path
Audits
Find what fails, page by page.
Add a page, run a scan and get a score out of 100. Each issue shows its severity, its WCAG criterion and level, and the exact elements it affects, so the list reads like a to-do list.
7-day free trial on every plan. One script tag, or the Shopify app.The Audits screen of the dashboard: one row per path with a score ring, error and warning counts, the scan cadence and a status. One row shows Scanning, then lands on a score of 93 and Passing.
Quill & Kiln/quillandkiln.comQK
OverviewInstallationAuditsAlt TagsSettings
AuditsAutomated accessibility scans across quillandkiln.com
8 of 20 scans usedScan all nowAdd path
All paths 5Passing 3Issues 1Failing 1
PathScoreErrorsWarningsLast scannedAuto scanStatus
/022h agoDailyPassing
/lighting142h agoDailyIssues
/ceramics……9303nownowjust nowWeeklyScanning…Scanning…Passing
/gift-cards571d agoWeeklyFailing
/journal013d agoMonthlyPassing
One row per page
Add a path, pick a cadence, read the row.
You choose which pages matter. Each one gets its own score, its own schedule and its own status.
A cadence per path.
Daily for the pages that change, monthly for the ones that do not, off for a one-time check.
DailyWeeklyMonthlyOff
Three statuses.
Passing is a score of 90 or more, Issues is 70 to 89, and Failing is anything below 70.
PassingIssuesFailing
A quota you can see.
The scan count for the month sits at the top of the tab, so you can see what your schedules use.
8 of 20 scans used
Audit results
A score, four counts, and the list.
Open a row and you get the score ring, the counts by severity and every issue with its description, its WCAG criterion and level, and the elements it affects.
The Audit results screen: a score of 84 with Needs attention, tiles for Errors, Warnings, Notices and Passed checks, and an issue list where Images must have alternate text is expanded to show WCAG 1.1.1 level A and the affected element.
Quill & Kiln/quillandkiln.comQK
OverviewInstallationAuditsAlt TagsSettings
Audits › /lightingShowing 3 of 11 issues
Audit resultsquillandkiln.com/lighting · Scanned 10/14/2026 9:12 am · 6 rules flagged
Re-scanNeeds attention
Errors
1
WCAG A / AA blockers
Warnings
4
Likely violations
Notices
6
Manual review suggested
Passed checks
212
Across rules
All issuesErrorsWarningsNotices
IssueWCAGSeverityElements
Images must have alternate text1.1.1 · AError3
Affected elements (3)img.product-hero[src="rattan-pendant.jpg"]
What it checks: every image needs alt text, or must be marked as decorative.
Elements must meet minimum color contrast1.4.3 · AAWarning4
Links must have discernible text2.4.4 · ANotice2
Errors
axe-core's critical and serious impacts. These block someone, so start here.
Warnings
Moderate impact. Likely violations that make a page harder to use.
Notices
Minor impact, plus checks axe-core could not finish and wants a person to review.
Passed checks
Every rule that ran and found nothing, so you can see the coverage.
The severity is axe-core's impact rating, grouped three ways. Filter the list to errors and start there.
Open source rules, run in a real browser.
Each scan loads your page in headless Chrome and runs axe-core, the open source rule set behind Lighthouse and many other checkers. An automated scan finds the issues a machine can measure: missing names, contrast, structure, ARIA. It cannot judge whether your link text makes sense or your reading order is right, so plan on manual testing for the rest. The audit gets the measurable part out of the way first.
Re-scan.
Fixed something? Run the page again and watch the row change.
Re-scan
From audit to fix
The list is the plan.
Two of the most common errors have a feature that handles them. The score on your Overview moves as the rows close.
WCAG score / 100On your Overview, from the latest scans
Audits by plan.
Starter5 a month
Growth20 a month
Enterprise100 a month
A scan is one path, run once. Quotas reset on the 1st of each month. Compare plans.
Checking a site against a standard? WCAG 2.2 in plain English explains what the criteria in the audit mean. Want a quick look first? The free checker scans one page without an account.
Does it crawl my whole site?
No. You add the paths you care about, and each one is scanned on its own. Scan all now runs every path at once.
How long does a scan take?
The scanner loads the page in headless Chrome and runs axe-core, so it takes about as long as the page takes to load, plus a few seconds. The row updates when it finishes.
Why does the score differ from another tool?
Tools use different rule sets and different scoring. Accessora runs axe-core, lists every rule that failed and counts the ones that passed, so you can compare issue lists even when the numbers differ.
Can I audit a password-protected page?
Not at the moment. The scanner loads the page like a visitor who is not logged in, so a password page or a bot challenge stops it. Audit a public page, or lift the password while you scan.
Is an audit enough for compliance?
No. Automated checks cover only part of WCAG. Someone still has to tab through your pages, read link text in context and check that headings match the content. Use the audit to clear the measurable issues first.
See it on your own site.
Start a free trial, add the script tag, and the widget shows up on your next page load. Cancel any time during the trial.