Free tool · no signup

Free Website Accessibility Checker

A quick automated scan of one page for common accessibility problems: images without alt text, form fields without labels, links and buttons with no name, blocked zoom and more. Each result says why it matters and how to fix it on WordPress, Wix, Squarespace or Shopify.

Your home page, or any page, like yourbusiness.com/contact.

Checks one page, as it is sent to browsers before any scripts run. Takes a few seconds. Reads public information only and changes nothing on your site.

Please read: this is a quick automated scan of one page's HTML. It is not an accessibility audit and not legal advice, and it can't tell you whether your website meets the ADA, WCAG or any other law or standard.

Automated checks find only some accessibility issues. Many can only be found by a person, for example by using the site with a keyboard alone or with a screen reader. For legal questions, talk to a lawyer or a professional accessibility auditor.

What this accessibility checker looks at

Website accessibility means people with disabilities can use your site: someone who is blind and uses a screen reader, someone who can't use a mouse, someone with low vision who zooms in, or someone who can't hear a video. Many of the most common problems are visible in a page's code, and those are what this checker reads:

Results are grouped into Needs fixing, Worth a look, Nothing found and Not checked by this tool. The last group is the list of things only a person can test, and it is on every result.

What an automated check can't tell you

No automated tool, including this one, can tell you that a website is accessible. Tools catch some of the common, easy-to-spot problems. Many important ones need a person:

The W3C, which writes the Web Content Accessibility Guidelines (WCAG), explains them in its WCAG overview, and has a short guide to easy checks you can do yourself. For a full review, hire a professional accessibility auditor; many test with people who use screen readers every day.

Accessibility and the law

We can't give legal advice, and this checker can't tell you whether your website meets the Americans with Disabilities Act (ADA) or any other law. WCAG is the standard most often used to measure website accessibility, but whether and how a law applies to your website is a question for a lawyer. If you have received a legal letter about your website, talk to a lawyer.

Be careful with any product that promises to make your site meet the law with one line of code. A toolbar or “overlay” widget runs on top of your page; it doesn't fix the problems in your page's own code, which is what this checker (and most others) read.

How to fix each issue

Menu names below are the ones we know from each builder's own settings. They can change between versions, so if you can't find one, search the builder's help pages for the same words.

Page language

The page should start with a tag like <html lang="en"> (or lang="es" for Spanish, and so on).

Page title

Alt text for images and image links

Write what matters about the image in a few words: “Chocolate birthday cake with candles”, not “cake.jpg”. If the image is a link or button, say where it goes: “Book an appointment”. If an image is only decoration (a background pattern, a divider), give it empty alt text so screen readers skip it; most builders do this when you leave the field empty and mark it as decorative.

Links and buttons with no name

These are usually icon-only links and buttons: social media icons, phone, search, cart, or the menu button on phones. Each needs a short label that a screen reader reads out, like “Our Facebook page” or “Open menu”. In code it looks like <a href="…" aria-label="Our Facebook page">.

Form fields without labels

Every field needs a label that says what to type, like “Your email”, and the label should stay visible. Grey hint text inside the box (a placeholder) is not enough: it disappears when people start typing.

Headings

Use one Heading 1 that says what the page is about, then Heading 2 for each section and Heading 3 inside those. Pick the heading level by its place in the outline, not by how big it looks; change the size with styling instead.

Repeated ids

An id is an internal name for one part of a page, and should be used once. Repeats usually come from the same embed code pasted twice (two forms, two widgets), or from a theme or app. Remove duplicate embeds where you can. Repeats only matter much when a label points to the repeated id, which is why those are under “Needs fixing”; otherwise this is a low priority. On Wix and Squarespace these ids are mostly written by the builder; ask their support if a label is affected.

Embedded frames without a title

Maps, videos and booking or review widgets are often embedded as frames. Add a short title to the embed code: <iframe src="…" title="Map of our shop on Google Maps">. Our free Google Maps Embed Generator adds a title to the map code it makes.

Zooming is blocked

The page's viewport tag should be <meta name="viewport" content="width=device-width, initial-scale=1">, without maximum-scale=1 or user-scalable=no.

Media that plays by itself

Never start sound by itself. Video that plays on its own should be muted and have a visible pause button, or not start at all.

Links that say “click here” or “read more”

Make the link words say where the link goes: “See our menu” instead of “Click here”, or “Read more about our facials” instead of “Read more”. You can change link text in any builder's editor; a “Read more” added by a WordPress theme is often changed in the theme's settings.

Tables without header cells

If a table shows information (prices, opening hours, sizes), its first row or column should be header cells. In WordPress, turn on Header section in the Table block's settings. In code, use <th> instead of <td> for the headers. Opening hours also work well as a simple list.

Text that is hard to read

Normal text needs a contrast of at least 4.5 : 1 with its background, and large text at least 3 : 1. Make the text darker or the background lighter (or the other way round), and check the two colors with a free tool such as WebAIM's contrast checker.

Your website builder's own accessibility help

None of these settings, and no checker, make a site accessible on their own. They help you find and fix problems.

What this checker does, and its limits

Questions

Is the Website Accessibility Checker free?

Yes. There is no signup, no email and no card. It is made by FlatRateChat, a website chatbot company, and it doesn't change anything on your site.

My page had no issues. Does that mean it meets the ADA?

No. This checker can't tell you that, and no automated tool can. A clean result means our checks didn't find the common problems they look for in the page's HTML. Many issues can only be found by a person, and whether a law applies to your website is a question for a lawyer.

What is WCAG?

The Web Content Accessibility Guidelines, written by the W3C. They describe what makes web content accessible, in levels A, AA and AAA; many organizations aim for level AA. The checks here are based on a few of the guidelines that can be tested from a page's code.

Will an accessibility widget fix these issues?

A toolbar or “overlay” widget runs on top of your page; it doesn't fix the problems in your page's own code, which is what this checker (and most others) read. Fixing them in your builder or theme is what helps visitors.

Why are my results different from another checker's?

Checkers test different things in different ways. Some run your page in a full browser, with its scripts and style sheets, and can check more (like contrast). This one reads the HTML as served, so it can miss things scripts add, and it never guesses about what it can't see.

I fixed it, but the result hasn't changed. Why?

On Wix, Squarespace and other builders, remember to publish your changes. Some sites and hosts also keep an older copy of the page for a while (caching); wait a few minutes and check again.