State Agency Websites. Between federal rules and local reality.

State agencies sit in an awkward middle: federal-style accessibility and procurement expectations, but resident-facing services as immediate as any city's. We build sites that satisfy the compliance bar without making a resident read policy language to renew a licence.

We grow your business with

CROturn traffic into leads

SEOrank & get found

GEOwin generative search

AEOget cited by AI answers

The problem

Two audiences, one site

A state agency site has to serve residents doing something specific — renewing, applying, reporting, checking eligibility — while also publishing the regulatory and policy content the agency is obliged to make public. Those two jobs pull in opposite directions, and most state sites resolve the conflict by burying the service under the policy.

Accessibility is rarely optional either. Many states have statutes modelled on Section 508, and federal funding conditions frequently apply on top. The standard is the same one we build to by default. For state and local government, the ADA Title II rule names WCAG 2.1 AA specifically, with staged compliance dates — a site built to 2.2 AA clears it.

The build

What state work requires

✓

Accessibility to WCAG 2.2 AA, which clears state statutes modelled on Section 508

✓

Service journeys separated from policy content, so residents are not reading regulation to find a form

✓

Multi-department governance across agencies and divisions that publish independently

✓

Multilingual delivery for the languages actually spoken statewide

✓

Migration that preserves the public record — notices, rules, datasets, archived guidance

✓

Answer-engine accuracy for eligibility rules and deadlines

✓

Written handover that survives an administration change

Questions

State agency questions

Do you follow our state's design system?

If you have one, yes. Tell us which and we will build to it. Several states maintain systems modelled on USWDS, and building to a documented pattern library is usually faster than negotiating a new design language.

How do you handle content owned by many divisions?

The same way we handle it for counties and campuses: shared components that carry the accessibility guarantees, division-level editing that cannot break them, and a governance model agreed during the build.

Can you work with counties and cities in our state too?

Yes — municipal website design covers local government, and the accessibility baseline is identical.