Overview
Check your website for accessibility problems — public pages, pages behind a login, and multi-step user flows.
There are two ways to check your pages
1. The TestKase web app — paste in your page links and TestKase checks them for you. This works best for public pages that anyone can open. Pages behind a login are harder: you have to give TestKase your cookies, login form, or headers, and some logins still won't work this way.
2. The free Chrome extension — for pages behind a login, use the TestKase Accessibility Toolkit for Chrome. Log in to your site the normal way in your own Chrome, open any page, and scan it. The results are sent to your TestKase account, where you can see them and share them with your team. You never have to give TestKase your password.
TestKase Accessibility Testing checks your website for problems that make it hard to use for people with disabilities — for example, missing image descriptions, low color contrast, or buttons a keyboard can't reach.
You give it a page link, choose which accessibility rules to check against (WCAG), and choose a real browser to run the check in (Chrome, Firefox, or Safari, on Windows or macOS). TestKase then gives you a report that lists each problem, how serious it is, where it is on the page, and how to fix it.
Whichever way you use, the results go to the same TestKase account and look the same. When you check several pages in a row with the extension, you open and share them in the web app, on a screen called Workflow Analyzer.
What you can do
- Check many pages at once — Up to 10 page links in one scan, with results for each page in one report.
- Add pages quickly — Type the links, upload a CSV file of links, or pull them from your site's sitemap.
- Choose the rules — Check against WCAG 2.0, 2.1, or 2.2, at Level A, AA, or AAA. If you don't choose, TestKase uses WCAG 2.1 AA.
- Turn extra checks on or off — Add advanced rules, best-practice rules, or items that need a person to review.
- Check pages behind a login — Sign in using cookies, a login form, or HTTP headers. Your login details are stored encrypted.
- Check a whole user flow — Use the Chrome Toolkit to check each page as you move through your site, including what shows up after you fill a form or click something. You view the results in the Workflow Analyzer.
- One-click check in Chrome — The free Chrome Toolkit adds a TestKase tab to Chrome DevTools that checks the page you have open.
- Share with your team — Share any scan with one or more accessibility teams so everyone can see the results.
- See what matters most — Every problem is marked critical, serious, moderate, or minor. You also get a WCAG summary, a list of affected pages and parts of the page, and a report you can download.
Next steps
- Quick Start — run your first scan in under two minutes.
- Getting Started — a guided tour of the product.
- Scans — the web scanner, checking pages behind a login, and the Workflow Analyzer.
- Reports — read and download your results.
- Chrome Toolkit — install the free Chrome extension.
- Collaboration — share scans and work with accessibility teams.
- Reference — WCAG versions, severity levels, and troubleshooting.
