A worked example, rendered from real sample data. Sign in to run the tool on your own input.
<html>
<body>
<img src="photo.jpg">
<a href="#"></a>
<h3>Skipped h1 and h2</h3>
<input type="text">
<div onclick="doSomething()">
</body>
</html>Accessibility audit — 8 findings (6 errors, 2 warnings, 0 notes)
7 elements across 9 lines scanned.
WCAG 1.1.1 Non-text Content (Level A) — 1 finding
[error] line 3: <img> has no alt attribute
code: <img src="photo.jpg">
impact: A screen reader reads out the file name instead of what the image shows.
fix: <img src="photo.jpg" alt="Describe what the image shows">
WCAG 1.3.1 Info and Relationships (Level A) — 2 findings
[warning] line 1: No <main> landmark
code: <body>
impact: Screen reader users jump straight to the main landmark; without it they must tab through the whole header every time.
fix: Wrap the primary content in <main>.
[warning] line 5: The first heading is h3, not h1
code: <h3>Skipped h1 and h2</h3>
impact: The page has no top-level heading, so its main topic is never announced.
fix: Start the document with a single <h1> describing the page.
WCAG 2.1.1 Keyboard (Level A) — 1 finding
[error] line 7: <div> has an onclick handler but is not focusable
code: <div onclick="doSomething()">
impact: Anyone using a keyboard or switch device cannot reach or trigger this control at all.
fix: Use <button type="button">, or add role="button" tabindex="0" and a keydown handler for Enter and Space.
WCAG 2.4.2 Page Titled (Level A) — 1 finding
[error] line 1: The page has no non-empty <title>
code: <head>…</head>
impact: The title is the first thing a screen reader announces and the only label in a list of open tabs.
fix: <title>Page name — Site name<
…
Check HTML for common accessibility issues (ARIA, alt text, headings). Part of the DevTools Surf developer suite. Browse more tools in the Web / Frontend collection.