Last updated Aug 2, 2026

Accessibility statement

We build to WCAG 2.2 AA. A change that fails the automated check for it doesn't ship.

1. The standard

Every page targets WCAG 2.2 Level AA, the same bar VA's own accessibility and plain-language review checks a site against. Contrast, text size, focus visibility, and form labeling all follow it, not a looser house style.

2. What's enforced, not just intended

Every push to this app runs axe-core, an automated accessibility scanner, against every page in both light and dark mode. It checks color contrast, form labels, focus order, ARIA roles, and the rest of WCAG 2.2's A and AA success criteria. A second, separate check loads every page at three phone widths — 360, 412, and 840 pixels — and confirms nothing scrolls sideways and every button or link measures at least 44 by 44 pixels.

Neither check is advisory. A page that fails either one blocks the change that broke it.

3. What we haven't tested

Automated scanning catches a lot, but it isn't a person. We have not run this site through a screen reader by hand — no NVDA, JAWS, or VoiceOver pass — and we have not user-tested it with anyone who relies on assistive technology day to day. Treat this page as an honest account of what's checked by machine, not a claim that every real assistive-technology workflow has been verified.

4. What we build in

Every interactive element shows a visible outline when it's focused. A claim's status or a documents-needed flag is always paired with a word or number, never color alone. Form fields carry real labels, and an error shows up in words next to the field, not just a colored border. Buttons that are icon-only still carry a text description for a screen reader.

5. Tell us what's broken

If a page doesn't work for you, email devs@forwardmarch.vet. Tell us the page, what device or software you were using, and what happened. A person reads it, same as our contact form.