Web & tools4 min read
Running a Lighthouse Accessibility Test: How It Works and What the Score Leaves Out
Lighthouse in Chrome and Edge automatically checks a website for accessibility. How to start the test, read the report, and why a score of 100 does not yet mean an accessible page.
- #web
- #digitalisierung
- #organisation
Lighthouse is a testing tool from Google that comes built into Chrome. It checks a page for loading speed, search engine friendliness and accessibility, and gives each category a score between 0 and 100. For a first look at the accessibility of your own website, that is a good start. It is worth knowing what the score does and does not tell you, though, before celebrating a 100.
What you need
You do not need a particular Chrome version; Lighthouse has been part of the browser's developer tools for years. Microsoft Edge has the tool too, with the same settings (Microsoft guide). If you would rather not open anything in the browser, you can enter an address in PageSpeed Insights. It also runs Lighthouse, but device and categories cannot be chosen as freely as in the developer tools (Chrome documentation on Lighthouse).
One advantage of the developer tools is that they also test pages behind a login or pages that only run locally on your own computer, such as a new version of the website before it goes live.
Running the test
- Open the page you want to test, ideally in an incognito window. According to the Chrome documentation, browser extensions, stored cookies and local data can otherwise affect the result.
- Open the developer tools with Ctrl+Shift+I (Cmd+Option+I on a Mac), or right-click the page and choose "Inspect".
- Select the "Lighthouse" tab. If you cannot see it, it is behind the double arrow or the menu for more tools.
- Set the mode to "Navigation". This is the default and tests the page on a fresh load.
- For the device, choose "Mobile" or "Desktop". According to Microsoft, "Mobile" changes the browser's user agent and resizes the viewport, which can affect the results. If you want to know both, run the test twice.
- Under categories, tick only "Accessibility". The other categories do no harm, but they make the run longer and the report harder to read.
- Click "Analyze page load". The report appears shortly afterwards.
Reading the report
The score sits at the top. It is a weighted average of all automated accessibility audits, and each individual audit is either passed or failed (Chrome documentation on scoring). There is no partial credit: if just one of twenty buttons lacks an accessible name, the whole audit counts as failed. The weights come from the axe testing library's assessment of how much a problem affects users.
Below the score, the report lists the failed audits. Expanding an item shows the affected elements on the page and a link explaining the problem. Typical findings on small company websites:
- Insufficient contrast: Text does not stand out enough from its background. For normal text, WCAG requires at least 4.5:1.
- Images without alternative text: The screen reader cannot announce what the image shows.
- Buttons or links without an accessible name: often icons such as a magnifying glass or a menu symbol with no label in the code.
- Form fields without labels: The field has no linked text saying what belongs in it.
- Missing language attribute: The HTML document lacks the
langattribute, so screen readers cannot choose the right pronunciation.
You can save the report from the three-dot menu at the top of the Lighthouse panel. That is worth doing so you can compare later what changed after your fixes.
Fixing problems and testing again
Many findings can be fixed in the content management system without any coding: add alternative text, choose a darker font colour, label the fields in the form plugin. Missing names on icons or a missing language attribute, on the other hand, usually sit in the theme or the code and are a job for whoever looks after the website technically.
After making changes, run the test again with the same mode and device settings. Only then can the two reports be compared.
What a 100 does not mean
According to the Chrome documentation, audits that have to be done manually are not included in the score. Lighthouse can tell, for example, that an image has alternative text, but not whether that text describes the image sensibly. Nor does it fully check whether the menu can be used with a keyboard or whether the tab order is logical.
How much automated tests find at all depends on how you count. You often read that they detect only 20 to 30 per cent of barriers. That figure refers to the share of WCAG criteria that can be checked automatically. The testing tool vendor Deque instead analysed the issues actually found in first-time audits and concluded that just over 57 per cent could be detected automatically (Deque report). Deque sells automated testing tools itself, which is worth bearing in mind. Either way of counting shows that a considerable share of problems only surfaces in a manual check.
If you want to go further after Lighthouse, test the page with a keyboard and a screen reader. How to do that, and which legal duties apply to which websites in Germany, is covered in the post Accessible websites: who Germany's BFSG applies to.
Log-Studio, the web design brand of Log-System Development, the company that runs this blog, offers a free online check without registration at log-studio.de/website-check that measures loading speed, findability on Google, security and the technology behind a site; accessibility is not part of it. Being automated, this check does not replace testing with a keyboard and a screen reader either.
Read next
Web & toolsAdvertisement from Log-Studio (log-studio.de)
Browser DevTools for Your Company Website: Checking Speed, SEO and Accessibility Yourself
Browser developer tools show which files slow a page down, whether titles and descriptions are in place and where contrast is too low. What Network, Lighthouse and the rest can do, and where they stop.
Digitalisation
Matomo Instead of Google Analytics: What It Does and When It Needs Consent
Matomo keeps visitor data on your own server. In Germany that still does not automatically remove the need for a consent banner, except with log analytics. Versions, costs and setup at a glance.
Organisation
Digital Organization for SMEs 2026: Tools and Strategies Against Chaos
In 2026, digital organization is key for SMEs: Explore practical tools, AI integration, and web strategies that minimize daily chaos and boost productivity. From Notion to Fraunhofer insights – actionable for freelancers and small teams.