For U.S. federal, state and local agenciesHow we work with government
Government
You will still be running this in fifteen years.
Most platforms are bought for what they do this year. Public services are judged on whether they still work after the budget, the supplier and the people who chose them have all moved on. SnowBlock is built for the long half of that.
The certifications, named as your checklist names them, with the paperwork behind each one. Ask for any of it before the first call.
Accessibility
WCAG 2.1 AA
Every shipped component is tested against it — keyboard paths, focus order, contrast. Not "accessible-ready". Tested.
Ask us for: Per-component audit results
Conformance report
VPAT 2.5
A current Voluntary Product Accessibility Template, written against the Revised 508 standard. The document your procurement file needs.
Ask us for: The VPAT itself, on request
Federal procurement
Section 508
Satisfied through the WCAG 2.1 AA work above — 508 points at that standard rather than defining its own. One body of evidence, both requirements.
Ask us for: Covered by the same VPAT
Security controls
SOC 2 Type II
Audited annually by an independent assessor — Type II, so it covers how the controls held over time rather than how they looked on one day.
Ask us for: Audit report, under NDA
State cloud programmes
StateRAMP
Deployable into environments that meet state programme requirements, including private regions where a statute says the data does not leave.
Ask us for: Deployment architecture
Content portability
JSON Schema
Your content types are defined in an open standard, and content exports as structured data — fields, versions and all. Public-records requests are a query, not a salvage job.
Ask us for: Export format documentation
Every programme words this differently. If yours asks for something not listed, ask — a straight “no” saves you more time than a discovery call.
In practice
Every platform on your shortlist will claim an audit trail. These are the duties that actually land on your web team, and what the platform does about each one.
Accessibility regulations
Launching compliant is the easy half. Six months in, someone pastes a table out of Word or uploads a scanned PDF, and the audit you paid for is out of date. So the checks run at the point of publish, against the person making the change, while they can still fix it.
Publish is blocked until the image has alt text. The editor cannot ship this page without it.
Freedom of information
Someone asks what the fee schedule said in March, and the statutory clock starts. Because every version is kept as structured content rather than as rendered markup, the answer is a search across dates and fields — and it exports as evidence you can hand over.
3 versions, each with the text as it stood that day. Exported as data, not as a screenshot of a page.
Welsh and community languages
Statutory parity does not mean a translated homepage and an English PDF behind it. Each language is a full site with its own URLs and its own publishing workflow, and right-to-left is a layout direction the components already handle rather than a plugin bolted on afterwards.
Cymraeg is at full parity — the same 214 pages, not a translated subset.
Your retention schedule runs longer than any framework agreement. Whoever wins the next tender inherits this, so it is built to be handed over: open formats, your own repository, and an export that carries the history rather than a snapshot of today.
Components live in your repository as ordinary React, not as templates inside our product. If the contract ends, nothing has to be handed back, because it was never ours to hold.
Your content types are written in JSON Schema. A successor supplier can read the structure of every record on day one, without a discovery phase billed to you.
Exports carry fields, versions and publish dates as data — what a retention schedule and a disclosure request both need. Not a crawl of rendered pages that loses everything except the current text.
Start where it hurts
One service, end to end, live and in front of residents. It proves the platform against real accessibility and real load before anything else is committed.
Move at your own pace
Sites move one at a time, across financial years if that is how the funding lands. The ones that have not moved carry on untouched.
Leave the systems of record alone
Planning, licensing and case management stay put. SnowBlock publishes the public face of them; it does not ask you to re-procure the systems behind it.
Renew because the platform still earns it — not because leaving would cost more than staying.
In service
Councils, agencies and public bodies running on the platform today. Every one of them assembled from the same component library.
Bring the statute you answer to, the systems nobody is allowed to touch, and the last platform that let you down. If we are not a fit, you will know inside the hour.