The WCAG 2.1 AA Checklist for Government Websites

Users must be able to perceive the information — nothing important can be invisible to a sense they don't have.

• Every meaningful image has descriptive alt text; decorative images have empty alt attributes.
• Text color contrast is at least 4.5:1 for normal text and 3:1 for large text.
• Non-text elements (buttons, icons, form borders) meet a 3:1 contrast ratio.
• Information is never conveyed by color alone (e.g., 'required fields in red').
• Pre-recorded video has synchronized captions; audio-only content has a transcript.
• Content reflows to a single column at 320px wide without horizontal scrolling.
• Text can be resized to 200% without loss of content or function.
• Content and structure are preserved when a screen reader linearizes the page.

Every function must work by keyboard alone — not everyone can use a mouse.

• All interactive elements are reachable and operable with the keyboard (Tab, Enter, Space, arrows).
• Keyboard focus is always visible with a clear focus indicator.
• There are no keyboard traps — focus can always move away from a component.
• A 'Skip to main content' link lets keyboard users bypass repeated navigation.
• Focus order follows a logical, meaningful sequence.
• Link text describes its destination ('Download the 2026 budget', not 'click here').
• The page has a descriptive, unique <title>.
• No content flashes more than three times per second (seizure safety).
• Time limits can be turned off, adjusted, or extended.
• Touch targets are large enough and don't rely on complex gestures.

Content and operation must be clear and predictable — especially for forms residents use.

• The page declares its language (lang attribute), and any passages in another language are marked.
• Navigation and components behave consistently across the whole site.
• Every form field has a visible, programmatically associated label.
• Form errors are identified in text and clearly describe how to fix them.
• Error messages are associated with the field they refer to.
• Instructions and required-field indicators don't rely on color or placement alone.
• Focus or input changes don't trigger unexpected changes of context.

Content must work reliably with current and future assistive technologies.

• HTML is valid — no duplicate IDs, properly nested elements.
• Custom controls expose a correct name, role, and value to assistive tech (ARIA used correctly).
• Status messages (e.g., 'form submitted', 'search results updated') are announced to screen readers.
• Third-party embeds (maps, payment forms, chat widgets) are themselves accessible or have an accessible alternative.

The most common compliance failure for government sites — the rule covers the documents you publish, not just the pages.

• PDFs are tagged with a proper reading order and document structure.
• Scanned documents are run through OCR — no image-only pages.
• Tables, headings, and lists use real tags, not just visual formatting.
• Every PDF has a title and declared language.
• Agendas, minutes, budgets, forms, and public notices are all accessible — not just web pages.