Is your website
accessible?
Enter your address and get Google Lighthouse's automated accessibility checks on your homepage, in plain English: missing image descriptions, low colour contrast, unlabelled buttons and form fields, missing page language and more, measured against WCAG. Your full website health report follows.
- Accessibility score
- Failed WCAG checks
- Contrast and labels
- What needs a person
- Full website health
Free to use. No account needed. Want every check first? Use the website checker.
Your report
Accessibility (WCAG, automated)
We couldn't load this site, so there is nothing to test yet.
These are Google Lighthouse's automated checks on one page, the homepage, measured on a simulated phone. Automated tools find only part of the problems a person with a disability runs into, so a clean result is a good start, not proof of WCAG conformance or ADA compliance. What the law asks for.
Based on what one page load shows: security, speed, search visibility, AI search, email and domain, contact and trust. Lighthouse numbers come from Google and don't change the score.
Top things to fix
Nothing to fix from what we can see. Nice site.
What we can tell about the site
Security
HTTPS and the certificate, the protective headers a browser honours, and what the server reveals about itself. An at-risk PHP2Shell verdict is counted here too.
Looks fine.
Speed
What the page's own markup says about load speed, then Google's Lighthouse run on a simulated phone.
Nothing to flag in the markup.
Lighthouse (mobile)
- LCP
- CLS
- INP
- Source
Search (SEO)
The basics Google reads first: title and description, headings, structured data, share cards, robots.txt and the sitemap.
Looks fine.
AI search (ChatGPT, Perplexity, AI Overviews)
Can AI assistants read and recommend the site? Whether robots.txt lets their crawlers in, whether the text is actually in the HTML, and whether there's structured, quotable content.
Looks fine.
Email & domain
Read from DNS and the public registry, nothing from the site: can someone send mail pretending to be you, and is the domain itself safe.
Looks fine.
Contact & trust
Can a visitor reach you, find you, and believe the business is current.
Looks fine.
Scores come from one page load and the HTML as served. Sites that build themselves in the browser can score lower than they deserve; a human look is the fix for that. Lighthouse figures are Google's, measured on a simulated phone.
What the accessibility results mean
The score is Google Lighthouse's accessibility score from 0 to 100. Each automated check either passes or fails, with no partial credit, and the score is a weighted average of them, so one missing button label can cost as much as many. Checks that need a person, such as whether the focus order makes sense, are listed but don't change the score (Chrome for Developers: Lighthouse accessibility scoring).
| Failed check | Who it affects | Typical fix |
|---|---|---|
| Images without alt text | Screen-reader users hear nothing, or a file name. | Describe each meaningful image; mark decorative ones with an empty alt="". See our image guide. |
| Low colour contrast | People with low vision, and anyone on a phone in sunlight. | Darken text or lighten backgrounds to at least 4.5:1 for normal text. |
| Buttons, links or form fields without names | Screen-reader and voice-control users can't tell what a control does. | Give every control visible text or a label tied to it. |
| No page language | Screen readers may read the page with the wrong pronunciation. | Add lang="en" to the <html> tag. |
| Headings out of order | People who navigate by headings lose the page's structure. | Use one H1, then H2 and H3 in order. See on-page basics. |
| Small or crowded tap targets | People with limited dexterity, and everyone on a phone. | Make tap targets larger or space them out (WCAG 2.2 sets a 24 by 24 pixel minimum). |
What an automated checker can't tell you
No automated tool can confirm a site is accessible. When the UK Government Digital Service built a page with 143 deliberate barriers, the best single tool found 37 to 41% of them, and all 13 tools together found 71% (GDS, 2017). Deque, which makes axe-core, the engine Lighthouse uses, reports that automated testing found 57% of the issues in its first-time audits, counted by volume (Deque).
What needs a person: whether the whole site works with a keyboard alone, whether focus is visible and lands in a sensible order, whether alt text actually describes the image, whether error messages explain how to fix a form, whether videos have accurate captions, and whether the pages beyond the homepage, such as booking, checkout and contact forms, work too. That's what an accessibility audit covers.
Accessibility and the law in the United States
For businesses open to the public, the Department of Justice's position is that the ADA covers what they offer on the web, though it has no regulation with a detailed technical standard; it points to WCAG as helpful guidance (ADA.gov guidance, 2022). State and local governments have a specific rule: WCAG 2.1 Level AA, by April 26, 2027 for those serving 50,000 people or more and April 26, 2028 for smaller ones and special districts, after a one-year extension in April 2026 (ADA.gov fact sheet). WCAG 2.2 is the current version of the guidelines, published by the W3C on October 5, 2023. Our ADA website compliance guide explains who must do what.
Want it fixed, not just found? We audit sites against WCAG 2.2 AA by hand and with tools, fix what we find on sites we build or manage, and give you a written report you can keep on file, for one site or several. See accessibility audits, book a free discovery call or call (914) 222-3310.
Common questions
Is this accessibility checker enough to make my site ADA compliant?
No. It runs Google Lighthouse's automated checks on your homepage, and automated tools find only part of the barriers people with disabilities run into. In a UK government test, all 13 tools together found 71% of 143 deliberate barriers. A clean result is a good start; an accessibility audit with manual testing is what tells you where you stand.
What does the accessibility score mean?
It's Lighthouse's score from 0 to 100: a weighted average of its automated checks, each either passed or failed with no partial credit. Checks that need a person don't change it. 90 or more is good, but it measures what a tool can see, not whether the site works for everyone.
Which version of WCAG should my website meet?
WCAG 2.2 Level AA is the current version and the W3C recommends using it. The Department of Justice rule for state and local governments names WCAG 2.1 Level AA, and a site that meets 2.2 AA also meets 2.1 AA. See our ADA website compliance guide.
Does the ADA apply to my business website?
The Department of Justice's position is that the ADA covers the goods and services businesses open to the public offer on the web. It has no regulation with a detailed technical standard for businesses and points to WCAG as guidance. State and local governments have a specific rule, with deadlines of April 26, 2027 and April 26, 2028.
Does this checker change anything on my site?
No. It asks Google's PageSpeed Insights to load your homepage like a visitor and reads the result. Nothing is logged into, submitted or changed.