Accessibility
What has been done, what is known to be imperfect, and how to tell us when something blocks you.
Last updated 09-14-2026.
What we aim at
The Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. We do not claim to have been independently audited against them.
What is in place
- Keyboard. Every control is reachable and operable with a keyboard. Focus is visible on every interactive element, and pages start with a skip link to the main content.
- Errors. When something you submit fails, the message says what went wrong in plain language, focus moves to it, and it is announced to screen readers. What you typed is kept — a failed save does not empty the form.
- Labels. Form fields have real labels, not placeholder text standing in for one. Explanatory text is associated with its field rather than floating near it.
- Structure. Headings are properly nested, landmarks are used, and status messages are announced rather than only appearing.
- Colour and text. Body text meets AA contrast, colour is never the only way information is conveyed, and text reflows at 200% zoom and at phone widths without a horizontal scrollbar.
- Print. Documents print in full, with page breaks and no clipped text. Navigation and buttons are removed from printed output.
- Motion. There is no autoplay, no carousel and nothing that flashes.
Known limitations
- Scanned PDFs cannot be read. A photographed or faxed decision letter has no text layer, and there is no OCR yet. The app detects this and says so instead of producing nonsense, but if scans are the only form your records take, this part of the app cannot help you yet. This is the gap we would most like to close.
- Long documents are dense. The drafts are long by nature. They can be printed or downloaded and read in whatever tool suits you best.
- Not audited. Testing has been done with keyboard navigation, zoom and screen-reader review during development. There has been no formal third-party accessibility audit, and no assistive-technology compatibility matrix is published.
- The staff admin console is not held to this standard. It is an internal tool.
If something blocks you
Email support@soldierclaims.ai and say what you were trying to do, what got in the way, and what you use — browser, screen reader, magnifier, voice control. A report that stops someone completing a claim is treated as a defect, not a suggestion.
If you tell us you cannot complete something here, we will also tell you the alternative: every document this app produces is a standard VA form you can obtain and complete on paper, and an accredited Veterans Service Organization will do it with you free of charge.