Services · By situation
Grant and Funding Audit: The Evidence Your Application Needs
For the school, university, or nonprofit whose funding terms require accessibility evidence, and who needs a document that answers the requirement plainly.
What We Keep Finding
Somewhere in the funding terms sits an accessibility clause, and the first job is working out which law it is pointing at, because two get mixed up constantly. Federal money makes you a Section 504 recipient, whichever department sends it. Section 508 binds federal agencies and the Postal Service themselves, so it reaches a grantee only where an award writes it into the terms. Getting that the wrong way round sends a school district looking up the wrong standard, and plenty of published guidance does exactly that.
One more piece for public institutions, and it usually carries the earlier date. A public school district, community college or state university is a public entity under ADA Title II. That rule sets WCAG 2.1 Level AA by April 26, 2027 for entities whose population is 50,000 or more, and April 26, 2028 for smaller ones. Of the departments funding you, only HHS has published a dated web standard under its own Section 504 rules, at WCAG 2.1 Level A and AA by May 11, 2027 or May 10, 2028. So a public institution taking HHS money is on two clocks, and Title II is the one that runs out first.
Plenty of private funders skip all of that and simply write that the funded website must be accessible, leaving the proving to you. The requirement is real either way, and "we believe our site is accessible" has never satisfied a program officer. What satisfies is a pass or fail recorded against each rule, dated, screenshotted, tested with real assistive technology. That is a document you can file, cite, and hand to a reviewer, and it is the same document that tells your own team what to fix.
What We Check
- Audit against all 55 WCAG 2.2 A and AA rules, which covers a 2.1 or 2.0 requirement
- Test with real blind screen-reader users, the people the requirement exists for
- Record pass or fail per rule, dated and screenshotted, ready to file
- Map every open gap to its fix, so the remediation plan writes itself
- Frame the report against the standard your award actually names
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 no audit can be. Funders differ, and we cannot promise a specific reviewer will accept a specific document, so what we promise is substance rather than acceptance. The thing no audit can be is a conformance claim for your website. Conformance in the standard is defined for a web page, and W3C's own evaluation method says a sample of pages cannot carry a claim for a whole site. An evidence pack that says exactly which pages were tested, on what date, with what result, survives a program officer's questions. A certificate for the whole estate would not, and nobody can sell you one.
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.