Free website accessibility checker with fixes
Check any page for WCAG accessibility issues: color contrast, missing alt text, unlabeled links, buttons and form fields. Get a fix for every element, with exact colors and corrected HTML.
Part of our free website audit, which also checks speed, SEO and security. No sign-up needed.
What it checks
- Color contrast
- Text too light against its background, measured against WCAG's 4.5:1 and 3:1 ratios.
- Images without alt text
- Images that screen readers can't describe, including image links.
- Links and buttons without a name
- Icon-only links and buttons announced as just "link" or "button".
- Form fields without labels
- Inputs and menus that don't say what to enter.
- Page structure
- Missing page language, heading order, landmarks and more.
The checks come from Google Lighthouse, which uses Deque's open-source axe-core engine, run on a simulated mobile visitor.
What you get
- A fix for every element
- Not just a list of problems: each failing element gets its own fix, with the exact text or HTML it applies to.
- Exact colors that pass
- For contrast issues, the nearest color that passes, keeping your design's hue, with a before and after preview and the CSS.
- Steps for your platform
- Guides for Shopify, WordPress, Webflow, Wix, Squarespace and Next.js, matched to the platform we detect.
- Progress you can see
- Re-run the audit and see what's fixed since the last scan.
“Web accessibility evaluation tools can not determine accessibility, they can only assist in doing so.”
That applies to us too. Automated checks catch common, measurable problems quickly; pair them with a test using only your keyboard and a screen reader on your key pages.
Accessibility fix guides
- How to fix low color contrast on your website
Text that's too light against its background is hard to read for many visitors, and fails WCAG. What the 4.5:1 rule means and how to fix it on Shopify, WordPress, Webflow, Wix, Squarespace and Next.js.
- How to add alt text to images (and when to leave it empty)
Images without alt text are silent or confusing for screen reader users and invisible to search engines. How to write good alt text and add it on Shopify, WordPress, Webflow, Wix, Squarespace and Next.js.
- How to fix “Links do not have a discernible name” (icon links)
Icon-only links (social icons, a cart, a logo image) are announced as just "link" to screen reader users. How to give them a name on Shopify, WordPress, Webflow, Wix, Squarespace and Next.js.
- How to fix the viewport meta tag (zoom disabled or not optimized for mobile)
One line in your page's <head> controls how phones size the page and whether visitors can zoom. How to fix it on Shopify, WordPress, Webflow, Wix, Squarespace and Next.js.
- How to fix “Form elements do not have associated labels”
Form fields that rely on placeholder text alone are unnamed for screen reader users. How to label newsletter, search and contact fields on Shopify, WordPress, Webflow, Wix, Squarespace and Next.js.
- How to fix “Buttons do not have an accessible name” (icon buttons)
Icon-only buttons such as menu, close, search, cart and slider arrows are announced as just "button". How to name them on Shopify, WordPress, Webflow, Wix, Squarespace and Next.js.
- How to fix heading order (skipped heading levels and empty headings)
Headings that jump from H1 to H4, or exist only for styling, break the page outline screen reader users navigate by. How to fix them on Shopify, WordPress, Webflow, Wix, Squarespace and Next.js.
- How to set your page's language (the lang attribute)
Without a language on the page, screen readers may read your text with the wrong accent and pronunciation. How to set it on Shopify, WordPress, Webflow, Wix, Squarespace and Next.js.
- How to fix small tap targets (“Touch targets do not have sufficient size or spacing”)
Links and buttons too small or too close together to tap reliably. How to give them room on Shopify, WordPress, Webflow, Wix, Squarespace and Next.js.
- How to fix “Frames do not have a title” (embedded maps, videos and widgets)
Embedded maps, videos, booking widgets and forms load in frames that screen readers announce only as "frame". How to give them a title on any platform.
- How to add captions to videos (“<video> elements do not contain a captions track”)
Videos without captions shut out deaf and hard-of-hearing visitors, and anyone watching with the sound off. How to add them on Shopify, WordPress, Webflow, Wix, Squarespace and Next.js.
- How to fix “aria-hidden elements contain focusable descendants”
Hidden menus, slides and pop-ups that keyboard users can still tab into, but screen readers won't announce. How to hide them properly.
- How to fix ARIA dialogs, fields and toggles without an accessible name
Custom pop-ups, dropdowns, switches and progress bars built with ARIA roles that screen readers can't name. How to label them.
- How to fix invalid ARIA (roles, attributes and duplicate IDs)
Misspelled ARIA attributes, roles used on the wrong elements, and labels pointing at duplicate IDs make screen readers report the page incorrectly. How to find and fix them.
- How to fix list markup (lists must only contain list items)
Lists with stray elements inside, list items without a list, and ARIA roles missing their parent or children. Why screen readers care and how to fix the markup.
- How to fix “Some elements have a tabindex value greater than 0”
Positive tabindex values force a custom tab order that skips around the page and confuses keyboard users. How to remove them, and why duplicate accesskeys cause similar trouble.
- How to add a skip link and a main landmark
Keyboard and screen reader users have to wade through your whole header on every page unless they can jump straight to the content. How to add a working skip link and <main> region.
- How to fix data table headers (size charts, price and spec tables)
Tables whose header cells aren't connected to their data leave screen reader users hearing numbers without context. How to mark up size charts and comparison tables correctly.
- How to fix “The document uses <meta http-equiv="refresh">”
Pages that reload or redirect themselves after a delay pull visitors away mid-read. How to replace a meta refresh with a proper redirect.
- How to fix “Links rely on color to be distinguishable”
Links inside paragraphs that look different only by color are invisible to many colorblind visitors. The simple fix is an underline.