Lighthouse Accessibility ScoreWhat it checks and how to fix it

What it checks

Reads the Accessibility category score from a Lighthouse run on the page, simulating a mid-range phone. A score of 90 or above passes, 50 to 89 warns, and below 50 fails. It runs on the pages chosen for Lighthouse.

Why it matters

The score summarizes automated accessibility audits: missing alt text, unlabeled buttons and form fields, low color contrast, broken heading order and invalid ARIA. A low score means some visitors using screen readers or keyboards cannot use the page, and it points at failures of WCAG, the standard behind laws such as the ADA and the European Accessibility Act.

How to fix it

Open Chrome DevTools → Lighthouse, run an Accessibility audit on mobile and fix each failing audit; every one lists the elements involved. The most common fixes:

<img src="/images/team.webp" alt="Our support team at the office">

<button aria-label="Close dialog"><svg aria-hidden="true">...</svg></button>

<label for="email">Email</label>
<input id="email" type="email" name="email" autocomplete="email">

<html lang="en">

Also make text contrast at least 4.5:1 against its background, and keep headings in order (h1, then h2, then h3). Aim for 90 or more and re-run Lighthouse after each change.