Guide8 min readUpdated
Accessibility Testing Tools: What axe and Lighthouse Check
Accessibility testing tools such as axe-core and Lighthouse find part of the problems in minutes. See what they check, how to run them and what they miss.
By Tithi Mondal, UI/UX Designer
Suppose a coaching centre in Asansol has an admission form on its website. A parent who cannot see well opens the form with a screen reader. A screen reader is software that reads the screen aloud. The screen reader says "edit text, edit text, edit text, button". No field has a name, so the parent cannot tell where to type the phone number. The parent leaves, and the coaching centre never knows.
Accessibility testing tools are programs that scan a web page and report barriers of this kind for people with disabilities. Two free and widely used tools are axe-core, made by a company called Deque, and Lighthouse, made by Google. This guide explains what each tool checks, how you can run a check without a developer, and what the tools cannot see.
Checked in November 2026. Tools change quickly, so confirm details on the project's own page.
What do accessibility testing tools actually check?
Accessibility testing tools check the things that can be measured in the code of a page. The tools compare the page against written rules. Most rules come from the Web Content Accessibility Guidelines (WCAG), the international standard for accessible websites.
axe-core. The project's README describes axe-core as "an accessibility testing engine for websites and other HTML-based user interfaces". According to the project's documentation, axe-core has rules for WCAG 2.0, 2.1 and 2.2 at levels A, AA and AAA, plus a set of best practice rules. The repository states that axe-core is distributed under the Mozilla Public License, version 2.0. An engine is the part that does the checking. Other products, including browser extensions, put a screen on top of the engine.
Lighthouse. Google's documentation describes Lighthouse as "an open-source, automated tool to help you improve the quality of web pages". According to the project's documentation, Lighthouse has audits for performance, accessibility, search engine optimisation and more. The accessibility part gives a score out of 100. The documentation says this score is a weighted average of all accessibility audits, and that the weighting is based on axe user impact assessments. So the two tools are closely related.
The rule list in the axe-core repository shows the kind of thing a machine can test:
| What the tool checks | What a person must still judge |
|---|---|
| Text and background colours meet the minimum contrast ratio | Whether the text is comfortable to read in sunlight on a mid-range phone |
| Every image has alternative text | Whether the alternative text describes the image correctly |
| Every form field has a label | Whether the label is clear to a first-time user |
| Buttons and links have text that can be read aloud | Whether "Click here" tells the user where the link goes |
| The page has a title and a language set in code | Whether Bengali or Hindi text is marked and read correctly |
| Touch targets have enough size and space | Whether a thumb can reach the button while holding the phone in one hand |
How can a non-developer run an automated accessibility check?
A non-developer can run a Lighthouse accessibility audit from the Chrome browser on a laptop, with nothing extra to install. Google's documentation gives these steps:
- Open Chrome and go to the page you want to check.
- Open Chrome DevTools. DevTools is the panel of developer tools built into Chrome. A right click on the page and then "Inspect" opens the panel.
- Click the Lighthouse tab.
- Click "Analyze page load". DevTools shows a list of audit categories.
- Leave the categories enabled and run the audit.
- Wait. The documentation says the report appears after 30 to 60 seconds.
The same documentation lists other ways to run Lighthouse: PageSpeed Insights, the command line, a Node module and a Chrome extension. For axe-core, Deque offers a browser extension called axe DevTools for Chrome. Check Deque's own page for the current terms before you install the extension.
Do not scan only the home page. Scan 3 to 5 pages that matter for money: the home page, one service page, the enquiry form, the login page and the payment page.
How should you read a Lighthouse accessibility audit?
Read the list of failed audits first and the score last. The score is a summary, and the failed audits are the work.
Two details from the documentation help here:
- Each Lighthouse accessibility audit is pass or fail. A page gets no points for partly passing an audit. One unnamed button out of 40 fails the whole audit for button names.
- According to the axe-core README, the engine returns some elements as "incomplete" where it could not be certain, and manual review is needed. In the report, treat such items as open questions, not as passed.
The Lighthouse report groups its findings under headings such as Contrast, Names and labels, Navigation, and Tables and lists. I would send the "Names and labels" group to the developer first, because missing names block screen reader users completely. Contrast and touch target problems come back to the designer. On a real project I would fix the contrast in the colour styles of the design file, so that one correction repairs every screen. My article on colour contrast in UI design explains how those colour pairs are chosen.
Why do automated tests find only part of the problems?
Automated tests find only part of the problems because a program can check that something exists, but not that it makes sense. Both projects say this openly.
- The axe-core README says that with axe-core you can find on average 57% of WCAG issues automatically. The same README says the engine aims to return zero false positives. So the engine reports only what it can be sure about, and stays silent on the rest.
- The Lighthouse report carries its own warning in the accessibility section. The text says that automatic detection can only detect a subset of issues and does not guarantee the accessibility of a web app, and that manual testing is also encouraged.
- Lighthouse also lists manual items, with the note that these items "address areas which an automated testing tool cannot cover". The manual items include logical tab order, focus traps, and labels and roles on custom controls.
Here is what automated tests miss in practice. An image has the alternative text "IMG_2031". The check passes, and the screen reader user learns nothing. An error message says "Invalid input" without saying which field is wrong. A One-Time Password (OTP) screen gives too little time to a person who types slowly. A popup opens and the keyboard focus stays behind the popup. No scanner will flag these problems reliably.
What should a person review by hand?
A person should review the main task of the site from start to finish, using a keyboard, a screen reader and large text. This review takes about 20 minutes for one flow.
- Keyboard only. Put the mouse away. Press the Tab key through the page. You should always see where the focus is, and the order should follow the visual order.
- Screen reader on a phone. Turn on TalkBack, the screen reader built into Android phones. Try to complete the enquiry form with your eyes closed.
- Large text. Increase the font size in the phone settings. Check that no text is cut off and no button moves off the screen.
- Colour alone. Check that errors and required fields are not shown only by a red colour.
- Words. Read every label, error message and alternative text aloud. Ask whether a first-time user would understand each one.
The strongest review is still a session with real users who have disabilities. My guide to usability testing on a small budget shows how to arrange such a session without a lab. The wider design principles are in my guide to accessibility in app and web design, so I will not repeat them here.
What is a realistic plan for a small business this week?
A small business can complete a first accessibility check in one week without buying anything.
- On day 1, run Lighthouse on 3 to 5 key pages. Save each report.
- On day 2, copy every failed audit into one sheet. Add the page name and the screen area.
- On day 3, do the 20-minute hand review on your most important form. Add the findings to the same sheet.
- On day 4, mark each row as "design" or "code". Contrast, focus styles, label wording and touch target size are design decisions. Missing names and wrong code structure are developer fixes.
- On day 5, fix the form first. A form that everyone can complete brings enquiries.
If the site also has other usability problems, a full UX audit checklist covers the rest. Form problems in particular are covered in my guide to form design best practices.
What are the limits and risks of automated checks?
The main risk is false confidence: a clean report feels like a finished job, and it is not.
- A score is not a certificate. A score of 100 means the automated audits passed. It does not prove that a blind user can book a class.
- A scan sees one state of one page. Screens behind a login, open menus, popups and error states need their own checks.
- These tools are for web pages. The axe-core README speaks of websites and other HTML-based user interfaces. A native Android or iOS app needs other testing methods.
- A report is not legal proof. I cannot say whether a site meets any law. Ask a qualified professional for that.
- Tools change. Rules are added and removed, so two scans a year apart can give different results.
A machine can count missing labels in seconds, and that speed is valuable. Deciding what a label should say, in which language, for which user, remains human work. If you would like your website or web app designed with these checks built into the process, my UI/UX design service covers that.
Sources
Frequently asked questions
Is a Lighthouse accessibility score of 100 enough?
No. A score of 100 means the automated audits passed. The Lighthouse report itself says automatic detection can only detect a subset of issues, so a person must still test with a keyboard and a screen reader.
What is the difference between axe-core and Lighthouse?
axe-core is an accessibility testing engine from Deque that other tools build on. Lighthouse is a Google tool that audits performance, accessibility and search optimisation, and its accessibility score is weighted using axe user impact assessments.
Can I check accessibility without a developer?
Yes. Open the page in Chrome, open DevTools, click the Lighthouse tab and run the audit. Google's documentation says the report appears after 30 to 60 seconds.
Do axe-core and Lighthouse test mobile apps?
They test web pages and other HTML-based interfaces. A native Android or iOS app needs other methods, including hand testing with the screen reader built into the phone.
Working on something like this?
Tell Tithi what you are planning. You get a clear scope, a fixed price and a timeline before any work begins. I reply to every enquiry within 24 hours.