USER EXPERIENCE AND ACCESSIBILITY
USER EXPERIENCE AND ACCESSIBILITY
Avalon designs the interface before the build, so the agency pays to build the right thing once instead of rebuilding the wrong thing twice.
Avalon produces research-informed wireframes, clickable prototypes, USWDS-based visual design, and accessibility-annotated handoff packages your developers can build from without guesswork.
THE PROBLEM & THE APPROACH
The Challenge
Our Approach
Federal systems were procured, not designed, screens are a projection of the database schema, and the interface confuses the very users the mission depends on.
Avalon defines the top tasks an interface must support and builds tested, annotated wireframes and prototypes before a line of code is written.
GSA's 18F, the government's internal design shared service, was eliminated in March 2025, agencies that used to borrow 18F designers now have no internal option.
Avalon delivers the design discipline directly: research, wireframes, USWDS-based visual design, and a build-ready specification, all under one technical roof.
Section 508, 21st Century IDEA, and OMB M-23-22 all set usability and accessibility requirements that are far cheaper to satisfy at the design stage than to retrofit after launch.
Every design ships with an accessibility annotation layer, focus order, semantics, ARIA intent, and error patterns, so developers and testers inherit intent instead of guessing at it.
Design gets skipped or absorbed as an afterthought inside build contracts, because O&M and modernization money is easier to justify for visible development than for the design work that determines whether it succeeds.
A fixed-price, 4–8 week design definition package de-risks the build before the larger contract is even scoped.
CORE CAPABILITIES
Establishing what the interface actually needs to do, before any pixels are drawn.
Testable design artifacts, reviewed with the agency before any visual investment is locked in.
Carrying design intent into the build so nothing gets lost or reinterpreted.
OUR PROCESS
Heuristic evaluation, stakeholder interviews, and definition of the top tasks the interface must support. (Weeks 1–2)
Annotated wireframes and a clickable prototype for priority flows, with one structured review cycle. (Weeks 3–5)
USWDS theming, accessibility annotation, and the build-ready developer handoff package. (Weeks 6–8)
In the embedded delivery model, design runs one to two sprints ahead of development with continuous design QA through the parent engagement's cadence.
WHY AVALON
5
Federal Frameworks Addressed
Engineering-First Design
Design-first boutiques hand agencies beautiful screens; Avalon hands agencies screens its own developers can build and its testers can pass, because the same firm builds systems like this one.
Designs are checked against the agency's actual environment, authorized tooling, IAM patterns, legacy backend behavior, before they ever reach a developer.
Accessibility is written into every screen in language 508 testers use, not promised as a value to be discovered later.
Session handling, warning banners, and MFA flows are resolved in the design, not discovered during integration.
One technical roof carries the work from design through the build, avoiding the handoff gaps that plague design-only boutiques.
FREQUENTLY ASKED
Straight answers about scope, timeline, and what design does and doesn't guarantee.
Talk to Our Team →5
Federal Frameworks Addressed
Ask who on that team owns task completion as a metric. On most build teams design is done incidentally by developers between tickets. Offer a bounded design review of one high-volume flow, if it comes back clean, the agency has lost nothing; it rarely comes back clean.
Reframe the ratio: design is typically 8–15% of build labor and it protects the other 85–92%. One post-launch rework cycle on a single flow costs more than the design package that would have prevented it.
USWDS is a component library, not a product design. It supplies the parts; it does not decide the flows, the states, the error handling, or which of its components a task needs. Misassembled USWDS fails users while looking compliant.
Avalon states the adjacent delivery record for what it is, walk the buyer through the actual methodology artifacts, annotation kit, handoff samples, USWDS theming approach, and propose a simplified-acquisition-sized first package that lets the agency verify at low exposure.
End-stage 508 findings are the most expensive kind to fix, and the government's own FY 2025 assessment shows most agencies still test inconsistently and late. Design-stage annotation is how findings are prevented rather than remediated.
Three lawful, standard paths exist: nine or fewer public participants, federal-employee research within official duties, and the A-11 Section 280 fast-track generic clearance where the agency holds one. Research is scoped to fit the path available.
Talk to Avalon about scoping a design definition package or embedding design into your next build.