Understanding the Lighthouse Accessibility Score
Website intelligenceUnderstanding the Lighthouse Accessibility Score
Accessibility is broader than a score. A Lighthouse accessibility result can help identify selected technical issues, but it cannot fully judge whether every visitor can understand and use a website.
Read the score as a set of automated checks
Lighthouse can test selected accessibility rules in the rendered page. These checks may identify issues such as missing accessible names, contrast problems or structural patterns that deserve attention.
An automated score cannot assess every user journey or every interaction. A page may pass many automated checks and still be confusing or difficult to operate with a keyboard or screen reader.
Use the SiteBoost report as a starting point
When a Lighthouse accessibility result is available in SiteBoost, check the source label and report status. Use the score to decide which pages need a deeper review, then inspect the actual issue details in the browser's accessibility tools.
Keep the page's purpose in mind. A form, dashboard and long-form article have different interaction needs, so test representative page types instead of assuming one score covers the whole website.
- Test keyboard navigation and visible focus.
- Check form labels and error messages.
- Review meaningful image alternatives.
- Use a screen reader for key visitor journeys.
Verify fixes with people and repeat tests
After correcting an issue, test the exact interaction that previously failed and rerun the relevant audit. Record both automated results and manual observations.
Do not claim a website is fully accessible based on one automated score.
