Accessibility in public-sector web and software tenders
Almost every government tender for a website, app or software product asks about accessibility. Buyers are legally required to make their services usable by disabled people, so they pass that duty on to suppliers. This page explains the standards they cite and how to answer the accessibility question well.
The standard behind everything: WCAG
The Web Content Accessibility Guidelines (WCAG), published by the W3C, are the common reference. Buyers almost always ask for level AA conformance. WCAG 2.1 and 2.2 add requirements for mobile, low vision and cognitive needs on top of WCAG 2.0; check which version the tender names.
What each region asks for
- United Kingdom. Public sector bodies must meet the accessibility regulations for their websites and apps and publish an accessibility statement. Tenders typically require WCAG 2.2 AA, testing with assistive technology, and, for services, alignment with the Government Service Standard.
- United States. Federal agencies follow Section 508 of the Rehabilitation Act, whose technical standards incorporate WCAG level AA. Solicitations often ask for an Accessibility Conformance Report (ACR), usually written on the VPAT template, for software you supply. State and local governments are covered by the Justice Department's 2024 ADA Title II rule, which requires WCAG 2.1 AA for their websites and apps; after a one-year delay in April 2026, the compliance dates are 26 April 2027 for larger governments (50,000+ people) and 26 April 2028 for smaller ones. Expect city, county and state tenders to ask for it now: see what ADA Title II means for agencies.
- European Union and Ireland. Public procurement of ICT refers to the harmonised standard EN 301 549, which incorporates WCAG for web content and adds requirements for software, documents and hardware. The Web Accessibility Directive covers public sector websites and apps. Since 28 June 2025 the European Accessibility Act also applies to many private-sector digital products and services (e-commerce, banking, e-books and more), so accessibility skills are in demand beyond the public sector.
- Canada. Federal requirements reference WCAG and EN 301 549 for ICT, and departments ask suppliers to show conformance.
Standards and versions are updated over time. The tender documents are the authority on which version applies.
How to answer the accessibility question
- State the target precisely. "We build to WCAG 2.2 level AA" — not "we take accessibility seriously".
- Describe your process. Accessibility in design reviews, automated checks in the build pipeline, and manual testing with keyboard and screen readers (for example NVDA, JAWS, VoiceOver) before each release.
- Include disabled users in research where the service is public-facing, and say how you recruit them.
- Show evidence. A past accessibility statement you wrote, an audit report, or an ACR/VPAT for your product.
- Cover documents and content. PDFs, videos (captions, transcripts) and content written in plain language are often forgotten and often scored.
- Plan for after go-live. How issues found by users are fixed, and how you keep the service compliant as it changes.
Common mistakes
- Relying only on automated tools: they catch a minority of issues. Evaluators know this.
- Promising conformance for third-party components you do not control without saying how you will handle them.
- Leaving accessibility out of the price: audits and testing take time, and buyers notice when the plan has no room for them.
Find tenders where this applies
Every website, app and software tender on Brieflist is likely to ask about it: see website tenders and software tenders. More: how to write a winning tender response · bid/no-bid checklist.
This page is general guidance, not legal advice. Follow the requirements stated in each tender.