Brieflist

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

Standards and versions are updated over time. The tender documents are the authority on which version applies.

How to answer the accessibility question

  1. State the target precisely. "We build to WCAG 2.2 level AA" — not "we take accessibility seriously".
  2. 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.
  3. Include disabled users in research where the service is public-facing, and say how you recruit them.
  4. Show evidence. A past accessibility statement you wrote, an audit report, or an ACR/VPAT for your product.
  5. Cover documents and content. PDFs, videos (captions, transcripts) and content written in plain language are often forgotten and often scored.
  6. Plan for after go-live. How issues found by users are fixed, and how you keep the service compliant as it changes.

Common mistakes

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.