RichScriptsProducts →
WEBSITE ACCESSIBILITY REPORT

Find the issue.
Show where to fix it.

Turn local website scans into a clear handover report: screenshots, code snippets, repeated issues and retest results.

Build your report →

Free scanner & preview · US$19 / report ZIP · Up to 100 pages

Illustrative developer desk with website review and screenshot reportsAI-created illustration · Not an app screenshot

Evidence your team can use.

  • Actual page and element screenshots
  • Rule + selector grouping across pages
  • Separate manual-review findings
  • Compare scans after repairs

1. Scan locally

Download the scanner, enter your URLs and run it on your computer. This page imports the results; it does not scan websites from the cloud.

Setup and scanning instructions

Requires Node.js 24 LTS. Extract the scanner ZIP and open a terminal in its folder:

npm install --ignore-scripts
npx playwright install chromium
node scan.cjs urls.txt scan-output

Edit urls.txt first: 1–100 explicit HTTP(S) URLs from one origin. Only scan sites you are authorized to test. ZIP the contents of scan-output, including report.json and screenshots/.

Compress-Archive -Path scan-output\* -DestinationPath scan-results.zip

No login, automatic crawling, clicks or form submissions. Initial desktop page state only. Scans remain on your device. Screenshots can contain website content; inspect before sharing.

2. Import results

ZIP up to 50 MB expanded; JSON up to 8 MB. Up to 100 pages and 10,000 finding nodes. A JSON-only report has no screenshots.

Group repeated findings

Exact rule and selector matches are grouped across scanned pages. Each occurrence retains its URL, code snippet and available evidence. This does not infer your framework’s component names.

Retest with honest scope

Resolved findings require a successful retest of the same URL. Failed or missing pages stay “not retested”; new pages are listed as new scope.

Machine checks, clear limits

Uses axe-core WCAG A/AA rule tags. Keyboard flows, screen-reader experience, content quality, authenticated pages and dynamic states still need human testing. No findings does not establish accessibility or legal compliance.

About the axe-core engine →