Skip to content
A11yRemedy home
Run a free scan

The platform

What happens after you add a site.

How A11yRemedy finds your pages, tests them, turns the results into fixes a developer can apply, and keeps checking. No script on your site, nothing to install.

Start free Scan a page free

How a scan works

Three steps, every time a scan runs.

The same process runs on a schedule, when you press "Run all scans", or when your pipeline calls the API.

01 · Discover

Find the pages

Pages come from the site's XML sitemap, or by following links when there isn't one, up to your plan's page pool.

  • Respects robots.txt
  • Pages behind a login on Studio and Agency

02 · Test

Test in a real browser

Each page loads in headless Chromium, so content built by JavaScript is tested the way visitors see it. axe-core then runs the WCAG checks.

  • WCAG 2.0, 2.1 and 2.2, Level A and AA
  • Best-practice checks reported separately

03 · Prioritise

Group and rank

Every failure is grouped by rule, ranked by impact on real users, and given an effort estimate, so the biggest wins come first.

  • Impact: critical, serious, moderate, minor
  • Effort: trivial, small, medium, large

What a finding looks like

Not a rule ID. A change your developer can make.

Every issue in the report comes in the same shape. This is one, as it appears in a real report.

  • What failed, and the standard behind itThe rule, a plain-English title, the WCAG success criterion and level, impact on users, effort to fix, and how widespread it is.
  • Exactly whereThe page and the CSS selector of the failing element, marked New the first time it appears.
  • The failing HTMLThe actual markup from the page, so there's no hunting for it.
  • A suggested fixCode a developer can review and apply, with the reasoning and the numbers behind it. We never change your site ourselves.

color-contrast

Elements must meet minimum colour contrast ratio thresholds

WCAG 1.4.3 (AA)SERIOUSEffort: small40 occurrences on 5 pages
yoursite.com/blog/·.post-card > .read-moreNew

Failing HTML

<a class="read-more" href="/blog/speed-tips/">
  Read more »
</a>

Suggested fix

/* Set this on the rule that styles this text, not inline. */
.read-more { color: #0d8163; }

Text #14c697 on #ffffff measures 2.20:1. WCAG 2.2 AA uses 4.5:1 for normal text. The suggested colour keeps the original hue and measures 4.84:1.

Showing 1 of 40 occurrences. The full list is in the CSV export.

Prioritised remediation plan

Know what to fix first.

Hundreds of issues usually come from a handful of rules. The plan groups them so one fix clears every page it touches, and puts the biggest impact for the least effort at the top.

WCAG A/AA issues
88
Critical
2
Serious
86
Best-practice
389
Example prioritised remediation plan, grouped by rule
RuleImpactEffortIssuesPages
labelCRITICALsmall21
link-nameSERIOUStrivial4623
color-contrastSERIOUSsmall405

From a real first scan: 88 WCAG issues came from 3 rules. Fixing link-name alone clears 46 issues across 23 pages.

Monitoring

It keeps checking after the first fix.

Sites change every week. A new plugin, a content edit or a redesign can undo months of work. Monitoring is how you find out first.

Scheduled scans

Each site has its own schedule. Run any site by hand after a deploy, or run them all at once.

  • FreeMonthly
  • Solo, Freelancer, StudioWeekly
  • AgencyWeekly, daily on 10 sites
  • Every planOn demand

A baseline, then changes

Your first scan is the baseline. After that, every issue that wasn't there before is marked New, and each site shows whether it is stable, improved or regressed, with a score and a trend over time.

Regression alerts

An email the moment a scan finds a new critical or serious issue, so you hear about it before your visitors, or your client, do.

Email: Solo and above · Slack: Studio and Agency

Activity log

Every scan, every change of status and every quote request, in one timeline. Useful when a client asks what happened and when.

Reports and documents

A report a developer can work from and anyone can read.

Every scan produces a PDF report. It states its own limits on the first page, and never presents itself as proof of compliance.

  • Executive summaryTotals by impact, whether this is the baseline, and the top three actions.
  • Prioritised remediation planEvery rule, ranked by impact and effort, with issue and page counts.
  • WCAG findingsEach issue with its page, selector, failing HTML and suggested fix.
  • Best-practice findingsImprovements beyond WCAG A and AA, kept separate so they don't inflate the count.
  • AppendixWhat was scanned, how, and what automated testing can't cover.

Also included: CSV and JSON export (Solo and above), an accessibility statement generator (Solo and above), and a VPAT® 2.5 starter template that needs manual review before use (Studio and Agency). See a sample report.

Branding

Free, Solo

Freelancer, Studio

Agency

Your logo, colour and name

Not included

Included

Included

Your own report footer

Not included

Included

Included

A11yRemedy name removed

Not included

Not included

Included

The automated-testing notice and the axe-core® attribution stay on every report, including white-label ones. Custom domains are coming soon.

When you look after many sites

Built to run a portfolio, not just one site.

For agencies, freelancers and in-house teams with several brands. Available on Freelancer, Studio and Agency.

Clients and sites

File every site under the client or brand it belongs to. The dashboard sorts by what needs attention this week: open critical issues, regressions and scans in progress.

Team roles

Owners, admins and members. Roles decide who can change sites, billing and team settings.

2 seats on Freelancer · 5 on Studio · unlimited on Agency

Pages behind a login

Test account areas, checkouts and member pages using a form login or session cookies. Login details are stored encrypted.

Studio and Agency

Quote requests

Anyone reading a report can ask for a scoped quote to fix what it found. The request lands in your workspace, for you to price. It isn't a purchase and it isn't a conformance record.

Integrations

Works with the tools you already use.

Get results into the places your team already works, instead of one more dashboard to check.

REST API Studio +

Trigger scans and pull issues, fix plans and reports with API keys. Scan from your deploy pipeline.

Slack Studio +

Regression alerts posted to the channel you choose.

CSV and JSON Solo +

Import every issue into Jira, GitHub, Linear or any tracker.

Email alerts Solo +

New critical or serious issues, sent to whoever needs to know.

PDF reports Solo +

A remediation report for every scan, ready to share.

Sitemaps All plans

Pages come from your XML sitemap, or by crawling when there isn't one.

Coming soon

WordPress plugin Soon

Scan results inside wp-admin. Still not an overlay: it reports, it doesn't change pages.

Chrome extension Soon

Check the page you're looking at in one click.

MCP server Soon

Scan results inside your AI coding tools.

Security and data

How we handle your data, and your clients' data.

Nothing on your site

We load public pages the way a browser does. No script, plugin or hosting access, and we never change a live site.

Separate workspaces

Each workspace's data is kept separate from every other workspace.

Encryption

All traffic uses HTTPS. Passwords are hashed, and stored website login details are encrypted.

Hosted in the EU

The app runs in Finland. A Data Processing Addendum is included, with Standard Contractual Clauses for transfers.

Read the Data Processing Addendum and the Privacy Policy.

See it on your own site. The first scan runs in minutes.

Free for one site, no card. Every paid plan has a 14-day free trial.

Start free Compare plans