WCAG Page Scan

Scan a live URL for WCAG issues: alt text, labels, headings, language, skip links, iframes, autoplay, and landmarks

100% free. This tool needs our server to do the work, so what you submit is sent there, processed and then discarded - it is never stored.

Static HTML analysis - a full audit also needs manual keyboard and screen-reader testing.

Jump to the next useful tool without leaving your flow.

See more

About this tool

A colour-contrast widget does not tell you whether a live page has alt text, form labels, a skip link, iframe titles, a language attribute, heading order, landmarks or autoplaying media. This scan fetches the URL and checks that HTML for those WCAG-style issues, then lists errors, warnings and checks that passed. It is the same engine as the Accessibility Checker, pointed at a full-page URL audit. JavaScript-only banners and canvas apps will be under-reported. Keyboard and screen-reader testing still matter. Not a certification.

How to use this tool

  1. Paste the live HTTPS URLThe page is fetched server-side so you are not blocked by the browser's cross-origin rules.
  2. Run the auditMarkup is checked for alt, labels, headings, lang, skip links, iframes, autoplay and landmarks.
  3. Fix by rule, then re-scanEach finding names the rule. Component-level fixes beat one-off page patches.

What an automated WCAG scan can and cannot tell you

An automated scan reliably finds missing alt text, unlabelled inputs, missing page language, untitled iframes, heading order problems, missing landmarks and autoplaying media. Those are worth fixing first, because they affect every visitor who uses assistive technology.

It cannot judge whether alt text is meaningful, whether the reading order makes sense, or whether everything works by keyboard. Pair the scan with a manual check before you claim WCAG conformance.

Key features

  • Goes beyond contrast: skip links, iframe titles, lang, autoplay, landmarks.
  • Error / warning / passed counts so you can see remaining work.
  • Same checks as the Accessibility Checker with a WCAG-oriented heading for this route.
  • No signup. You only submit a public URL.

Common uses

  • Pre-release pass on a marketing site before a client a11y review.
  • Finding missing alt and labels on a legacy template.
  • Checking that a skip link and main landmark exist after a redesign.

Tips for better results

  • Pair with the colour contrast checker for text that this HTML pass cannot see inside images.
  • Re-run after the first contentful paint is in the HTML. Client-only widgets will look empty here.
  • A passed automated scan is not WCAG conformance. Manual keyboard testing remains required.

Mistakes to avoid

  • Treating zero errors as a legal WCAG 2.2 AA certificate.
  • Scanning a login wall and thinking the app behind it was tested.
  • Ignoring warnings because only errors are counted in a KPI.

Frequently asked questions

Static HTML from the URL: image alt, form labels, heading structure, page language, skip links, iframe titles, autoplay media and landmark regions. Contrast of CSS text is better on the dedicated contrast tool.

Same audit engine. This route is named and described as a full-URL WCAG pass. Use either; pick the name your team already searches for.

It sees the HTML we fetch. If the useful UI appears only after JavaScript, findings will be incomplete. That gap is itself a hint to test with a real browser.

No. Automation catches a subset. Keyboard order, screen-reader wording and cognitive load need a person.

Yes. Not a certification body.