Scan a page for accessibility problems
Enter a web address. Raasta runs the automated WCAG 2.2 checks, groups what fails, says who it hurts and gives you the code to fix it.
Three ways to check, and what each one sees
| Check | Runs in | Runs the page’s JavaScript | Takes | Best for |
|---|---|---|---|---|
| Quick scan | This page | No: HTML and CSS as delivered | Seconds | Any public page; content sites, shops, landing pages |
| Live-page check | Your browser, on the page itself | Yes, as on your screen | Seconds | Single-page apps, pages behind a login, open menus and dialogs |
| Monitoring | Raasta’s scheduled headless Chrome | Yes | Every month or week | Every page of a site you own, with new and fixed issues |
All three use axe-core, the open-source engine behind Lighthouse and axe DevTools, with the WCAG 2.0, 2.1 and 2.2 A and AA rules plus axe’s best practices. Try the live-page check or set up monitoring.
The quick scan fetches one public page (up to 2 MB) through Raasta’s server and checks it in your browser; the page’s own scripts never run. Nothing is stored unless you choose Save and share. Automated checks find a large share of problems, not all. Privacy