Skip to main content
Independent VPAT review

Independent review of vendor accessibility claims.

Vendors document their own accessibility conformance. We review those reports against the standard your solicitation names — identifying uncovered criteria, unsupported conformance claims and missing test evidence — and return a dated assessment you can put in the procurement file.

Every applicable criterion reviewed Claims checked against stated evidence Dated, documented, defensible

From $650/year.

Under most agencies’ informal purchase threshold — no solicitation, no three quotes. Quoted in writing, W-9 and certificate of insurance on request.

Independently reviewed
Dated for the file
Acme Permitting Cloud
VPAT 2.5
C
Overall
Proceed with caution — request clarification before award.
Level A criteria falling short3
Never addressed12
Claims we dispute2
Reviewed against WCAG 2.2 AA · Example
The clock was reset — not stopped
April 26,
2027 / 2028.

The DOJ’s ADA Title II web rule sets a hard compliance date for public websites and mobile apps — 2027 for populations of 50,000+, 2028 for smaller jurisdictions and special districts. The extension is your window to do this properly, not a reason to wait.

The DOJ says it “fully anticipates implementing the regulation at the new deadline.”
01
Months, not weeks
A full audit-and-remediation cycle takes months. Start now and you control the timeline.
02
A scan isn't enough
The DOJ itself cited the limits of automated and AI tools — automation alone won't satisfy the standard.
03
~50 criteria
WCAG 2.1 AA has roughly 50 success criteria; most can't be confirmed by automation.
04
Time is the variable
Entities that start early manage remediation on their own schedule. Those that wait do it under a complaint.
When a review is warranted

Conformance reports are written by the party selling the product.

That is how the VPAT format is designed to work, and it is not a criticism of vendors. It does mean the receiving agency carries the burden of assessing whether a report substantiates what it claims.

A vendor sent a VPAT and nobody on your team can tell you whether it’s any good.
?It claims “Supports” on everything — with remarks that say nothing at all.
!You’re past your ADA Title II deadline and need to know what you already bought.
The report is three years old, or covers a version of the product you aren’t buying.
You’re a vendor who’d rather find the gaps yourself than have an agency find them.
If any of these apply, request a review.
Request a quote →
Conformance report review

An independent read of what the report actually documents.

An Accessibility Conformance Report is a self-disclosure by the vendor, and the format gives them wide latitude in how much they explain. Few procurement teams have the time or the specialist background to tell a thorough report from a cursory one. We provide a documented assessment for the procurement file.

  • A dated assessment with an overall grade and a clear recommendation.
  • A plain-English summary of what the product does and doesn’t support.
  • A findings list — the specific things that should give you pause.
  • A procurement-ready memo you can drop straight into the evaluation file.
Request a review →Two business days · we set up your account
C
Acme Permitting Cloud
Vendor VPAT 2.5 · vs WCAG 2.2 AA · Proceed with caution
What the review found
Level A criteria falling short31.1.1, 1.3.1, 2.1.1 — the floor for basic use.
Claims we dispute2Marked Supports over a remark describing a gap.
Never addressed12Criteria the report does not mention at all.
Marked not applicable22Excluded from the grade rather than scored.
Red flags
  • 9 criteria claim full support with no explanation.
  • Forms only “Partially Support” 1.3.1 & 3.3.2.
  • No tester or testing method named.
  • PDF / document accessibility never addressed.
Who we work with

The same review, from either side of the procurement.

Agencies need to establish whether a vendor’s conformance claims are substantiated. Vendors need to know how their report will be assessed before they submit it.

If you buy software

Assess what you have already procured.

Every vendor conformance report on file, reviewed against the standard your contracts specify, so that gaps are identified on your schedule rather than in a demand letter.

  • Every criterion checked, not a spot sample
  • “Supports” claims tested against their own remarks
  • A prioritized list of items to raise with each vendor
  • Version history, so you can see what a vendor fixed
For agencies →
If you sell it

Review your report before submission.

Have the report you intend to submit reviewed the same way the receiving agency will review it, so that any gaps can be addressed or explained in advance.

  • Graded against 508, WCAG 2.1/2.2, EN 301 549 or INT
  • Every claim with no evidence behind it, flagged
  • The criteria your report never addressed at all
  • The questions a procurement reviewer is likely to raise
For vendors →
How a report becomes a review

Software reads it. A person signs it.

An automated read is fast, thorough, and occasionally wrong in ways that matter — it can miss a disclosed keyboard failure, or flag a clean row because of one word. That is a fine place to start a review and a poor place to end one, so every report is checked by a reviewer before you ever see a grade.

1

You send the report

