Quick Start: Accessibility Testing
Run your first WCAG scan and read the results.
Scan a page for accessibility issues in about two minutes.
Using an AI assistant? Let it do the setup.
Paste this into Claude, Cursor, Copilot or any coding agent:
Read https://www.testkase.com/SKILL.md to set up TestKase testing.1. Start a scan
Go to accessibility.testkase.com, click Website Scanner, then New website scan.
2. Add your URLs
Type a URL and press Enter. Add up to 10 per scan. The scan is named after the first URL's domain; edit it if you like.
3. Change the settings, or don't
The defaults — Chrome on Windows, checking WCAG 2.1 AA — are fine for a first run. Scan Settings lets you pick a different browser, a different WCAG level, or sign in first if your pages are behind a login. See Authenticated scanning.
4. Start it
Click Create Scan. Expect 30–90 seconds per URL.
Scans spend device-minutes. Accessibility itself is free, but every scan runs on a real browser. Without a subscription that allowance is 15 minutes for the lifetime of the organization, per product. See Usage & minutes.
5. Read the report
Click the finished scan. You get a score out of 100, a breakdown by severity, a list of issues you can filter, and for each one the rule it broke, the element that broke it and a snapshot with that element outlined in red.
Severity runs Critical, Serious, Moderate, Minor — see Severity levels.
While a scan runs you may notice a key called a11y-scan-session in your API keys. TestKase creates it to run the scan and deletes it afterwards — leave it alone.