Services · By situation
Procurement and RFP Audit: Evidence by the Bid Deadline
For the vendor mid-bid whose RFP asks for accessibility proof, and who would rather submit findings than a paragraph of intentions.
What We Keep Finding
The RFP is out, the deadline is set, and a section somewhere asks how your product meets WCAG or Section 508. Procurement teams read stacks of these and have learned to skim past "we take accessibility seriously". What stops the skim is evidence. Results rule by rule, the assistive technology named, the screenshots dated.
Now the part that saves bidders a small panic. Most RFPs name an older standard than the one we audit, because the standards behind them are older. Section 508 still incorporates WCAG 2.0 Level AA. The DOJ Title II rule and the HHS Section 504 rule both name WCAG 2.1 Level AA. The European harmonised standard currently sits on 2.1 as well. None of that is a problem, because the versions are built to be backwards compatible. Content that conforms to WCAG 2.2 also conforms to 2.1 and to 2.0. One audit against the current 55 rules answers a request for any of the three, and your bid can say so in a sentence. The one asterisk is the parsing rule, which 2.2 retired and those regulations keep, because a regulation freezes the version it names. We check it where a dated rule is in play, so the asterisk is on our side rather than yours.
Deadlines are the real constraint, so here is how ours actually run. The Rapid Audit is 5 business days and the Standard is 10, and both are counted from the point we have confirmed scope and payment has cleared rather than from the moment you press the button. If something blocks our testers, a site that goes down or a login we cannot get into, the clock pauses until it is cleared. Count backward from your bid date with those two facts in hand and you will book early enough.
What We Check
- Audit against all 55 WCAG 2.2 A and AA rules, which covers 2.1 and 2.0 too
- Test with a real blind screen-reader user, on the pairing your buyer is likeliest to run
- Date and screenshot every finding, so your bid team can quote the report directly
- Flag the gaps a procurement reviewer would find, with the fix beside each one
- Deliver on the published timeline, 5 business days Rapid and 10 Standard
What You Get
Every service on this site runs the same three-pass engine: an automated scan, an expert review of all 55 WCAG 2.2 A and AA rules, and a hands-on session with a professional blind screen-reader user. You get one report with every finding screenshotted, ranked by user impact, and linked to its fix. Your team fixes, we verify: the re-audit is half price within 3 months.
The format is not a mystery either. Read the sample report before you spend anything.
The Honest Limit
One honest limit and one thing we cannot evidence. The limit is that an audit reports what is true, failures included, so if your product has gaps the report will say so. The strong bid names them next to a fix plan, and buyers trust that more than a spotless sheet nobody can check. What we cannot evidence is anything outside a browser. Our testing is desktop-based and web-based. A native mobile client, a desktop application or a hardware component in your bid needs its own testing from somebody else, and a conformance report gives you nowhere to hide that at Level A or AA. Tell us the shape of the product before you order and we will say which rows we can fill.
What It Costs
Rapid Audit: $499, up to 10 pages you pick, report in 5 business days. Standard Audit: $1,499, up to 25 pages in 10 business days. Flat rates, no discovery calls, and a real blind screen-reader user on every engagement. Pick your pages. We bring the humans.
Worth Reading Next
Related on this site
Guides, checklists, tools, and terms that go with this service.