ACCESSIBILITY · AUTOMATED EVIDENCE + HUMAN REVIEW
Website Accessibility / WCAG Audit
Find accessibility issues reported during one rendered Lighthouse page load. Separate automated findings from checks that still need a person.
No compliance certificate · No invented pass rate
Findings you can inspect
Review failed audits and bounded affected-element selectors. Missing evidence remains unknown.
Manual checks stay visible
Keep keyboard, screen-reader and real-task testing separate from automated results.
Source-labelled reports
See the device, measurement time and engine version. Export the report with its limits intact.
Automatic checks: source setup required
The tool is installed, but its shared Google PageSpeed connection is not enabled for lookups. The administrator can configure a PageSpeed Insights API key, or explicitly enable no-key attempts, under Web Performance → Page Weight Audit.
No paid subscription is added by this tool. Provider quota and a real report must still be verified; a live page is not a completed accessibility audit.
A score is not a WCAG verdict
Lighthouse evaluates an automated subset. Even 100 does not establish accessibility or WCAG conformance. A failed rule needs investigation; an unavailable or manual check is never a pass.
This run does not audit every page, log in, click menus, choose consent, submit forms or assess all interactive states.
Keep a human-review checklist
- Use only the keyboard to reach and operate navigation, dialogs, forms and controls. Check logical order, visible focus, focus return and absence of traps.
- Use a screen reader to check headings, landmarks, names, roles, states and announcements in real tasks—not only the initial page.
- Review text alternatives in context, meaningful reading order, instructions, error identification and recovery, captions and transcripts where applicable.
- Test zoom/reflow and narrow layouts without loss of content or functionality. Review contrast in all relevant states and over image backgrounds.
- Test menus, validation errors, consent states, authentication and other dynamic flows with permission. This tool does not click controls or submit forms.
Questions and limits
Does this certify WCAG compliance?
No. The report covers one automated Lighthouse navigation. A high score cannot prove accessibility or conformance. Human testing across pages, content and interactive states is essential.
How does the automatic lookup work?
Enter a public page URL and select mobile or desktop. The backend sends it to Google PageSpeed Insights and requests the Lighthouse accessibility category. No target JavaScript runs on this WordPress server.
Why might source setup be needed?
The existing shared PageSpeed connection has no API key and no-key attempts are disabled unless the administrator explicitly enables them. Google quota can be unavailable. A free PageSpeed API key can be configured in Web Performance; a stored key still needs a successful source test.
What do missing or manual results mean?
They are not passes. Missing results, provider errors and incomplete coverage stay visible. Manual checks require a person; not-applicable describes only the provider observation in this run.
Are affected-element examples complete?
No. The administrator limits examples per audit. Raw HTML, node text and nested related-node details are omitted; selectors may still identify public page content. A node row is not necessarily one unique accessibility defect.
What is stored or shared?
Your public URL and device are sent to Google. The module does not store reports or run scheduled crawls. Shared protection keeps usage counters. CSV and JSON are created in your browser; review exports before sharing.
Engine reference: open-source Lighthouse through Google PageSpeed Insights. Evaluation guidance: W3C WAI. No target JavaScript runs on WordPress.