VPAT® 2.5 conformance reports
VPAT® reports backed by real accessibility testing
A buyer asked for your VPAT? We test your website or web application against WCAG, can fix what fails, and write the Accessibility Conformance Report (ACR) from what we found.
- Tested, not guessed. Four automated engines, then a person with a keyboard and the NVDA screen reader checks what machines can't judge.
- WCAG or Section 508 edition, in the VPAT 2.5 format procurement teams expect, as a PDF and a web page.
- Honest conformance levels, each with a plain-language remark. Nothing says "Supports" unless testing shows it.
- Fix first, if you'd like. We can repair what fails before the report is written, so it describes a better product.
| Criterion | Conformance level | Remarks |
|---|---|---|
| 2.1.1 Keyboard (Level A) | Supports | Every control in both key flows works from the keyboard, including the mobile menu, carousel arrows, gallery controls and the contact form. |
| 1.4.3 Contrast (Minimum) (Level AA) | Supports | Text over photos and gradients was measured against the darkest and lightest pixels behind it, including hover and focus states. |
| 1.2.2 Captions (Prerecorded) (Level A) | Not Applicable | No video on the reviewed pages. |
Get a quote for an ACR
Tell us what the report is for: your site or app, who asked for it, which edition they want and any deadline. We'll reply by email with what we'd test, how long it takes and what it costs.
What's in the report
Every criterion, a conformance level and the reason for it
An ACR documents how your product meets an accessibility standard, criterion by criterion. Government agencies, universities and larger companies ask vendors for one during procurement.
WCAG edition
WCAG 2.2 Level A and AA, or 2.1 or 2.0 if your buyer names one. Each criterion is marked Supports, Partially Supports, Does Not Support or Not Applicable.
Section 508 edition
For US federal buyers: the WCAG 2.0 Level A and AA tables Section 508 uses for web content, plus its Chapter 3 functional performance criteria. See Section 508 testing.
How it was tested
The report names the pages, screen sizes and sign-in flows tested, the tools and their versions, and what a person checked by hand. A buyer can see what stands behind each answer.
How it works
From your buyer's request to a report you can send
Scope
We agree on the pages, key tasks and sign-in flows to cover, and the edition your buyer asked for.
You get: a fixed quote and a dateTest
Automated scans at desktop and phone sizes, then keyboard, screen reader, zoom and form testing by a person.
You get: a findings reportFix, if you'd like
We repair problems in your site's code and content, or hand your developers a fix sheet, then test again.
You get: a before-and-after reportReport
The ACR in the VPAT 2.5 format, dated, with every Level A and AA criterion reviewed by a person. Monitoring keeps it current when buyers ask for a newer one.
You get: an ACR, PDF and web
Before you get in touch
Websites and web apps
We test web content: public sites and web applications, including pages behind a sign-in. We don't evaluate hardware, desktop or phone apps, or documents such as PDFs.
No draft goes out
Until a person has reviewed every Level A and AA criterion, the report is marked a draft. You won't get a "Supports" we can't stand behind.
Evidence, not a certificate
An ACR describes your product on the date tested. It isn't a certification or a legal opinion, and no one can honestly sell you one that is.
VPAT® is a registered trademark of the Information Technology Industry Council (ITI). Trouble using the form? Reach us another way through our accessibility statement.