Selling software to US public bodies?
State and local governments in the US must make their web content and apps meet WCAG 2.1 level AA, and that includes the software they buy. Their procurement teams will ask you for proof.
- Public bodies serving 50,000 people or more
- April 26, 2027
- Smaller public bodies and special districts
- April 26, 2028
- The standard the rule names
- WCAG 2.1 AA
Details
What the rule says
The Department of Justice’s rule under Title II of the Americans with Disabilities Act covers the web content and mobile apps that state and local governments provide or make available, directly or through contractors and licensed software. Public universities and colleges run by a state count too.
In April 2026 the department moved both compliance dates back by one year. What the rule requires did not change. This is a summary, not legal advice.
What buyers will ask you for
Procurement teams have to show that the software they buy meets the rule, so they pass the question on to you. Expect requests for:
- an Accessibility Conformance Report on the VPAT template;
- evidence of testing, such as an audit report;
- a plan, with dates, for the barriers that are not fixed yet.
How we help
We audit the parts of your product your buyers use most, such as sign-in, the main workflows and the forms. Your developers fix what we find, with our fix support if they want it. Then we re-test and write the ACR, so every remark in it rests on evidence.
Selling to federal agencies too?
Federal agencies follow Section 508. The International edition of the VPAT covers Section 508, WCAG and the EU standard EN 301 549 in one report, so one audit can answer buyers in several markets.
Not sure where your product stands?
Send us one page of your product, such as the sign-in or a main form. We check it by hand and tell you its five most serious issues, free.