Accessibility page checker

Check any public page for accessibility issues

Paste a page URL to see what might block people who use keyboards or screen readers. We explain each finding in plain language and link you to interactive demos on this site.

Enter a public page URL

We send the URL to WAVE (opens in a new tab) to detect issues, then explain how to fix them in plain language.

Include https:// at the start, for example https://example.com

What this checker does

This tool runs your URL through the WAVE accessibility API and reports issues in the HTML it can fetch. It is a useful first step, not a complete audit.

What it finds

  • Image alt text (missing, weak, or on linked images)
  • Form labels, fieldsets, and select/combobox labeling
  • Empty links, buttons, and unnamed controls
  • Page language not set on html
  • Colour contrast failures (approximate)
  • Heading order and empty headings
  • Landmarks, tables, and document regions
  • Broken ARIA references (dialogs, menus, widgets)
  • Skip links, tabindex, and keyboard-related alerts
  • Detected features, structure, and ARIA (for manual review)

Still needs manual testing

WAVE does not run full keyboard journeys through modals, comboboxes, search suggestions, infinite scroll, drag-and-drop, or live toast regions. It cannot verify focus return, alertdialog behavior, or breadcrumb current-page semantics. Plan manual keyboard and screen reader testing after you fix what this scan reports.

Important: Automated tools catch roughly 30–40% of accessibility issues. Manual testing and screen reader testing are still required for a complete audit.

What to do next

After your scan

  1. Fix the errors this tool found first
  2. Test your page with keyboard only (Tab, Enter, Escape)
  3. Test with a screen reader (NVDA on Windows, VoiceOver on Mac/iOS)
  4. Use the Playground to learn how to fix common patterns
  5. Explore Dev Tools (wcag-kit, Claude Skill, and WCAG Lens) while you implement fixes
Back to top