Skip to main content

Report to clients Pro

Branded client reports

Reports with your logo and colors, covering all 55 WCAG 2.2 A and AA criteria, as a tagged PDF — plus CSV export of every finding.

A client report's WCAG 2.2 checklist, with each criterion marked Issues found, Needs review, No automated issues or Manual check needed.

Overview

Client reports lives under Accessibility → Reports. Create a report asks for a Report title, the Client name and an optional Note for the client, shown at the top of the summary. You choose whether to include Findings for each page and Tips. The form shows how many checked pages the report will cover, and warns when some content has not been checked yet, because unchecked items are left out.

Each report is a frozen snapshot of the stored results and your branding at that moment. It opens in a new tab with a Summary, the WCAG 2.2 checklist, Issues and how to fix them, Findings by page, Live page checks and Recommended next steps. When an earlier report exists, the summary says how the score and the error count changed since then.

To send it, press Save as PDF in the report toolbar and choose Save as PDF in the print dialog, or use Download HTML for a single self-contained file with the logo embedded. Branding comes from Accessibility → Settings → Branding. The report prints your logo or agency name, contact email, accent color and footer text, which also runs along the bottom of every printed page. Text on the accent color switches between black and white to stay readable, whatever color you pick.

Why it matters

Clients and managers do not read issue lists. They need a clear document that says where the site stands, what was found, how it has changed since the last report and what still needs a person — and an accessibility report that is not itself accessible is embarrassing.

What you get

  • Summary, WCAG 2.2 checklist of all 55 A and AA criteria, issues with fixes, findings by page, live page checks and next steps.
  • Each criterion marked Issues found, Needs review, No automated issues or Manual check needed — never a false "pass".
  • Your agency name, logo, accent color and footer text.
  • Tagged PDF straight from Chrome or Edge, plus an HTML download; earlier reports stay available to open again.
  • CSV export of every finding for spreadsheets and ticketing tools.

How it works

  1. Set your branding

    Add your logo, colors and contact details once.

  2. Generate a report

    Lumtera freezes a snapshot of the current results.

  3. Save as PDF and send

    Print to PDF from Chrome or Edge for a tagged, accessible document.

Who it helps

  • Agencies

    Send a monthly or quarterly report that shows where the site stands and how the score moved since the last one.

  • In-house teams

    Give managers a readable document instead of an issue list, including the criteria that still need manual testing and budget.

  • Public sector and procurement

    Keep a dated record of each automated review. The cover labels it as an automated review of WCAG 2.2 levels A and AA.

Good to know

How it behaves, what it needs, and where its limits are.

Plans and access
Included in every Pro plan. Creating and viewing reports needs the same permission as the Lumtera reports; editing branding needs an administrator.
No false passes
A criterion is never marked as passed. The best result is No automated issues, and criteria with no automated check are marked Manual check needed.
Limits
Findings by page lists up to 300 pages and says how many more have issues. The Reports list on the screen shows the 50 most recent reports.
What is not included
PDF results from the Documents screen are not part of the report. Live page checks appear only for public pages: a page whose post is unpublished or password-protected is left out.
CSV export
Export CSV on the Content report downloads one row per content finding, following the current filters, with the WCAG criterion, level, message and markup. Cells a spreadsheet would read as formulas are neutralised.

Questions

Something else on your mind? Contact support

Why print to PDF instead of generating one?

Chrome and Edge produce tagged PDFs with headings and reading order. Most PHP PDF libraries do not — and an accessibility report should be accessible.

Does the report say my site is compliant?

No. It shows what automated checks found and which criteria still need a manual check. That honesty is what makes it credible to clients.

If I change my logo, do old reports change?

No. Each report keeps the branding it was created with, so what the client received stays on record.

Can my client open the report in WordPress?

Reports are stored privately and are not public web pages. Viewing one in WordPress needs an account that can see the Lumtera reports, so clients normally get the PDF or HTML file you send.

More in “Report to clients”

Start with the free plugin today

All 64 checks, the editor sidebar, Elementor panel and site report — free, with no account and no page limits.