For web agencies
Accessibility reports your clients understand. Fixes your team can ship.
Check client sites against WCAG 2.2, send a report with your logo, give developers the exact fix for each issue found, and keep every site monitored. Built for agencies that manage many websites.
Turn accessibility into a service you can sell
Audit
Check a prospect's or client's site, then send a white-label report with an executive summary written for people who do not read code.
Fix
Your team gets the fix pack: code before and after, steps for WordPress, Shopify, Webflow and more, AI prompts, and export to GitHub or Linear.
Monitor
Scheduled rescans show what is new and what is fixed. Send a monthly report and offer accessibility as part of your care plan.
Everything an agency needs, in one workspace
White-label reports
Your logo and colours on PDF reports and share pages, with no AccessibilityBrief branding. Includes an executive summary and a WCAG evaluation report.
Every client in one place
Group sites by client, invite your team with roles, and choose which pages are scanned.
Daily rescans and alerts
Up to 30 sites with daily or weekly rescans. Email and Slack alerts only when something new breaks.
A developer workflow
Developer handoff links, GitHub and Linear export that updates instead of duplicating, a REST API, CLI and an MCP server for AI editors.
The laws clients ask about
A view for the European Accessibility Act, Germany's BFSG, the ADA and Section 508, and reports in English and German.
Pages behind a login
Scan member areas, checkouts and staging sites with a saved test login.
What your client and your developer receive
One real issue from a scan of Northwind Coffee, a fictional demo shop on WordPress.
The problem
Images missing alternative text · 4 elements affected
4 images have no text alternative. Screen readers announce the file name or skip the image, so blind users miss what it shows.
Who it affects, and which rule
Screen reader users · People with low vision
WCAG 1.1.1 Non-text Content (A)
How to fix it
- Decide whether the image conveys information (a product, a chart, a person) or is purely decorative.
- For informative images add an `alt` that says what the image communicates in context, in one short sentence – not "image of…".
- For decorative images use an empty `alt=""` so assistive technology skips them.
Where to click in WordPress
In the Media Library open each image and fill in "Alternative Text". In the block editor select the image block and edit "Alt text" in the sidebar. For decorative images tick "Decorative image" or leave alt empty.
How an agency uses it
Send the client a white-label PDF with your logo and a plain-language summary, give your developer a handoff link or export the issue to GitHub or Linear, and let the next scheduled rescan confirm it is fixed.
Images missing alternative text
CriticalBefore
<img src="/images/hero-roastery.jpg">After
<img src="/images/hero-roastery.jpg" alt="TODO: describe what this image shows">Replace the TODO with a real description, or use alt="" if the image is purely decorative.
Prompt for Cursor or Claude Code
Fix this accessibility issue in the codebase: Images missing alternative text – 4 element(s) affected. 4 images have no text alternative. Screen readers announce the file name or skip the image, so blind users miss what it shows. Standard: WCAG 1.1.1 Non-text Content (Level A) – https://www.w3.org/WAI/WCAG22/Understanding/non-text-content.html The selectors and HTML below come from the rendered page, so the source may be a component, template or CMS content rather than literal HTML. Search the codebase for the matching markup (class names, text, component names) and fix it at the source so every use is corrected. 1. Page: https://northwind.example/ Selector: img[src$="hero-roastery.jpg"] HTML: <img src="/images/hero-roastery.jpg"> 2. Page: https://northwind.example/ Selector: img[src$="ethiopia-guji.jpg"] HTML: <img src="/images/ethiopia-guji.jpg"> 3. Page: https://northwind.example/ Selector: img[src$="colombia-huila.jpg"] HTML: <img src="/images/colombia-huila.jpg"> 4. Page: https://northwind.example/ Selector: img[src$="kenya-nyeri.jpg"] HTML: <img src="/images/kenya-nyeri.jpg"> Steps: 1) locate each element, 2) make the smallest change that fixes it, 3) list the files you changed, 4) run the type-check/lint/tests if available. Expected outcome: every informative image has a meaningful `alt` and decorative images have `alt=""`, for the listed elements and any others with the same problem. Don't change the visual design or any other behaviour beyond what is needed for this fix.
Generated by AccessibilityBrief's fix engine for the demo shop, exactly as a customer would see it.
Plans for agencies
Prices in USD. Payments by Paddle; 14-day refunds.
Launch offer: 50% off your first payment with code LAUNCH50.
Pro
For small teams
$49 / month
- 5 sites, daily rescans
- 3 team seats
- API, GitHub, Linear, Slack and MCP
Agency
For agencies
$149 / month
- 30 sites, daily rescans
- 10 team seats
- White-label reports and clients
- Everything in Pro
Questions agencies ask
Can I put my own logo on the reports?
Yes. On the Agency plan, PDF reports and share pages carry your logo and colours, with no AccessibilityBrief branding.
Do my clients need an account?
No. You send them a share link or a PDF. Developers can get a handoff link with the fixes, also without an account.
Can you scan staging sites and pages behind a login?
Yes. Pro and Agency can scan pages behind a login with a saved test account, such as a member area or a staging site.
Does it add a script or overlay to client sites?
No. AccessibilityBrief never adds anything to a site. Your team makes the fixes in the site's own code and content.
Does a clean scan mean a site meets WCAG?
No. Automated tests find only part of what WCAG covers. Every report includes a manual checklist so your team can test the rest, which is also a service you can offer clients.
Start with one client site
Run a free check on a client's home page and see what you would send them.