Upload the file, or paste the address the vendor publishes it at. PDF, Word or HTML.

2

What the software does

Automated read

  1. Every criterion read

    The vendor's own table, row by row — conformance level, and the remark behind it. Nothing sampled.

  2. Claims checked against their own words

    A row marked “Supports” whose remark describes a keyboard failure is found and quoted back.

  3. Silence counted as silence

    Criteria the report never mentions are listed by name. Unanswered is not passing.

3

What a person does

Independent review

  1. A reviewer reads the draft

    Every finding, against the source document. What the software flagged, and what it may have missed.

  2. Findings corrected or confirmed

    False flags removed, missed disclosures added. The draft is an opinion until a person agrees with it.

  3. Published with their name on it

    The report reaches your vault signed, dated, and defensible in a procurement file.

4

You get the review back

Grade, findings, the criteria nobody answered, and what to put to the vendor — with the reviewer’s name on it.

2

business days

What each approach establishes

Receiving a conformance report is not the same as assessing one.

What an in-house review, accepting a vendor’s report as submitted, and a GOVvpat review each establish.
What you’re really gettingReviewed in-houseAccept as submittedGOVvpat
A named reviewer signs off before you see itNoNoYes
Tells you which criteria were never addressedNoNoYes
Checks “Supports” claims against their own remarksNoNoYes
Flags “Not Applicable” with no justificationNoNoYes
Catches a report written to the wrong editionPartlypartlyNoYes
Names the testing method and assistive tech usedNoPartlypartlyYes
Tracks whether the next version actually improvedNoNoYes
Written by someone without a deal on the lineYesNoYes

Most of what matters in a conformance report is what it doesn’t say — criteria left out, claims with empty remarks, an edition that doesn’t match your contract. Those are invisible unless someone checks the document against the standard line by line.

What a review catches

What a review catches that a read-through doesn’t.

Conformance reports rarely contain false claims. They contain omissions — criteria never addressed, support claimed without evidence, an edition that answers a different question. Those are the things we go looking for.

81

chapter requirements

Beyond the success criteria

Section 508 and EN 301 549 ask for more than WCAG: whether the product works without vision or hearing, whether it reaches assistive technology through the platform, whether the support documentation is itself accessible. An INT review checks 81 of those on top of the criteria table. A report can answer every criterion and still not answer the standard you named.

4

editions, checked against yours

The wrong edition is caught

A WCAG-edition report does not answer a Section 508 solicitation, however good it is. We read which edition the document declares and say plainly when it cannot answer the standard your procurement language names.

0

credit for silence

Absence is reported as absence

A criterion the report never mentions is unanswered, not passing. The grade is capped by how much of the standard the document actually addresses, so a thin report answering a dozen criteria cannot score well on the strength of what it left out.

Large reports repeat criteria across platform or standard tables, and the answers do not always agree. We take the least favorable reading and flag the disagreement by reference, so you can ask the vendor which one is true rather than discovering it later.

A flat “Supports” whose remark says “in most instances”, or “planned for a future release”, is a partial answer wearing a pass. It is invisible if you read only the conformance column, so we read the remark against the claim.

You can ask the report questions and get the vendor’s own words back, quoted. Ask about something it does not address and it says so rather than filling the gap — it answers from that document alone.

Proven against real reports, not sample ones.

The reader is validated against 21 conformance reports published by national GovTech and mapping vendors — with 1,004 rows checked line by line against the source documents. It reads PDF, Word and HTML, including the permission-locked PDFs some vendors publish.

When it cannot read a document, it says so and refuses to grade it. A number nobody can trace back to a table is worth less than no number.

Standards we review against

One template, four editions. We review against the one your solicitation names.

A report written to the wrong edition is one of the most common and most easily missed gaps — a WCAG 2.1 report submitted against a 2.2 requirement, for instance.

Section 508
U.S. federal & federally-funded

The edition most often specified by U.S. federal agencies and recipients of federal funding.

WCAG
2.1 / 2.2, the global baseline

Conforms to the Web Content Accessibility Guidelines (also ISO/IEC 40500) — the standard most others build on.

EU / EN 301 549
European public procurement

The European Union's accessibility requirements, specified in EU public-sector procurement and under the EAA.

INT
Multi-jurisdiction procurement

The combined edition — 508, WCAG and EN 301 549 in a single document — used where a product is procured across jurisdictions.

Also coveredWeb applications, mobile applications (iOS and Android), software, and published PDF documents.
Why us

We know procurement from the inside.

We come from public-sector IT and procurement. We know how a city buys, what an ADA Coordinator actually needs in the file, and how to write a read that survives scrutiny.

