Accessibility Testing for Agencies
Run accessibility for every client, one domain at a time. Each client site has its own plan, its own record and its own evidence, and the fixes you deliver live in the client’s code, with nothing injected into their pages.
- Passed. 1 · Sign-in form — labels announced
- Passed. 2 · Submit — error summary takes focus
- Passed. 3 · Dashboard — heading level 1 announced
- Serious. 4 · Search field — placeholder, no label
- Critical. 5 · Results — list replaced silently
- Not evaluated. 6–7 · not reached
Completed 3 of 7 stepsWCAG 4.1.3 · 3.3.2
Example output, produced by Accessible on a test site. Not a customer site, and no customer data is shown.
What does an agency need from an accessibility tool?
A way to show each client where their site stands today, what to fix first, and what changed after the work, without promising something no tool can deliver. Automated checks find some barriers, not all. The failures that cost clients orders and sign-ups usually appear only once someone uses the site with a keyboard or a screen reader.
Why per-domain pricing fits an agency
Each client domain carries its own plan, so a client's plan is a line item you can explain. Every paid plan has unlimited seats and no limit on URLs, and scanning is unmetered.
Journey runs draw on credits. Each domain uses its own allowance first, and an optional org credit pool can be shared across clients. Running three or more domains? Talk to us about Enterprise volume pricing.
Evidence you can hand to a client
A baseline in the first week
Scan every URL, then run a journey through the task the client cares about most, such as checkout, sign-up or booking. The journey report names the step where it stopped, what was announced, and the WCAG criterion it falls under.
A backlog your developers can work from
Issues are deduplicated across pages and ranked by severity, with fix guidance for each, and export to CSV for whatever tracker the client uses.
A record that shows the work
Activity reports, scan history and a public posture page show when the site was last tested and what changed. A draft VPAT/ACR is built from the site’s own evidence, per criterion, for the client’s team to review.
How agencies use Accessible
- Add a client domain. Install monitoring with one script tag, or start with a scan.
- Pick the tasks that matter. Journeys can work behind a login using a dedicated test account, never live credentials.
- Ship fixes, then re-test. Scans run weekly on every paid plan, and on every deploy on Professional and Enterprise.
- Report. Export the activity report or share the posture page with the client.
Scanning
Every URL on the client’s domain checked against WCAG 2.2 in a real browser, with a broken component grouped into one issue across every page it appears on.
How scanning worksJourneys
A simulated screen-reader user attempts a real task and reports the step where it could not continue, with the WCAG criterion and the fix.
How journey testing worksMonitoring
Real user monitoring ranks the barriers the client’s visitors meet by how many sessions hit them, so the fix list starts where people actually struggle.
How monitoring works
A diagnostic, never an overlay
Clients ask about accessibility widgets. Accessible doesn't install one and never changes the pages it tests, so every fix you deliver is in the site's own code, where it works for every visitor and every assistive technology.
What it does not do
- It doesn't certify anything. No score, report or badge is a compliance certificate, for you or your client. Accessible documents what was tested, found and fixed.
- It doesn't replace expert testing. Journeys simulate a screen-reader user in a browser; they don't use NVDA, JAWS or VoiceOver.
- It doesn't fix the site for you. It tells your team what to fix and shows whether the fix held.
Testing client sites is covered by our fair use policy.
Need help fixing findings?
Accessible tells you what to fix and shows whether the fix held. If you'd like a hand with the fixing, teams on a paid plan can ask our team for remediation help, from reviewing a client’s findings with you to taking on a defined piece of the work, scoped and quoted before anything starts.
Frequently asked questions
Can agencies use Accessible on client sites?
Yes, for sites a client has authorized you to test. Each client site is added as its own domain with its own plan, and the work you deliver to that client is covered by our fair use policy. Reselling scanning as a service of your own, or using Accessible as the backend for another product, is not.
Who holds the plan, the agency or the client?
Plans belong to an organization, and everyone in an organization can see all of its domains. So either your organization holds each client’s domain, or the client creates its own organization and invites your team to it.
Can I hand clients a report?
Yes. Every paid plan includes CSV export, an activity report, a draft VPAT/ACR and a public posture page for each domain. Reports carry Accessible’s format, not your branding, and none of them is a certification.
Is the free plan enough for an agency?
Monitor watches one domain per organization for free, with no card and no expiry, so it covers one client site rather than a portfolio. Scanning, journeys and reports start with a paid plan, and your organization’s first paid plan opens with a 7-day trial.
Does Accessible replace a manual audit?
No. It finds what automated checks and simulated screen-reader journeys can find, on every page and in real sessions, so an expert’s time goes to what only a person can judge.
Every client site, tested the way people use it.
Start with free monitoring on one client site, or see what a plan per client costs.