Web Accessibility Checker
Scan any page for the accessibility issues that fail Lighthouse audits — heading-order skips, missing main landmark, unlabeled form fields, empty links, missing alt text and low-contrast pairs — each with a plain-language fix.
Get more from the Web Accessibility Checker
How it works
- 1PASTE
Enter a page URL
Paste the page you want to make accessible.
- 2SCAN
Find the failures
Heading order, landmarks, form labels, alt text, link names and contrast are checked.
- 3FIX
Follow the plain-language fixes
Each issue comes with a clear fix you can hand to a developer.
Key features
Lighthouse-style checks
Heading order, landmarks, form labels, alt text, link names and buttons.
Colour contrast
Flags text that is hard to read for people with low vision.
Plain-language fixes
Every issue explains who is affected and how to fix it.
Good for SEO too
Clear headings, alt text and link names also help search engines.
Web Accessibility Checker: everything you need to know
It fetches your page’s HTML in your browser and runs the structural checks screen readers depend on: document language and title, a main landmark, exactly one H1, heading levels that never skip, labels on every form field, accessible names on buttons and links, alt text on images, real link destinations, and a best-effort contrast check on inline styles.
- Enter a URL — any public page.
- Read the score — pass/warn/fail across ~10 structural checks.
- Fix the fails first — landmarks and heading order move Lighthouse the most.
- Label every control — inputs, icon buttons, image links.
- Verify contrast in Lighthouse — rendered-page contrast needs computed styles.
Four issues cause most failed Lighthouse accessibility audits: heading levels that skip (h2 straight to h4 — often a footer’s h5), no main landmark, form fields without labels, and text contrast under 4.5:1 — classically white text on light greens or ambers. All four have one-line fixes shown in the table below.
| Issue | One-line fix |
|---|---|
| Heading order skips (h2→h4) | Demote to the next level (h4→h3); footer h5s become styled <div>s |
| No main landmark | Wrap content in <main>…</main> |
| Unlabeled form fields | <label for="id"> or aria-label on every input/select/textarea |
| Low contrast text | Darken text until the ratio ≥ 4.5:1 (white-on-#12996B = 3.35 fails) |
| Links that rely on colour | Underline links inside content so colour isn’t the only cue |
Website accessibility checker: questions people search, answered
Whether you searched for a web accessibility checker, an accessibility issues detector, a WCAG checker or how to check website accessibility online, the questions are similar: what does a checker test, is a free one enough, and how do you fix what it finds?
What is a website accessibility checker?
A website accessibility checker is an online tool that scans a web page for barriers that stop disabled people from using it — missing alt text, unlabeled form fields, poor colour contrast, skipped heading levels and missing landmarks — and maps them to WCAG (Web Content Accessibility Guidelines) success criteria.
How to check a website for accessibility: step by step
Run an automated scan
Paste the URL above for a free WCAG scan of the page.
Fix blockers first
Missing labels, alt text and empty links stop screen-reader users completely.
Check colour contrast
Body text needs at least 4.5:1 against its background (WCAG AA).
Test with the keyboard
Tab through the page: every link and button must be reachable and visibly focused.
Test with a screen reader
NVDA (Windows) or VoiceOver (Mac/iPhone) catch issues no scanner can.
Re-scan after fixes
Repeat on your key templates: home, article, product and form pages.
Free vs paid accessibility checkers
| Free online checker (this tool) | Browser extensions | Paid platforms / audits | |
|---|---|---|---|
| Scope | One page at a time | The page open in your browser | Whole sites, scheduled scans |
| Finds | Common automated WCAG failures | Similar, plus page structure overlays | Automated + manual expert review |
| Cost | Free, no login | Free | Subscription or per-audit fee |
| Best for | Quick checks and fixes | Developers testing locally | Legal compliance and large sites |
- Good start: free scans catch the most common issues quickly
- For compliance: automated tools find only part of WCAG issues, so add manual testing
Who an accessibility check is for
Do small websites need an accessibility check?
Yes. Many laws (ADA in the US, the European Accessibility Act, the UK Equality Act) apply regardless of size, and accessible pages also tend to rank and convert better.
Is an automated scan enough for WCAG compliance?
No. Automated checks find a portion of issues; keyboard and screen-reader testing are still needed for a full WCAG 2.2 AA review.
Tips for better results
- Fix missing labels and alt text first — they block screen-reader users completely.
- Use one H1 and a logical heading order.
- Aim for a contrast ratio of at least 4.5:1 for body text.
- Test with the keyboard only: can you reach every button?
Website owners, developers and agencies who want an inclusive, compliant site.
How this tool handles your data
- Public page fetch. To read a public web page, your browser requests it directly or through a public relay (a CORS proxy) because browsers cannot read other sites on their own. Only the URL you enter is sent; the analysis itself happens in your browser.
- Google PageSpeed Insights. Speed, Lighthouse and Core Web Vitals checks send the URL you enter to Google’s PageSpeed Insights API. Google’s own privacy policy applies to that request.
- No account, no tracking of your input. The tool is free with no login. Anonymous usage statistics (Google Analytics) and ads may use cookies only as described in our Privacy & Cookie Policy.