Free accessibility checker for any website
Scan for 14 common markup issues that affect screen readers, keyboard users, and assistive technology. Results in under 60 seconds.
No signup required. Results in under 60 seconds.
423,000+ checks run and counting
What we check
One in four adults in the US has a disability. Missing alt text, broken heading order, and unlabeled forms make sites harder for people who use screen readers or keyboards. Fixing these issues helps everyone, not just people with disabilities. Clear markup also helps search engines read your pages.
Many accessibility problems are easy to fix once you know they exist. A missing alt tag takes seconds to add. A skipped heading level is a quick edit. The hard part is finding the issues in the first place. That is what this checker does.
Verifies the page has exactly one H1 element. More than one confuses screen readers about the main topic.
Checks that the HTML tag has a lang attribute. Screen readers need this to pronounce words correctly.
Confirms the viewport meta tag does not disable user scaling. People with low vision need to zoom in.
Flags images missing alt text. Screen reader users hear nothing for images without it.
Checks that headings follow a logical H1 to H6 order. Skipped levels confuse both users and search engines.
Verifies the page uses elements like main, nav, and footer. These help screen readers jump to key sections.
Checks for a skip-to-content link. Keyboard users need it to bypass repeated menus on every page.
Flags form inputs with no linked label. Without labels, users can't tell what a field asks for.
Checks for valid ARIA roles on buttons and controls. Wrong roles confuse assistive tools.
Verifies iframes have titles that describe their content. This helps screen readers explain embedded content.
Flags positive tabindex values that break natural tab flow. This makes keyboard navigation confusing.
Checks that data tables use th elements. Without them, screen readers can't link cells to column names.
Flags links that say 'click here' or 'read more.' Users need link text that tells them where the link goes.
Checks that inline SVGs have title or aria-label tags. Without them, screen readers skip the graphic.
These 14 checks cover the most common accessibility issues found on the web. They won't catch everything, but they are a strong starting point. Run a scan to find what needs fixing and get clear next steps.
Each check comes with a short tip that explains what to fix and why it matters. You do not need to be an accessibility expert. The fixes are usually small markup changes that take minutes to make.
What to fix first
- Main Heading (H1): Verifies the page has exactly one H1 element. More than one confuses screen readers about the main topic.
- Page Language Set: Checks that the HTML tag has a lang attribute. Screen readers need this to pronounce words correctly.
- Mobile Viewport Configured: Confirms the viewport meta tag does not disable user scaling. People with low vision need to zoom in.
How to use this audit
- Run the scan and identify which warnings appear across several pages, not just one template.
- Fix the problems that affect visibility, trust, or conversion first, then move on to polish items.
- Re-scan after each batch of changes so you can confirm the issue count actually drops.
Why this matters in the full scan
This category is most useful when you review it alongside the other six. A site can look good in one area and still lose traffic or trust because another area is weak. SiteCurl keeps these checks together so teams can work from one prioritized report instead of juggling separate tools.
Example findings from a scan
4 images missing alt text
Heading hierarchy skips from H2 to H4
No skip navigation link found
See how teams use SiteCurl:
Deep dives for common findings:
Frequently asked questions
Does SiteCurl test for full WCAG compliance?
No. SiteCurl checks 14 common markup issues. It gives you a starting point, not a full WCAG 2.2 audit. You should still test with real users and screen readers.
What accessibility checks does SiteCurl run?
SiteCurl checks H1 tags, page language, viewport, alt text, heading order, landmarks, skip links, form labels, ARIA roles, iframes, tabindex, tables, link text, and SVG names.
How is this different from WAVE?
WAVE gives deeper detail on a single page. SiteCurl checks 14 common issues across many pages as part of a broader seven-type audit.
Can I scan more than one page?
The free audit checks your home page. With a paid plan, you can scan up to 100 pages per site and track accessibility scores over time.
How do I fix a missing alt tag?
Add an alt attribute to the image tag that describes what the image shows. Keep it short and clear. SiteCurl tells you which images need it.
Why does heading order matter?
Screen readers use headings to build an outline of the page. Skipping from H2 to H4 breaks that outline and makes it hard for users to find what they need.
Check your site for accessibility issues