Start a project
Menu

Public Sector

Section 508 Compliant Development

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

Sound familiar?

  • Our procurement requires Section 508 conformance and we need a vendor who understands it.
  • Our current site fails accessibility audits.
  • Our security requirements cite NIST 800-53 and we need the controls mapped.
  • We handle student or criminal justice data and it must be handled correctly.

What we deliver

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.

  • 01

    Accessibility evidence

    Records of how each screen was designed and tested for accessibility, ready to support your agency's conformance report.

  • 02

    Control mapping

    Our delivery controls mapped to the NIST 800-53 families your security assessment asks about.

  • 03

    Accessible design system

    Components built and tested to WCAG 2.2 AA, so every new screen starts accessible.

  • 04

    Security in the pipeline

    Scanning, secrets management and audit logging on every change, as described under DevSecOps.

Standards

What each standard asks.

Certifications and authorizations are listed here only once Dynaamx holds them.

  • Section 508

    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.

  • WCAG 2.2 AA

    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.

  • NIST SP 800-53

    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.

  • CJIS Security Policy

    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.

  • FERPA

    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.

  • StateRAMP (GovRAMP)

    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

Three steps, no surprises.

Our process
  1. 01

    Clarify

    Agree which standards apply to the project and what evidence your agency needs.

  2. 02

    Build in

    Design and engineer to those standards from the first screen.

  3. 03

    Evidence

    Document testing and controls as the work happens, ready for your review.

Outcomes

What changes.

  • Requirements mapped before the build, not discovered at audit
  • Accessibility and security evidence produced as part of delivery
  • Plain statements of what is met, with no inflated claims

In practice

Related work.

All work

Tools we use

  • axe
  • NVDA
  • VoiceOver
  • Lighthouse
  • Trivy
  • Terraform

Related

  • Sector · Overview

    Public Sector

    Digital services for state, local and education agencies.

  • UX & UI Design

    Flows tested with real users and a design system engineering can build from.

  • DevSecOps & AppSec

    Scanning, secrets management and threat modeling built into every change.

  • Citizen Services

    Permits, payments and status tracking residents can finish online.

  • Education

    Student platforms and adaptive learning with FERPA-aware data handling.

  • Modernization

    Aging agency systems replaced in stages, with public services kept running.

Further readingShipping accessible interfaces without slowing down

Frequently Asked Questions

Good questions.
Straight answers.

Is Dynaamx certified for these standards?

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.

What is the difference between Section 508 and WCAG 2.2 AA?

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.

Can you fix the accessibility of an existing site?

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.

Who is responsible for CJIS compliance?

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.

Still have a question?Ask a senior engineer. We reply within one business day.Ask us anything

Start a project

Got an idea worth building?

Share a few lines about what you have in mind and we'll reply with next steps.