Product
Monitoring that produces something you can send
Rampsight crawls a client site in a real browser, runs the axe-core engine against the WCAG 2.2 A and AA rules, and turns the result into a score, a located list of failures, a branded report and a publishable accessibility statement. 100 to 1000 pages per scan depending on your plan, every week, under your agency's name.
14-day free trial, no credit card, running on the Agency capabilities.
How a scan works
Six steps, all of them automatic after you add the site.
1
You add a site
One site is one origin — https://example.com and everything under it. A subdomain is a separate site.
2
The address is checked
Private, loopback and link-local addresses are refused, so a scan can never be pointed at an internal network.
3
A real browser crawls it
Chromium opens the home page and follows same-origin links breadth-first, up to your plan's budget of 100 to 1000 pages per scan. Off-origin links are never followed.
4
axe-core tests each page
The engine runs on the rendered page, restricted to the WCAG rule tags. A page that fails to load is reported, not silently dropped.
5
Findings are aggregated and scored
One row per violated rule across the whole crawl, then a 0–100 score and a letter grade weighted by severity and reach.
6
You are told, and so are your tools
An email in your language, a Slack message if you want one, Jira issues if you push them, and a report ready to send.
Scanning and coverage
What gets tested, and against which rules. The scope is deliberately narrow: a compliance report should carry requirements, not opinions.
A real browser, not a fetch
Every page is loaded in a real Chromium and tested after it renders. What we check is the DOM your client's visitors actually get, including whatever the site's JavaScript builds.
Breadth-first, same origin
The crawl starts at the site's home page and follows same-origin links breadth-first, so the pages people reach first are the pages covered first — up to 100 pages per scan on Starter, 300 on Agency and 1000 on Scale. When a site is larger than the budget, the report says so instead of implying full coverage.
WCAG 2.2 A and AA only
axe-core is restricted to the WCAG rule tags
wcag2a,wcag2aa,wcag21a,wcag21aaandwcag22aa— WCAG 2.2 levels A and AA, a superset of the WCAG 2.1 AA baseline that EN 301 549 references.The engine’s best-practice rules are excluded on purpose: they are not WCAG failures, and they would pad the report with things your client is not required to fix.
Scans on a schedule
Every monitored site is re-scanned automatically once a week. That is what turns a one-off audit into a service: you find out when a release breaks something, not when a customer complains.
Scans on demand
A Run scan button in the dashboard for the moment a fix ships, and the same scan can be triggered from the REST API — so a deploy pipeline can ask for one.
Nothing internal, ever
The scanner refuses private, loopback and link-local addresses, and a redirect that leaves the origin is recorded as an error rather than followed. A staging site behind your firewall is not something we can reach.
Findings you can act on
A list of failures is only useful if a developer can go straight to the element. Every finding carries the evidence.
One row per rule, not per element
Findings are aggregated by axe rule across the whole crawl: the impact (critical, serious, moderate or minor), the WCAG tags it maps to, how many pages it fails on and how many elements it affects.
The exact element
Each rule comes with located examples: the CSS selector, the HTML of the failing element and the engine's own fix summary. Up to 10 examples per rule and at most 3 from any single page, so the examples spread across the site instead of piling up on the home page.
Every page a rule fails on
The report lists the affected page URLs — up to 50 per rule, with the page count staying exact — so nobody has to guess whether a failure is one template or the whole site.
A score people without a WCAG background understand
0 to 100 with a letter grade from A to F, weighted by severity and by how much of the site each failure touches. Fixing a rule returns exactly the points it was costing.
History, not a snapshot
A chart of the last 12 scans per site. It is the fastest way to show a client that the retainer is doing something — and the fastest way to spot the release that undid it.
The rule, explained
Every finding carries the axe rule description and a link to the matching Deque University page, so the developer fixing it gets the reference documentation rather than our paraphrase.
Deliverables for your client
Two artefacts leave the product and go to the site owner: the report and the accessibility statement. Both carry your brand, never ours.
The white-label report
Your agency name, logo and brand colour, in your language: an executive summary with the score, the findings table, the located evidence, the methodology and an honest disclaimer. Send it as a link or as a PDF. See a full sample report.
A share link you control
The public report link is protected by a signed token, so only the people you send it to can open it. No login, no account for your client, nothing indexed by search engines.
A PDF for the people who want a PDF
The report is print-ready: A4 pages, one section per sheet, a repeating footer with your agency name, and the fix-guide URLs printed out because links are not clickable on paper.
The accessibility statement
The document your client has to publish, generated in English, German, French or Portuguese, following the EU model statement (Commission Implementing Decision (EU) 2018/1523): conformance status, non-accessible content, how the statement was prepared, and feedback contact details.
Hosted at a link the client can cite
Publish the statement at a public URL your agency controls and link it from the site's footer. Editing a published statement updates the public page as soon as you save it.
Four languages, chosen per agency
Reports, statements and notification emails go out in the language you set for your agency — English, German, French or Portuguese — independently of the language each of your people uses in the dashboard.
Automation and integrations
Monitoring only becomes a service when nobody has to remember to run it. Everything here is there so the work reaches your team where it already happens.
Weekly scans, plus a button and an endpoint
Each site is re-scanned automatically every week. You can also run a scan by hand from the dashboard, or trigger one over the REST API from a deploy script.
Email that says something happened
Notifications in your agency's language when a scan finishes, when a scan fails, and when a site's score drops compared with the previous scan — plus the billing ones: trial ending, trial ended, payment failed.
Slack alerts
Point a Slack incoming webhook at your agency and scan results land in the channel where your team already talks, with the score and whether it regressed.
Jira Cloud
Connect a Jira Cloud site and push a finding into your backlog as a single issue, with the affected pages, the element examples and the fix guidance in the description. One issue per finding, and never twice for the same one.
REST API v1
Read your sites, scans and issues, and start a scan, from your own tooling. Per-agency keys (up to 20 active at a time), 120 requests per minute per key on Agency and 300 on Scale. Read the API documentation.
Failures that stay visible
A page that returns an error, redirects off-origin or hangs is recorded as a crawl error instead of quietly vanishing from the count. A scan that dies is marked failed and you are emailed about it.
Your agency's brand
The whole point of white label is that the client never wonders who else is involved. We keep our name off everything they see.
Your name, logo and colour
Set them once in your agency settings. They are applied to every report and every accessibility statement, on screen and on paper, for every client.
Your own subdomain
Point a subdomain such as reports.your-agency.com at us with a single CNAME record, and reports and statements are served from your domain instead of ours. Included from the Agency plan up.
We stay invisible
Our name is absent from reports, statements, link previews and browser tab titles. The only place your client could learn about us is from you.
Team and access
An agency is more than one person, and the people who read reports are not always the people who pay the invoice.
Invite your team
Invitations by email, with two roles: admins manage the agency, billing, integrations and people; members work on clients, sites and reports. Roles can be changed and people can be removed.
A dashboard in each person's language
English, German, French and Portuguese, chosen per person. It is a separate setting from the language of your client deliverables, so a German-speaking developer can work on French reports.
Billing without VAT paperwork
Our merchant of record handles VAT and invoicing for you. The trial lasts 14 days with no card; after it, the account stays readable — reports and statements keep working — until you pick a plan.
What each plan includes
The monitoring itself — scans, findings, white-label reports and statements — is on every plan. What grows with the plan is capacity (sites, pages per scan, seats) and the pieces larger agencies need: your own report domain, the API and Jira. See the plans and prices.
On every plan
- Included: Weekly automated scans of every monitored site
- Included: Located findings: pages, selector, HTML snippet and fix guidance
- Included: Score, letter grade and the history of the last 12 scans
- Included: White-label reports as a share link and as a PDF
- Included: Accessibility statements in English, German, French and Portuguese
- Included: Email and Slack alerts when a scan finds new issues
- Included: Unlimited clients and unlimited end-client reports
| Capability | Starter€99 / month | Agency€299 / month | Scale€599 / month |
|---|---|---|---|
| Monitored sitesOne site is one origin. Clients are unlimited on every plan. | 10 | 40 | 120 |
| Pages per scanCrawled from the home page within the same origin; the report always states the sample. | 100 | 300 | 1000 |
| Team seatsMembers plus pending invitations. | 5 | 20 | Unlimited |
| Weekly automated scans | Included | Included | Included |
| Located findings with fix guidanceThe page, the element, the HTML and what to change. | Included | Included | Included |
| White-label reports, share link and PDF | Included | Included | Included |
| Hosted accessibility statementsEnglish, German, French and Portuguese. | Included | Included | Included |
| Email and Slack alerts | Included | Included | Included |
| Reports on your own domainreports.your-agency.com instead of ours. | Not included | Included | Included |
| REST APIRequests per minute per key. | Not included | 120/min | 300/min |
| Jira Cloud integration | Not included | Included | Included |
| Priority supportAn answer within one business day. | Not included | Not included | Included |
The 14-day free trial runs on the Agency capabilities with 5 sites, so you can try the custom domain, the API and the Jira integration before deciding which plan you need.
What we do not claim
Automated testing finds a real but partial share of the WCAG success criteria. Any vendor telling you otherwise is selling you a risk, so here is the honest boundary of this product.
Rampsight does not
- Not included: Certify, guarantee or ensure that a site is compliant
- Not included: Replace manual expert review or testing with assistive technologies
- Not included: Judge whether alternative text actually describes the image
- Not included: Tell you whether a custom widget really works with a screen reader
- Not included: Decide whether a page is understandable, or give legal advice
So what is it for
It finds the machine-detectable failures — the missing alternative text, the unlabelled form field, the contrast that is too low, the link with no accessible name — on every page, every week, and hands them to you located and prioritized. That is the layer that is cheap to keep clean and expensive to leave broken, and it is the layer a human reviewer should not be spending their day on. Every report we generate says this in writing, and the accessibility statement is worded accordingly.
Add accessibility to what you already sell
Set up your agency, add a client site and run the first scan today — the report is ready to send the same day. 14 days free, no credit card.