We review these the way a procurement office must: against the language in the solicitation, with attention to what a report does not address.

Independence, in writing

We do not author conformance reports. We disclose any prior relationship with a vendor under review, and we will decline a review where one exists.

Computer Systems Plus also publishes CivicCA and SentraCheck. GOVvpat reviews vendor products you are procuring; SentraCheck remediates documents you already own. Where a review touches a product that competes with one of ours, we disclose it on the face of the assessment and you may decline the finding.

Annual license

One license, every vendor you buy from.

Accessibility review is not a one-off purchase — vendors arrive with every solicitation, and the ones already on file reissue their reports. The license covers the portfolio for the year, so the cost of checking one more vendor is never the reason a check gets skipped.

From $650

per year — a license, not a per-report fee. Quoted in writing before anything starts, and it does not move because you sent one more vendor than you expected.

  • Every vendor report you send, reviewed and published to your vault
  • Re-review when a vendor issues a revised report, compared against the last
  • The portfolio view: which vendors are weakest, and what to chase first
  • Exports for the procurement file, and the findings written for the vendor

Buyable without a solicitation. Most agencies set an informal purchase threshold between $5,000 and $25,000 for professional services. An annual license sits well below it, which means a purchase order or p-card rather than a competitive process. We provide a W-9, certificate of insurance, and a written quote on your form if your finance office needs one. Sole-source justification language available on request.

How pricing and procurement work →
How many vendors

The vendors already on file, plus the ones arriving with each solicitation through the year. Volume sets the tier.

Which standard

Section 508, WCAG 2.1 or 2.2 AA, EN 301 549, or the combined INT edition — whichever your procurement language names.

How many seats

Procurement, IT and legal usually all want in. Seats are part of the license, not billed per person.

Request a quote

Quotes go out the same business day. If a review isn’t warranted for what you’ve described, we’ll tell you that instead.

Questions

Common questions from agencies and vendors.

What exactly is a VPAT?+
A Voluntary Product Accessibility Template — a standardized document in which a vendor reports how their product conforms to WCAG 2.1/2.2 AA, Section 508, or EN 301 549. The filled-in version is called an Accessibility Conformance Report. Crucially, it is self-disclosed by the company selling the product.
Do you write VPATs?+
No. We used to, and we stopped. A VPAT is the manufacturer’s own statement about their own product — we’d rather be the party that reads it critically than another author of one. If you need a VPAT written, we’ll point you at firms that do that work well.
Do you certify compliance?+
No. There is no accreditation body for WCAG or Section 508 conformance, and no certificate that establishes ADA compliance. What we produce is a dated assessment of a specific report against a named standard — evidence you did diligence, not a seal of approval.
Is this legal advice?+
No. Our assessments are technical, risk-reduction tools that describe a report as reviewed, on the review date, against the named criteria — not legal advice and not a guarantee against litigation.
Which editions can you check against?+
VPAT 2.5 in any edition your procurement language names: WCAG 2.1 or 2.2, Section 508, EU (EN 301 549), or the combined INT edition. If a vendor sends a WCAG 2.1 report and your contract says 2.2, that gap is one of the first things we flag.
Who actually reviews it — software, or a person?+
Both, in that order. Software reads every criterion in the vendor's table, checks each conformance claim against the vendor's own remarks, and lists the criteria nobody answered. A reviewer then works through that draft against the source document before anything is published — removing false flags, adding what the software missed. The published review carries the reviewer's name. Nothing reaches you ungraded by a person, which is why it takes two days rather than two seconds.
How long does a review take?+
Two business days from when we receive the report — or we tell you at intake that we can't, rather than missing it at the end. Weekends are not counted, so a report sent on Friday afternoon comes back Tuesday afternoon. You will see the exact date and time in your vault as soon as the report is received. If you are working to a deadline, say so and we will confirm before you commit to it.
What does a review actually catch?+
Criteria the report never addressed. “Supports” claims whose own remarks describe a defect. “Not Applicable” with no justification. Missing test methodology or assistive technology. Reports covering a product version you aren’t buying. Most of it is what the document fails to say.
How current does a vendor’s VPAT need to be?+
Best practice is a refresh annually or after any significant product change. A report three versions behind tells you little about what you’re buying — staleness is part of what we grade, and we keep version history so you can see whether a vendor actually fixed what they promised.
Do you cover mobile apps and PDFs?+
Yes — we review conformance reports for web applications, native iOS and Android apps, and published PDFs. ADA Title II covers documents too, which is where vendor reports are most often silent.

Request a review of a vendor conformance report.

Whether you’re evaluating a vendor’s claims or checking your own before you submit them, it’s the same read — against the standard your contract actually names.