Government
Drupal platforms for agencies that have to pass a Section 508 audit, stay up on a bad day, and say who runs them.
Federal, state and local agencies publish under statutory accessibility obligations, with teams that cannot afford downtime and procurement that asks who operates the platform. We build for that, in your own cloud account, and stay to run it.
Talk about your agency's platform- Section 508 conformance you can hand to procurement
- Operated inside your own cloud account
- Editors trained before launch, not after
What a government platform has to do
Publish to everyone, including the person on a screen reader and the person on a nine-year-old phone. Stay up when a storm, an election or a court ruling sends everyone to one page at once. Keep a record. And survive procurement: someone will ask who operates it, where the data lives, and what happens if the vendor goes away.
What we do for agencies
We build and migrate Drupal platforms for federal, state and local agencies, run them inside the agency's own AWS or Azure account, and keep them at Section 508 and WCAG 2.2 AA with a conformance report procurement can use. We train the editors before launch, because most accessibility barriers arrive through the editor. Our first platform has been a federal one for more than ten years.
How we work with government
An audit first: the current site, its accessibility state, its hosting and its integrations, in writing. Then a content model designed for the agency's programs rather than its org chart, a build to the standard, a rehearsed migration, and a cutover in a window you choose. After launch, security releases inside the advisory window and a named engineer who answers.
Why now
The ADA Title II rule puts WCAG 2.1 AA on the calendar for state and local governments: April 26, 2027 for entities serving 50,000 people or more, April 26, 2028 for the rest. Drupal 10 reaches end of life on December 9, 2026. An agency still on Drupal 7 or an early 10 has both deadlines inside one budget cycle.
The calendar that drives government work
Apr 26, 2027
ADA Title II, 50,000+
WCAG 2.1 AA for larger state and local governments; April 26, 2028 for the rest.
ADA Title II web ruleJan 18, 2018
Revised Section 508 in effect
Federal agencies and what they procure, harmonized with WCAG 2.0.
Section 508 laws and policiesDec 9, 2026
Drupal 10 end of life
Planned to coincide with the release of Drupal 12.
Drupal core release schedule10+ yrs
Running a federal platform
Our first platform, still on the standard it launched to.
I want to …
pass the next 508 audit
An audit against WCAG 2.2 AA with a screen reader, remediation at the source, and a conformance report written for procurement, not for engineers.
- Automated and manual testing, in plain language
- Fixes in the theme and the editorial rules, so they hold
- A conformance report and an accessibility statement
meet the ADA Title II deadline
WCAG 2.1 AA by April 26, 2027 for governments serving 50,000 or more, April 26, 2028 for the rest. The audit and the plan come first; remediation follows in priority order.
- A dated plan that fits the deadline and the budget
- The services the public depends on fixed first
- An accessibility statement and a feedback path that meet the rule
get off Drupal 7
A site on 7 has had no security fixes since January 2025 and is still serving the public. We audit it, design the Drupal 11 model it should have had, and migrate the content into it.
- An audit of modules, custom code, content and integrations
- A content model designed for programs, then a rehearsed migration
- A cutover with redirects, so no link or ranking is lost
run it in our own cloud account
The platform in the agency's AWS or Azure account, as code, monitored and patched, with a monthly cost review. Nothing resold, nothing the vendor can walk away with.
- Infrastructure as code in your own account
- Monitoring, backups restored on a schedule, patching inside the window
- A monthly cost review in writing
answer procurement's questions
Who operates it, where the data lives, what happens if the vendor goes away. Documented infrastructure in your own account answers all three before they are asked.
- Runbooks and architecture in your repository
- Your account, your keys, your data
- A handover any engineer can follow
train our editors
Most new barriers arrive through the editor: a skipped heading, an image without alt text, a link that says "click here". Rules, training and a gate in the build stop them.
- Editorial rules and a short training for every editor
- An automated accessibility gate that fails a broken build
- A quarterly check on the journeys, by a person
An agency platform, from audit to operation
The same sequence for a migration and a new build. Decisions above the line, the steps that run on every build below.
Nothing is decided on launch day. The conformance report is written before it, not after.
What is changing for government
Checked on ada.gov, section508.gov and drupal.org on September 11, 2026.
ADA Title II has a calendar
WCAG 2.1 AA by April 26, 2027 for governments serving 50,000 or more, April 26, 2028 for the rest, under the interim final rule of April 20, 2026.
Drupal 10 ends in December
December 9, 2026, alongside the planned release of Drupal 12. Agencies on 7 or an early 10 have both moves in one cycle.
Procurement asks about operations
Who runs it, where the data lives, what happens if the vendor goes away. A platform in your own cloud account answers all three.
AI answer engines read government pages first
Structured, plainly written, canonical pages get cited. The same work that passes an audit.
Services for government
The three most agencies buy first.
-
Accessibility & AI visibility
Accessibility fixed at the source, in the theme and the editorial rules, with a conformance report you can hand to procurement. The same work makes your pages the ones AI engines cite.
-
Drupal development
New builds, major-version upgrades, module and theme work, and migrations from Drupal 7 onward. Every site we build is one we can keep patched, accessible and on a supported version for years, because that is the job after launch.
-
Cloud engineering
We design and run the cloud your platform lives on, in your own account, as code, with monitoring, patching and a monthly cost review in writing. We do not resell hosting, and everything we build is documented so the next engineer can run it.
Tell us what the agency runs.
The version, where it is hosted, the last audit, and the deadline you are working to. We come back with what we would do first and what it would take.
Talk about your agency's platform