Docs SEO
Lighthouse accessibility and best practices
Uses Google Lighthouse's accessibility and best practices scores from a mobile PageSpeed run. Both count toward the SEO score.
What it checks
These two checks come from the same mobile Google PageSpeed Insights run as the speed results. We take Lighthouse's Accessibility and Best practices category scores and show them out of 100.
Both count in the SEO score, not the Speed score: accessibility with weight 3, best practices with weight 2. If PageSpeed does not return a result, these checks are not shown and do not count. The performance score from the same run is covered in PageSpeed performance.
- Pass90 or higher.
- Warning50 to 89.
- FailUnder 50.
Why it matters
The accessibility audits catch problems that stop people using the site: text that is hard to read against its background, buttons and form fields with no label, images without alt text, headings out of order.
The best practices audits catch errors in the browser console, outdated browser features, insecure requests and images shown at the wrong shape.
Automated audits only find some accessibility problems, so a high score is a good start, not proof that the site works for everyone.
How to fix it
Run PageSpeed Insights or the Lighthouse panel in Chrome's developer tools and open the failed audits. Each one lists the elements involved. Fix the ones that repeat across the site first, such as colours in the theme, the header or the footer.
Platform notes
Many issues come from the theme or from plugins and apps. Check whether an update fixes them before editing theme code.
Contrast and labels are mostly in your hands: text colours, button text and form field labels in the editor.
Your report shows what this check found on your site. Pro shows the exact fix for your site. See pricing.
Free, about 30 seconds, with every other check included.