White-label accessibility reports for agencies

Updated 2026-10-24 · Altlark guides

If you build or maintain websites for clients, accessibility questions are probably already reaching you: a client heard about a new rule, a procurement form asks about WCAG, or a customer emailed because they couldn't use the contact form. A recurring accessibility report is a straightforward way to show you're watching for issues, catch regressions after content edits and plugin updates, and turn fixes into scoped, billable work.

This guide covers what a useful client-facing report contains, how to describe its scope honestly, and how Altlark's agency plans handle white-label reporting.

What a useful client report includes

• What was checked: the site, the number of pages, and the date.
• A trend: a score or issue count over time. Clients care most about direction ("down from 42 issues to 7 since March").
• Specific issues with locations: the page, the element and a snippet, so a developer can find it without guessing.
• Plain-English fixes: one line per issue type.
• Scope and limits: what automated checks cover and what they don't.
• Next steps: what you recommend fixing, and what needs manual testing.

Describing scope honestly

This matters for your reputation and your client's understanding. A few guidelines:

• Say "automated checks found these issues", not "the site passes" or "the site meets the law". Automated tools find some, not all, accessibility issues.
• Don't promise legal outcomes. Your report is an engineering document. If a client needs a legal view, they need a lawyer.
• Separate automated results from manual testing. If you also do keyboard and screen-reader testing, report it separately, with who tested and when.
• Keep the disclaimer. Every Altlark report includes one; leave it in when you forward reports.

Here's a short scope paragraph you can adapt:

This report lists issues found by automated accessibility checks on [N] pages of
[site] on [date]. Automated checks find some, not all, accessibility issues. They
don't cover color contrast, keyboard use, captions or the quality of text
alternatives, which need manual review. This is not legal advice or a certification.

Turning findings into work

Most automated findings cluster in templates, which makes them easy to scope:

<!-- footer.php: social icons, repeated on every page -->
<a href="https://facebook.com/client"><i class="fab fa-facebook-f"></i></a>

<a href="https://facebook.com/client" aria-label="Client on Facebook"><i class="fab fa-facebook-f" aria-hidden="true"></i></a>

One template change like this can clear an issue from every page of the site. A sensible way to package it for clients:

1. Baseline: first full scan, a short summary, and a fixed-price template pass for the common errors (page language, empty links and buttons, form labels, logo alt text).
2. Monitoring: monthly or quarterly report showing the trend and any new issues.
3. Manual review: an optional add-on for key tasks (checkout, booking, forms) with keyboard and screen-reader testing.

How Altlark's agency plans work

• Agency: $99/month for up to 25 sites. Agency Plus: $199/month for up to 75 sites. Each site is scanned up to 100 pages, daily.
• Alerts: an email when new issues appear on any site, with a link to the report.
• Dashboard: a private dashboard link listing each site with its latest score, errors and warnings, new issues, a score trend for the last 14 scans, and a link to each full report.
• White-label: on agency plans, reports and the dashboard show your agency's name at the top instead of Altlark's navigation, and the footer reads "Report generated with Altlark." Email support@deadlinkpatrol.com with the name you want shown after you subscribe.
• PDF: print any report or the dashboard to PDF from the browser; the print layout hides navigation and forms.
• Sharing: report and dashboard links are private but unguessable, so anyone with a link can view it. Share them only with the client.

See pricing for the payment links. At checkout you list the sites to monitor; if your list doesn't fit, email support@deadlinkpatrol.com and we'll add the rest.

Prospecting with the free scan

The free scan is one page, no signup, and you can run it on any public site you're working with. It's a quick way to show a prospect specific, fixable issues on their own site. Keep the tone factual: point at the element and the fix, not at fear. "Your contact form's email field has no label, so screen-reader users can't tell what to type; here's the fix" is more persuasive, and more honest, than any statistic.

Limits to tell clients about

Altlark reads server HTML without running JavaScript, so issues inside JS-rendered widgets (chat, some booking tools, cookie banners) aren't scanned, and contrast and keyboard checks aren't included yet. Include those in manual review if they matter for the client.

Checklist

1. Run the free scan on two or three client home pages to see typical findings.
2. Pick a plan by number of sites.
3. Send the first report with a scope paragraph and a fixed-price template pass.
4. Report the trend monthly; re-scan after every theme or plugin update.