WCAGKit
WCAG 2.2 Compliant — Test any URL or paste HTML directly.

Site Accessibility Checker

Paste HTML or try a browser-readable URL to check for missing alt text, heading errors, empty links, and more.

FreeNo SignupNo UploadsNo Tracking

URL checks are best-effort browser fetches. If the site blocks cross-origin reads, paste the HTML source instead.

Enter a URL or paste HTML above to run accessibility checks.
Embed code
<iframe src="https://wcagkit.com/embed/site-checker" width="100%" height="600" frameborder="0" title="Site Accessibility Checker - wcagkit"></iframe>
<p style="font-size:12px;text-align:center;margin-top:4px;">
  <a href="https://wcagkit.com/tools/site-checker" target="_blank" rel="noopener">Powered by wcagkit</a>
</p>
Attribution preview

Powered by wcagkit

How to Use Site Accessibility Checker

  1. 1

    Paste HTML

    Copy the page source or rendered HTML and paste it into the checker. This is the most reliable and private path.

  2. 2

    Or try a URL

    If the page allows browser cross-origin reads, the tool can read the URL directly. Many production sites block this.

  3. 3

    Run the check

    Click the Check button to analyze the page against 12 accessibility rules covering images, headings, links, forms, and more.

  4. 4

    Review results

    See your overall accessibility score, then drill into each violation to see affected elements and learn how to fix them.

Frequently Asked Questions

The tool runs 12 automated checks: images missing alt text, empty links, missing form labels, heading hierarchy issues, missing lang attribute, missing page title, missing viewport meta, empty buttons, duplicate IDs, missing skip navigation, tabindex misuse, and inline color contrast issues.

Browsers enforce CORS restrictions that prevent JavaScript from reading many other domains. wcagkit stays static-only and does not use a server-side crawler, so paste the HTML source when a URL is blocked.

No. Pasted HTML is parsed entirely in your browser using DOMParser. If you try a URL, the browser requests it directly when allowed. wcagkit does not receive or store the page content.

The score is the percentage of checks that pass with no issues. For example, if 10 out of 12 checks pass, the score is 83%. This gives a quick overview, but you should focus on fixing all errors regardless of the score.

No. Automated tools can detect about 30-40% of accessibility issues. This tool catches the most common machine-detectable problems, but manual testing with a screen reader, keyboard navigation testing, and cognitive accessibility review are all necessary for full WCAG compliance.

The checks map to several WCAG 2.2 success criteria including 1.1.1 (Non-text Content), 1.3.1 (Info and Relationships), 2.4.1 (Bypass Blocks), 2.4.2 (Page Titled), 2.4.4 (Link Purpose), 3.1.1 (Language of Page), and 4.1.1 (Parsing).

Related Tools

Color Contrast Checker

Check color pairs against WCAG AA/AAA

Heading Analyzer

Validate heading hierarchy

Alt Text Checker

Find images missing alt text

Link Checker

Find inaccessible link text

ARIA Validator

Validate ARIA attributes

Why Automated Accessibility Testing Matters

Web accessibility is not optional. Over one billion people worldwide live with some form of disability, and digital accessibility barriers prevent many of them from fully participating in online life. Legal requirements like the Americans with Disabilities Act (ADA), the European Accessibility Act (EAA), and Section 508 of the Rehabilitation Act mandate that websites be accessible to people with disabilities. Automated testing tools like this Site Accessibility Checker are the first line of defense, catching common issues quickly so developers can focus on the more nuanced aspects of accessibility.

What This Tool Checks

This tool analyzes a webpage's HTML against 12 automated accessibility rules that cover the most common and impactful issues found on the web. These include missing image alt text (WCAG 1.1.1), empty links without accessible names (WCAG 2.4.4), form inputs without labels (WCAG 1.3.1), heading hierarchy violations (WCAG 1.3.1), missing page language (WCAG 3.1.1), missing page title (WCAG 2.4.2), empty buttons, duplicate IDs that break ARIA references, missing skip navigation links (WCAG 2.4.1), and tabindex misuse that disrupts keyboard navigation order.

How the Client-Side Approach Works

Unlike many accessibility checkers that require uploading your HTML to a server, this tool operates entirely in your browser. Pasted HTML is parsed using DOMParser, a native browser API that safely converts HTML strings into a DOM tree without executing scripts. If you try a URL, the browser reads it directly only when the site allows cross-origin access. wcagkit does not run a server-side crawler or store page content.

Many websites block cross-origin requests through CORS policies. When this happens, paste the page's HTML source code directly. To get the source code, right-click on any webpage and select "View Page Source" in your browser, or copy the rendered HTML from your browser's developer tools.

Understanding Your Accessibility Score

The accessibility score represents the percentage of automated checks that found no issues. While a high score is encouraging, it is important to understand that automated tools can only detect an estimated 30-40% of all possible accessibility barriers. A perfect score does not mean a website is fully accessible. Manual testing with assistive technology, keyboard-only navigation testing, and evaluation of cognitive accessibility are all necessary for comprehensive WCAG conformance.

Focus on fixing all errors first, as these represent clear WCAG failures. Warnings should be reviewed and addressed where applicable. Passing checks confirm that the automated rules found no problems, but the underlying aspects of the page may still need human verification.

Common Accessibility Issues Found on the Web

According to the WebAIM Million study, which analyzes the top one million home pages annually, the most common accessibility errors are low contrast text, missing image alt text, empty links, missing form labels, empty buttons, and missing page language. These six issues alone account for the vast majority of automatically detectable errors. This tool checks for all of them, making it an effective first step in any accessibility remediation effort.

Next Steps After Running This Check

After fixing the issues identified by this tool, continue with manual testing. Navigate the entire page using only a keyboard to verify all interactive elements are reachable and operable. Test with a screen reader like VoiceOver, NVDA, or JAWS to hear how your content is announced. Check that all functionality works without relying solely on color. Verify that content is understandable at 200% zoom. For a thorough audit, use our individual tools to dive deeper into specific areas like color contrast ratios, heading structure, alt text quality, link accessibility, and ARIA usage.