Industry · Government & Public Sector
Accessibility requirements for Government & Public Sector websites
Public-sector accessibility has the longest legal track record. US federal sites have been Section 508-bound since 1998; EU public sites have been WAD-bound since 2018. Recent DOJ Title II rules tightened deadlines for US state and local government.
Regulations that apply
Government & Public Sector sits at the intersection of general digital-accessibility law and sector-specific obligations. The most relevant items to track:
Section 508
Active since 1998; refreshed 2017 to align with WCAG 2.0 AA.
US federalDOJ Title II Final Rule (2024)
WCAG 2.1 AA required; phased deadlines.
US state/localWeb Accessibility Directive (EU 2016/2102)
EN 301 549 / WCAG 2.1 AA. Audited annually.
EU public sector
The accessibility risks specific to Government & Public Sector
Every industry has its own failure pattern. The combination below is what audits, complaints, and lawsuits in this sector keep returning to. Fixing them clears the most-cited issues without touching every page.
Form-heavy services without proper labels
Tax, benefits, and licence renewal forms are most-cited issues.
1.3.1, 3.3.2Document portals serving image-only PDFs
Common in older municipal sites.
1.1.1
A short remediation checklist
Most Government & Public Sector teams do not need a 200-item audit before they fix anything. They need an ordered list of the highest-impact moves. Start with these and re-audit after each pass.
Audit highest-traffic services first
Publish a public accessibility statement with current conformance score
Establish feedback channel and 30-day response
Run a free Certvo scan against your homepage and one task-flow URL (login, checkout, booking). It pinpoints which of the issues above apply to you, and how often.
Scoping an audit for Government & Public Sector
Government & Public Sector carries 3 distinct obligations to satisfy — Section 508, DOJ Title II Final Rule (2024), Web Accessibility Directive (EU 2016/2102) — spanning US federal and US state/local and EU public sector. An auditor prices the work by how many of those regimes are in scope and how many distinct task flows carry them, not by page count.
The 2 failure patterns above map to 1.3.1, 3.3.2, 1.1.1. Every one of those is machine-detectable, which means a scan can clear them before an auditor starts charging by the hour. What remains for manual review is the judgement work: whether form-heavy services without proper labels actually functions end to end for a screen-reader user.
Scan first, audit second
Clearing the 2 automated patterns above shortens the manual pass to the flows that need a person.
Scope by template, not by page
A site with thousands of pages usually has fewer than twenty distinct templates. Price the templates.
Re-test after remediation
The conformance claim rests on the re-test, not the first report.
Evidence for US federal
Keep dated scan history — it is what turns a conformance claim into something a regulator accepts.
Other industries
Accessibility for Media & Publishing
WCAG 2.1 AA for news sites, magazines, and publishers: video captions, paywalls, audio des
Accessibility for Travel & Hospitality
WCAG 2.1 AA for airlines, OTAs, hotels: search, calendar, booking flow. EAA covers consume
Accessibility for Legal & Professional Services
WCAG 2.1 AA for legal practice sites, intake forms, document portals: ADA, EAA, and risk o
Accessibility for Real Estate
WCAG 2.1 AA for property listings, search, virtual tours, and ADA compliance in real-estat
Accessibility for Nonprofit & NGO
WCAG 2.1 AA for nonprofits: donation flows, volunteer portals, ADA, EAA, and grant-funder
Accessibility for E-commerce
WCAG 2.1 AA + EAA + ADA for online stores: cart, checkout, product pages. Lawsuit risks, a
Find every accessibility issue on your site in 60 seconds.
Free public scan. No card. AI-generated fixes for every issue we find.