Accessibility-first,
plain-language always.
Municipal sites, state portals, public-sector agencies. The visitor is filing a form, paying a tax, or looking up a deadline. They are not browsing; they are working.
Government sites are the surface where civic UX failure has the largest aggregate cost. Every minute a resident wastes finding the right form is a minute charged against their day; every form that’s unfillable on a low-end Android phone is a resident excluded. The standards that should govern these sites (WCAG 2.1 AA at minimum, plain-language drafting, mobile-first responsive design, language access) are well established. The actual delivery has been wildly inconsistent.
Accessibility fundamentals for government sites
- Color contrast at WCAG AA minimum for all text and interactive elements. Most failing government sites fail here first.
- Keyboard navigation for every interactive element. Form fields, dropdowns, file uploads: all of it.
- Screen-reader compatibility, tested against NVDA and VoiceOver at minimum. Not assumed; tested.
- Language access where your community needs it, typically English and Spanish at least.
- Mobile responsive design that holds up at 360-pixel width.
- A “Skip to main content” link as the first focusable element.
Building for government?
Let's talk specifics.
Tell us what you do. We'll come back with three questions and one honest take.
Replies within a few hours. Prefer WhatsApp? Message us there.