The Government Web Accessibility Handbook: From Compliance to Excellence
A working reference for government web teams who want to understand accessibility deeply. Not just pass an audit. Actually serve every member of the public who lands on the site.
About This Handbook
124 pages. Published July 2026. Written by Logan Nathan for web designers, developers, content editors, and communications staff who need to understand accessibility at the level where you can make real decisions. Not the level where you tick boxes and hope for the best.
Compliance vs. Genuine Accessibility
Your site can pass a WCAG 2.1 AA automated audit and still fail the people it's supposed to serve. That's the trap. WCAG is a technical standard with measurable criteria, and measuring against criteria is a lot easier than measuring whether a disabled resident can actually use your permit portal at 9pm on a Tuesday.
Consider what “passing” can look like. Every image has alt text (WCAG 1.1.1 pass), but every alt text says “image” or “photo.png.” Every form field has a label (WCAG 1.3.1 pass), but the labels are so vague that a screen reader user has no idea what to type. The heading hierarchy is technically correct, and yet navigating by headings feels like reading a phone book backwards.
This handbook closes the gap between passing an audit and building something people can actually use. It goes past the checklist. You get the user experience behind each requirement, the implementation mistakes that clear automated tools but break real users, and the design decisions that make government digital services usable instead of just defensible. Pair the reading with a real-world scan of your site using an ADA audit tool so you can see where your own pages fall short before you start remediating.
Topics covered by section
35 topics across 6 sections
Every topic maps to a real decision government web teams face in the field.
Handbook Contents
Section 1: Color Contrast and Typography for Government Audiences
Government websites serve populations with higher-than-average rates of vision loss, cognitive disability, and age-related visual changes. The 4.5:1 contrast ratio WCAG requires is the mathematical minimum for adequate readability. It isn't the target. Section 1 walks through why 7:1 is achievable and better for body text on government sites, how type size and weight change perceived contrast, and the specific headaches of government data visualization, where color often encodes meaning that has to also come through in shape, pattern, or text.
Topics covered
- Why 4.5:1 is the floor, not the goal. The case for higher contrast in government contexts
- Typography choices that affect reading for people with dyslexia and low vision
- Data visualization color: how to design charts and maps that read without color
- Focus indicator design: the 3:1 contrast requirement and why most focus indicators fail it
- Dark mode and high-contrast mode support for government websites
Section 2: Accessible Navigation Patterns for Government Websites
Navigation is where most government websites fail screen reader users and keyboard users worst. Multi-level menus get built wrong constantly. They trap keyboard users in open submenus, announce the wrong expanded state to screen readers, or refuse to close when focus moves away. Section 2 hands you the correct ARIA patterns for each navigation type, with code examples and testing steps you can hand to a developer today.
Topics covered
- Skip navigation: why the first link matters and how to build it correctly
- Keyboard navigation in multi-level dropdown menus: the correct ARIA pattern
- Breadcrumbs: proper markup, ARIA labels, and the mistakes we see over and over
- Mobile navigation patterns: hamburger menus, off-canvas menus, and keyboard focus
- Search: making government search usable for keyboard and screen reader users
Section 3: Accessible Form Design for Government Services
Government forms are the highest-stakes accessibility context on your site. Permit applications. Service registrations. Payment portals. An inaccessible contact form is annoying. An inaccessible permit application blocks a resident from getting a government service. Section 3 goes through every part of form design with focus on the messy realities of government workflows: multi-page applications, conditional fields, address validation, and file upload.
Topics covered
- Label associations: when <label for> isn't enough
- Field descriptions and help text: when aria-describedby is needed and how to use it
- Error handling: the three requirements (identify, describe, suggest) and why most forms fail all three
- Required field marking: alternatives to color-only indication
- Multi-step forms: managing focus and state announcements across steps
- CAPTCHA alternatives: accessible challenge methods for government forms
- File upload accessibility: the implementation mistakes almost every team makes
Section 4: Accessible Document Publishing
Section 4 is the working guide to accessible document publishing for government teams. It goes past PDFs to cover the full range of document types your agency publishes every week. Includes the specific settings in each version of Word, Excel, PowerPoint, and Google Workspace that actually change what gets exported.
Topics covered
- The document vs. web page decision: when to build a page instead of a PDF
- Accessible Word document structure (the foundation of accessible PDF exports)
- The accessible PDF checklist: 12 points every published PDF should hit
- Accessible Excel and spreadsheet data: tables, charts, and named ranges
- Accessible PowerPoint presentations
- Meeting minutes: the case for HTML-first minutes with a PDF alternative
Section 5: Video and Multimedia Accessibility
Government agencies are publishing more video than ever. Public meeting recordings, emergency information, service tutorials, event coverage. Section 5 covers the full range of multimedia rules, with real focus on the question that keeps coming up around public meeting recordings. What captioning standard applies. How to handle live vs. recorded captions. How to manage audio descriptions for information that only shows up visually in a presentation.
Topics covered
- Captions vs. subtitles: the difference and why it matters legally
- Auto-generated captions: when they're fine and when they need a human pass
- Audio descriptions: what they are, when they're required, and how to produce them
- Meeting recording accessibility: public meeting recordings and the ADA
- Accessible media players: what to look for and the common failures
- Social media video: platform-specific captioning requirements
Section 6: Building an Accessible Content Culture
The final section tackles the organizational problem behind every compliance project. Accessibility has to become a sustained practice, not a one-time push before an audit. Government web teams that hold real accessibility over time share the same traits. Accountability spread across roles. Leadership that backs the work. Clear processes when something breaks. Real relationships with residents who have disabilities. Section 6 gives you the framework to build that culture where you work.
Topics covered
- Why training alone doesn't work (and what to do instead)
- Accessibility champions: finding and supporting them inside government teams
- Integrating accessibility into content workflow and review processes
- Measuring and reporting accessibility progress to leadership
- Responding to accessibility complaints: process, tone, and follow-through
- Building community with users who have disabilities: feedback programs and disability advisory panels
Contrast ratios that show up in Section 1
4.5:1 is the floor, not the goal
Get the Full Handbook
Book a demo and we'll send you the complete 124-page handbook, plus access to our monthly accessibility webinar series for government web teams.
Schedule Demo to Get Access