Civic DeskPublic sector
A permit portal that moved most applications online
68%applications filed online
Public Sector
WCAG 2.2 AA and NIST-aligned by default.
How we build government software to the accessibility and security standards agencies require, stated plainly and with no claim to certifications we do not hold.
Who it's for
What we deliver
Agencies ask for standards by name. This page sets out what each one requires and how Dynaamx builds to it. Building to a standard is not the same as holding a certification or an audit report: where a standard involves formal assessment or authorization, we say so, and certifications appear on this page only once we hold them.
Records of how each screen was designed and tested for accessibility, ready to support your agency's conformance report.
Our delivery controls mapped to the NIST 800-53 families your security assessment asks about.
Components built and tested to WCAG 2.2 AA, so every new screen starts accessible.
Scanning, secrets management and audit logging on every change, as described under DevSecOps.
Standards
Certifications and authorizations are listed here only once Dynaamx holds them.
What it requires
US accessibility rules for information and communication technology, which many states and agencies also adopt. For web content they point to WCAG 2.0 AA.
How we build to it
Accessibility designed into every component and checked on every release, including keyboard, screen reader and zoom testing, documented so it can support your conformance reporting.
What it requires
The current W3C accessibility guidelines at level AA, which also cover the 2.1 AA level the 2024 ADA Title II rule sets for state and local governments.
How we build to it
Our default target for every public-facing screen: contrast, focus, target sizes, labels and errors checked in design reviews, automated tests and manual testing with assistive technology.
What it requires
A catalog of security and privacy controls used for US federal systems and as the basis of state cloud programs.
How we build to it
The controls in our delivery process (access control, audit logging, configuration management and vulnerability scanning) align with the 800-53 families, and we map them for your agency's assessment.
What it requires
FBI requirements for systems that access criminal justice information: personnel screening, advanced authentication, encryption, auditing and agency agreements.
How we build to it
Where a project touches criminal justice information, we design for the policy's technical controls and work under your agency's CJIS agreements. Compliance is established with your agency, not claimed by a vendor alone.
What it requires
US law protecting the privacy of student education records held by schools and institutions that receive federal education funding.
How we build to it
Data minimization, role-based access for people with a legitimate educational interest, access logs and retention rules designed in with the institution.
What it requires
A security program, now operating as GovRAMP, that verifies cloud products used by state and local governments against a NIST 800-53 baseline.
How we build to it
Verification applies to cloud products and their providers. Where your agency requires it, we build on infrastructure from providers that hold the relevant status, and align our own controls with the same baseline.
How we work
Agree which standards apply to the project and what evidence your agency needs.
Design and engineer to those standards from the first screen.
Document testing and controls as the work happens, ready for your review.
Outcomes
In practice
Civic DeskPublic sector
68%applications filed online
Brightpath LearningEducation
2.3×course completion
Related
Digital services for state, local and education agencies.
Flows tested with real users and a design system engineering can build from.
Scanning, secrets management and threat modeling built into every change.
Permits, payments and status tracking residents can finish online.
Student platforms and adaptive learning with FERPA-aware data handling.
Aging agency systems replaced in stages, with public services kept running.
Further readingShipping accessible interfaces without slowing down
Frequently Asked Questions
Certifications and authorizations appear on this page only once we hold them. What this page describes is how we design and build to each standard, which is what most project requirements ask a vendor to show.
Section 508 is a US legal requirement that points to WCAG 2.0 AA for web content. WCAG 2.2 AA is the current version of the guidelines, with added criteria such as keeping focus visible and targets large enough to use. Building to 2.2 AA covers the earlier levels too.
Yes. We audit against WCAG 2.2 AA, fix issues in order of their impact on users and set up checks so new issues are caught before release.
The agency, working with every vendor whose systems or people touch criminal justice information. We design for the policy's technical controls and follow your agency's CJIS requirements and agreements.
Start a project
Share a few lines about what you have in mind and we'll reply with next steps.