An Accessibility Conformance Report, written for you.
You have been asked for a VPAT or an ACR, and nobody on the team has the time to produce one. We test the product against WCAG 2.2 AA by hand and hand you the finished document: signed, dated, and naming the version it describes.
A fixed price, not an estimate. Delivered in 10 working days from the point the scope is agreed. The scope is agreed in writing before any work starts, so nothing is open-ended on either side.
Ask about a report Nothing is charged until you have agreed the scope.
Not sure what the finished document looks like? Open a complete worked example — a real page on this site, filled with illustrative figures and naming no real vendor.
What you get
- A WCAG 2.2 AA audit of the product, tested by hand. Automated scanners are the starting list, not the answer.
- The findings written up as a VPAT 2.5 Accessibility Conformance Report, criterion by criterion, Level A and AA.
- The remarks that make each row defensible, rather than a conformance level with nothing behind it.
- A named signatory, a date, and the product version the report was evaluated against.
- A public link you can send to a buyer, plus a print-ready copy for your own records.
- A written statement of what was tested, how, and what was out of scope.
What I need from you
Three things, and the first one is enough to start.
- A URL for the thing that needs the report. The page or the flow a customer actually reaches. A build or a written description works too, if it is not on the open web.
- A test account, if there is a sign-in. A working username and password. A real low-privilege account is more useful than an admin one, because it is what a customer sees.
- Your existing report, if you have one. So the new one can be compared against it rather than quietly replacing it.
Nothing needs to be uploaded, and there is no portal to sign up to. Please do not send screenshots or a spreadsheet of criteria; a URL is enough to begin, and anything else is asked for by name once the scope is agreed.
How it works
- You tell us what needs a report. The form below is enough. A URL, a build, or a description of what a user reaches. If you already have a report, mention it.
- We agree the scope in writing. Which surfaces, which standard, which version, and which date. You see this before anything begins, and the price does not move afterwards.
- We test by hand against WCAG 2.2 AA. Keyboard only, with a screen reader, at different zoom levels and text spacings. An automated scan is the starting list rather than the answer, because roughly two thirds of real issues never appear in one.
- You get the finished report. The document, a link you can hand to procurement, and a coverage statement that says exactly what was and was not examined.
What this is not
An ACR is an attestation, so it is worth being precise about its limits before you buy one.
- It is not a certificate of accessibility. It is a record of what was tested, when, by what method, and what the result was.
- It is not a fix. Remediation is separate work and is not included in this price.
- It does not cover what was not in scope. If a surface was excluded, the report says so rather than implying coverage it does not have.
- It will not say "conforms" for anything that was not tested. Where the answer is "partially supports" or "not evaluated", that is what it will say.
After the report
A report describes one version of a product. When you ship past that version it stops being accurate, and re-issuing it is a manual job with no deadline attached to it, so in practice it does not get re-issued.
If you would rather keep the record current in-house from then on, that is what the subscription is for: you maintain the record, and the public page reports when it no longer matches what you ship. There is no obligation to take it, and it is not needed to use the report you have just been given.
Questions
The things buyers ask before they send the form. If yours is not here, ask it in the notes field and it will be answered. Longer answers: how a VPAT differs from an accessibility audit and ACR costs and timelines compared.
What is the difference between a VPAT and an ACR?
A VPAT is the template. It stands for Voluntary Product Accessibility Template, it is published by the ITI, and it is a table with one row for each success criterion. An ACR, an Accessibility Conformance Report, is that template filled in and signed. People say VPAT when they mean the completed document, and most buyers accept either word. What you get here is a completed VPAT 2.5, which is an Accessibility Conformance Report.
How much does an ACR or a VPAT cost?
Fifteen hundred US dollars, fixed, per product. That covers the audit, the written report, the public link and the print-ready copy. It does not cover fixing anything the audit finds; remediation is separate work and is priced separately if you want it.
How long does it take?
Ten working days from the point the scope is agreed in writing. The clock starts when the scope is agreed rather than when the form is sent, because the scope is what fixes the amount of work. If you have a deadline, say so when you write and it will be answered honestly rather than accepted and then missed.
Do you test the product, or just fill in the template?
The product is tested. Keyboard only, with a screen reader, at different zoom levels and text spacings. An automated scan runs as well, but as a starting list rather than as the result, because most real failures never appear in one.
What do you need from us to start?
A URL for the thing that needs the report, and a test account if it sits behind a sign-in. If you already have a report, mention it so the new one can be compared against it. Nothing needs to be uploaded.
What standard is the report written against?
ITI VPAT 2.5, Level A and AA, evaluated against WCAG 2.2. If your buyer has asked for a particular edition or a particular standard, say so when you write and it will be named in the scope before any work starts.
Who signs it?
A named individual who did the work and accepts responsibility for it. A report with no human name on it is not an attestation, and a buyer is entitled to ask who stands behind the claim.
What if the honest answer is that we fail something?
Then that is what the report says. Where the answer is "partially supports" or "does not support", that is the answer it gives. A report that overstates its own coverage is worse than no report at all, because the buyer relies on it and you are the one who signed it.
Ask about a report
Tell us what needs a report and when you need it. You will get the scope, the fixed price and the delivery date back in writing, usually within one working day, and nothing is charged until you have agreed to it.
Would rather write in your own client? The form reaches support@accessrecord.app, and so does anything you send there.