Step-by-Step Lighthouse Accessibility Test

Open Chrome version 128 or later on the work computer and load the target URL. Without this browser the full Lighthouse audit cannot start because alternative browsers do not provide the complete report.
Press F12, switch to the Lighthouse tab and select only the Accessibility category. Skipping this filter includes unnecessary performance and SEO metrics that dilute the accessibility focus.
Click Analyze page load and wait for completion. The tool needs 30 to 90 seconds depending on page size; aborting here produces no usable report.
Read the list of contrast and ARIA errors in the generated report. web.dev has documented since 2024 that automated scans detect only about 30 percent of actual barriers – manual follow-up with keyboard and screen reader remains necessary.
Export the JSON report via the download button and save it under the project name. Without export the dataset is lost on the next Chrome restart.
Compare the errors against the WCAG success criteria on web.dev. The page lists concrete techniques for color contrast checks; skipping this comparison often misses color values that only appear on certain devices.
Fix the critical points directly in the CMS or source code. A common mistake is leaving color contrasts at 4.2:1 after correction instead of the required 4.5:1 – the test must be repeated afterwards.
Run the same test a second time to measure the improvements. Omitting this repetition step makes it impossible to prove whether the changes are sufficient.

The automated test does not cover situational impairments that only become visible in real usage contexts. For a more detailed review including manual checks the free website check at https://log-sysdev.de/website-check can be used.

Open Chrome version 128 or later on the work computer and load the target URL. Without this browser the full Lighthouse audit cannot start because alternative browsers do not provide the complete report.
Press F12, switch to the Lighthouse tab and select only the Accessibility category. Skipping this filter includes unnecessary performance and SEO metrics that dilute the accessibility focus.
Click Analyze page load and wait for completion. The tool needs 30 to 90 seconds depending on page size; aborting here produces no usable report.
Read the list of contrast and ARIA errors in the generated report. web.dev has documented since 2024 that automated scans detect only about 30 percent of actual barriers – manual follow-up with keyboard and screen reader remains necessary.
Export the JSON report via the download button and save it under the project name. Without export the dataset is lost on the next Chrome restart.
Compare the errors against the WCAG success criteria on web.dev. The page lists concrete techniques for color contrast checks; skipping this comparison often misses color values that only appear on certain devices.
Fix the critical points directly in the CMS or source code. A common mistake is leaving color contrasts at 4.2:1 after correction instead of the required 4.5:1 – the test must be repeated afterwards.
Run the same test a second time to measure the improvements. Omitting this repetition step makes it impossible to prove whether the changes are sufficient.

Run a Lighthouse Accessibility Test for a Website

Run a Lighthouse Accessibility Test for a Website