Paste the HTML of a page or a snippet and get a list of common accessibility problems, each with the line it is on and a short fix. It looks for images without alt text, form fields without labels, empty links and buttons, skipped heading levels, duplicate ids and a few other basics. It checks only the code you paste, never a live website.
Markup rules are the part of accessibility a program can judge reliably. Either an image has an alt attribute or it does not; either a text field is connected to a label or it is not. These are the same facts a screen reader reads out, so fixing them has an immediate effect on people who browse by listening.
What a code check cannot see is meaning and appearance. It cannot tell whether alt text describes the picture well, whether grey text on a white background is readable, or whether a modal traps keyboard focus. Treat a clean result as the floor, then spend your time on those judgement calls.
Names come first. Every link, button and form field needs a name that a person can hear: text inside it, an associated label, or an aria-label for icon-only controls. A page full of unnamed controls reads like a list of the word 'button', and nobody can tell them apart.
Structure comes second. Headings give a page an outline that people jump around with, so keep one h1 and do not skip levels. Landmarks such as main, nav and footer let visitors leap to the part they want. Using real elements for real jobs, a button for actions and a link for navigation, gives you keyboard support without writing any script.
No. It reads only the HTML you paste, so it never visits a web address. Content that a script adds after the page loads is not in the pasted code and is not checked.
Images without alt text or with file names as alt text, form fields without a label, image buttons without alt, empty links, vague links such as 'click here', empty buttons and headings, skipped heading levels, duplicate ids, a missing language, title, h1 or main landmark, positive tabindex values, frames without a title, data tables without header cells, media that autoplays, click handlers on non-interactive elements and viewport tags that block zoom.
An error is a missing piece that blocks or confuses people using assistive technology, such as a button with no name. A warning is a pattern that is often wrong or makes a page harder to use, such as a heading level that jumps from h1 to h3. Warnings can be intentional; errors rarely are.
Every time the tool applies a rule to an element it counts one check. If the element meets the rule it is a pass, otherwise it adds a row to the table. For example, a page with three images where one lacks alt text has three image checks, two passes and one error.
No. WCAG covers far more than markup, including contrast, motion, timing and how content reads aloud. Use this as a fast first pass, then test with the keyboard and a screen reader. This is a code check and not legal or compliance advice.
Related: Colour contrast checker, Image alt text generator, Accessibility statement generator.
Start for free or see all free tools. We.Inc is free to start, with no card needed. AI building is on paid plans from $20 a month.
We.Inc is an AI-powered website builder you can resell under your own brand. Launch a branded client dashboard, bill on Stripe Connect, and deliver AI-generated websites in minutes. White-label plans start at $99 a month for 25 client sites, with a 7-day free trial and no per-site fees.