Guide · reviewed 2026-11-03
How can I check my website’s accessibility for free?
You can check a website’s accessibility for free in two steps: run an automated WCAG check such as the Accessibility audit in Chrome’s Lighthouse, the axe DevTools browser extension or WebAIM’s WAVE, then test the page yourself with only a keyboard and with a screen reader, because automated tools find many problems but not all. Raasta’s free quick scan does the automated part with no account: enter a URL and get a score, the problems ranked by impact and the code to fix each one.
Step 1: an automated check
- Raasta’s quick scan. Enter a URL at raasta.danixsoft.com/scan, with no account. Raasta fetches the page and runs the axe-core rules in your browser, then shows a score, the problems grouped by rule and ranked by impact, who each one hurts, and fix code for HTML, React, Shopify Liquid and WordPress. It checks the page’s HTML and CSS without running its JavaScript.
- Raasta’s live-page check. For pages built with JavaScript, behind a login or with a menu or dialog open: a bookmarklet runs the same rules on the real page in your own browser.
- Lighthouse (built into Chrome). Open DevTools, choose Lighthouse, tick Accessibility and run it. It uses the axe-core rules and lists failing elements.
- axe DevTools. A free browser extension by Deque that runs the axe-core rules on the page you are viewing, with more detail per issue.
- WAVE. WebAIM’s free checker, as a website or extension, which marks problems directly on the page.
Step 2: what only a person can check
- Keyboard only. Put the mouse away and press Tab through the page. Can you reach and use every link, button and form field, and can you always see where focus is?
- A screen reader. VoiceOver (Mac, iPhone), NVDA (free on Windows) or TalkBack (Android). Do images, buttons and form fields announce something meaningful?
- Zoom and reflow. Zoom to 200% and 400% on a desktop browser. Text should stay readable without scrolling sideways.
- Plain sense. Are error messages clear, are links named for where they go, and does anything move, flash or time out without warning?
Fixing what you find
Most automated failures fall into a short list: images without alt text, buttons and links without names, low contrast, unlabelled form fields and a missing page language. Raasta’s rule guides explain each one, who it affects and the code that fixes it, for plain HTML, React, Shopify Liquid and WordPress. Fix the failures that block people first (critical and serious), then scan again to confirm they are gone.
See the common failures and their fixes, the WCAG 2.2 guide or the accessibility statement generator.
Questions
Does passing an automated check make my site compliant?
No. Automated checks find a share of WCAG failures, not all of them, and some criteria can only be judged by a person. Use them to catch the common problems, then test by hand.
Is Raasta’s scan really free?
Yes. The quick scan and the live-page check need no account and check one page at a time. A free account adds monitoring of one site (up to 5 pages, checked monthly); paid plans cover more pages and sites.
Which standard should I test against?
WCAG 2.2 level AA is the usual target. The European Accessibility Act points to EN 301 549, which builds on WCAG level AA.