Government & federal

Public-sector work, built to the standards it will be judged against

Government buyers verify before they call, and the site is where they start. Ours are built so the facts sit where they get looked for — and so the accessibility and security questions arrive already answered.

The standards are already written. The site should meet them on purpose.

Three frameworks shape public-sector work, and all three cost far less to build in than to retrofit later. We treat them as part of the spec from the first day, not as a remediation project after someone complains.

What we build for this sector

Section 508 and WCAG 2.1 AA, built in

Section 508 is the federal accessibility law for digital content, and it points at WCAG — the international Web Content Accessibility Guidelines. We build to both: semantic structure, keyboard operation, contrast, focus order, and screen-reader labeling done as we build and verified before launch, not bolted on afterward. We publish an accessibility statement so your position is documented rather than assumed.

ADA Title II readiness for public entities

ADA Title II reaches the web content and mobile apps of state and local government entities. The Department of Justice rule names WCAG 2.1 Level AA as the technical standard those entities have to meet. We audit against that bar, fix what fails, and hand you the record showing what was tested and when. Confirm your own dates and obligations with counsel — we build to the standard, we do not advise on the law.

SOC 2 readiness and security questionnaires

SOC 2 is the security reporting framework primes and agencies lean on to check how a vendor handles data. When one of them asks how the site is hosted, secured, and monitored, the answers already exist in writing — we prepare the evidence a SOC 2 review expects on the web and infrastructure side. The attestation itself is issued by an independent CPA firm, never by us.

Your capability statement, on the web

The one-page document your buyers already know, rebuilt as a page they can scan and a PDF they can forward — core competencies, differentiators, past performance, and points of contact in the order a contracting officer reads them.

Codes, registrations, vehicles, and teaming

Your NAICS and PSC codes — the industry and product-service codes buyers search by — plus your UEI (Unique Entity ID) and CAGE (Commercial and Government Entity) numbers, your status in SAM.gov (the federal System for Award Management vendor registry), set-aside designations, the vehicles you can be ordered from, and how you team, all in one scannable, linkable block. You supply the values; we make them findable and easy to keep current. We never research or assert them for you.

A build that behaves on a government network

Self-hosted fonts and assets, minimal third-party scripts, no tracking you have not asked for, HTTPS and security headers throughout. Locked-down agency browsers and content filters block much of what a typical marketing site loads, so we leave it out by default.

How a public-sector engagement runs

  1. 1

    Positioning

    Who you are actually selling to — agencies, primes, the public, or all three — and what a first-time visitor has to be able to confirm before they will pick up the phone.

  2. 2

    Compliance plan

    We agree the accessibility target and the security posture in writing up front, so which standard applies is settled at the start instead of argued about at launch.

  3. 3

    Design and build

    Real pages with your real language in them, then developed, wired up, and kept light enough to load on a constrained connection.

  4. 4

    Verify and document

    Automated checks plus a manual keyboard and screen-reader pass, documented so you have a dated record to hand over when someone asks for one.

  5. 5

    Launch and keep current

    We handle the cutover, then keep awards, vehicles, and registrations current — stale details cost credibility fast in this sector.

A good fit if

  • You are a city, county, or special district facing the Title II deadline
  • You hold a set-aside designation and want it easy to verify
  • Primes and agencies find you by NAICS code
  • A security questionnaire is holding up a deal
  • Your buyers are contracting officers, not consumers

Questions we get

If you are a state or local government entity, the rule reaches your web content and mobile apps and names WCAG 2.1 Level AA as the standard. As published, entities serving 50,000 or more people were required to comply by April 2026, and smaller entities and special districts by April 2027 — so the first deadline has already passed. We are not a law firm and this is not legal advice: confirm your obligations and dates with counsel, then we will audit against the standard and fix what fails.
Section 508 binds federal agencies directly and reaches contractors through what agencies buy and what solicitations require, so the practical answer is usually yes for anything a federal audience touches. We build to WCAG, the standard Section 508 references, and publish an accessibility statement so the position is documented. If a solicitation names a specific conformance level, we build to that level.
Ask us directly about our own registrations, certifications, and vehicle status — we will tell you plainly what we do and do not hold rather than imply anything. We build and audit to these standards; we do not issue attestations, and a SOC 2 report is always produced by an independent CPA firm. We can be engaged directly, or as a subcontractor to a prime under your paper.
Cost and timeline both move with page count, the depth of past-performance content, and whether a documented accessibility conformance report is part of the deliverable. You will have a real number and schedule after the first conversation.

Tell us which standard you are being held to.

Start your project

A few quick questions — about two minutes.