Skip to main content
Raasta

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.

One public page per scan, checked with axe-core against WCAG 2.2 A and AA. No account needed. Need JavaScript, a login or an open menu checked? Use the live-page check.

Three ways to check, and what each one sees

Comparison of Raasta’s quick scan, live-page check and monitoring
CheckRuns inRuns the page’s JavaScriptTakesBest for
Quick scanThis pageNo: HTML and CSS as deliveredSecondsAny public page; content sites, shops, landing pages
Live-page checkYour browser, on the page itselfYes, as on your screenSecondsSingle-page apps, pages behind a login, open menus and dialogs
MonitoringRaasta’s scheduled headless ChromeYesEvery month or weekEvery 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