Accessibility TestingChrome Toolkit
Toolkit vs Web App
When to use the Chrome Toolkit and when to use the Website Scanner in the web app.
Toolkit vs Web App
Both use the same axe-core engine and push results to the same workspace. They differ in what they can reach and what they can do.
Quick comparison
| Capability | Chrome Toolkit | Web App (Website Scanner) |
|---|---|---|
| Number of URLs per scan | 1 (active tab) | Up to 10 |
| Authenticated scanning | Uses your current browser session | Configurable: cookies / login form / HTTP headers |
| Workflow Analyzer (recorded flows) | ❌ no | ✅ yes |
| WCAG version / rule pack configuration | Uses workspace defaults | Per-scan |
| Element inspection | Native Chrome DevTools | Page snapshot viewer |
| Report export (PDF / CSV / JSON) | In the web app | In the web app |
| Team sharing | In the web app | In the web app |
| Best for… | Quick checks during development | Batch audits, compliance reports |
Pick the toolkit when…
- You're actively developing and want to re-scan a page after a fix without leaving DevTools.
- You want to scan whatever page you happen to have open, without copying URLs.
- You want to inspect a failing element with the native Chrome picker, not a snapshot.
Pick the web app when…
- You need to scan multiple URLs in one run.
- You need configurable authentication (cookies / login form / headers).
- You need a Workflow Analyzer session to catch interaction-triggered bugs.
- You need exports or formal WCAG conformance reporting.
- You want to share a report with an accessibility team.
Can I use both?
Yes — they share the same workspace. A common pattern is:
- Use the toolkit during development to catch issues as you code.
- Use the web app in CI or for periodic audits to produce shareable reports against a bigger URL list.