Accessibility Statement

Legatus is used by veterans living with service-connected disabilities. Some of those disabilities — low vision, hearing loss, tremor, chronic pain, traumatic brain injury, post-traumatic stress — change how a person uses a computer, and often on the days they most need to get something filed.

So this page is written as a record rather than a statement of intent. It sets out what has been built, how each piece is known to work, and — at the same level of detail — what has not been checked. Where we cannot demonstrate something, it says so instead of claiming it.

We build to the Web Content Accessibility Guidelines 2.1, Level AA. We target 2.1 rather than the older 2.0 that Section 508 requires of federal agencies, because county veteran service offices and statewide programs — public bodies — use this software, and the 2024 Department of Justice rule holds them to 2.1.

In plain terms, Level AA means text has to be readable at a defined contrast, everything has to work from a keyboard, nothing may depend on colour alone to make sense, content has to be reachable and correctly named for a screen reader, and motion has to be avoidable.

We say we build to it, not that we conform to it. That wording is deliberate. Conformance is a claim you make after an audit, and no audit has been done — section 04 sets out what that leaves open.

• Skip to the content

  Every page opens with a link that jumps past the navigation to the main content. It is the first thing you reach on a keyboard, and it appears as soon as you tab to it.

  Built in site-wide

  How we know It is rendered by the layout that wraps every page on the site, so no individual page can be missing it.

• You can see where you are

  Moving through a page with the Tab key draws a brass ring around whatever you have landed on. Controls are reachable in the order they read.

  Not fully verified

  How we know Focus styling is part of the shared control styles and is applied across the site, but we have not walked every control on every screen to confirm none was missed.

• Motion stops if you have asked it to

  If your device is set to reduce motion, animation on this site stops rather than merely slowing down.

  Built in site-wide

  How we know Every animation on the site is defined in one stylesheet, and every one of them is switched off there when your system asks for reduced motion — it does not rely on each part of the page remembering to check. Short colour fades on hover remain.

• Text contrast is measured, not estimated

  Body text, labels, links and help text are set at contrast levels that meet AA against the backgrounds they actually appear on — which is a harder test than meeting it against plain white.

  Covered by an automated test

  How we know Two automated tests re-derive the contrast of every text colour from the stylesheet itself and sweep the source for the faint greys we removed in 2026. Either one going wrong fails the test suite.

  Scope Covers text set in our colour palette. It does not check text drawn over a photograph.

• Form fields are sized for reading

  Boxes you type into are set at 16 pixels. That is a readability floor for low vision, and it also stops an iPhone zooming the page in the moment you tap a field.

  Not fully verified

  How we know There is one shared set of form styles that sets the floor, and it is what form controls are built from as screens are rebuilt. It does not yet cover every control on the site — older screens still carry their own.

• Headings are a usable table of contents

  Each page has one main heading, and the headings below it step down in order without skipping a level — so pulling up the heading list in a screen reader gives you the shape of the page.

  Covered by an automated test

  How we know An automated test walks the rendered heading order and fails on a second main heading, on a skipped level, and on a heading that has swallowed interface text.

  Scope That test covers the largest sets of public pages — more than 600 condition and exam guides — and individual pages as they are rebuilt. It does not yet run across the whole site.

• Buttons are big enough to hit

  Buttons, links and other controls are sized to at least 44 by 44 pixels, so they can be used with an unsteady hand or on a phone screen.

  Not fully verified

  How we know It is the size we build to and it is used in hundreds of places across the site, but we have not measured every control to confirm none falls short.

• Controls are named for screen readers

  Buttons that show only an icon carry a text name, decorative icons are hidden so they are not announced, form fields are tied to their labels, and error messages are announced when they appear.

  Not fully verified

  How we know These are the conventions the codebase is written to, and they are checked in review. They are not verified by an automated scanner.

• Pages are laid out for paper

  Print a page, or save it as a PDF, and you get the content — without the navigation, the side rails or the buttons, and with dark panels converted so they do not come out as white text on white paper.

  Not fully verified

  How we know The print layout is written once in the stylesheet and applies site-wide, but a page with a side rail needs one extra rule of its own, and that has been missed before. If a printout comes out wrong, it is worth telling us — it is usually a one-line fix.

There is no video or audio anywhere on this site. Nothing autoplays, nothing needs captions, and nothing will start making noise over the top of a screen reader.

• There is no dark mode. The site is light only. A dark theme was removed in August 2026 during a rebuild of the design system and has not returned. We have also not tested the site in Windows High Contrast mode or with a browser-level colour inversion, so we cannot tell you how it behaves in either.

• Some interface text is small. Reading copy is set at 16 pixels, but labels, captions, table cells and other supporting text are set at 13 to 14 pixels in a good many places. We are raising these where the text is something you have to read rather than glance at, page by page, instead of sweeping the whole site at once.

• AI-generated text. The explanations our AI tools produce are placed into a structure we control, but the wording inside is generated for each request. We cannot promise every one of them reads well through a screen reader.

• The payment page is not ours. Checkout runs on Stripe’s own hosted page. Its accessibility is Stripe’s rather than ours, and we cannot change it. Everything before and after checkout is on our pages.

• Documents you upload. A PDF or Word file you upload stays your file. If it was not built as an accessible document we do not remediate it, and text we pull out of a scanned image may be incomplete.

If any part of this site stops you doing something, tell us. Write to support@legatusos.com, and if you can, include:

• The address of the page you were on
• What you were trying to do, and what happened instead
• The device and browser you were using
• Any assistive technology you use, and its version if you know it

We answer email within two business days. You will get an answer saying what we found and whether we can fix it — including when the answer is that we cannot fix it soon, which is more useful to you than silence.

There is no phone line; our contact page explains why, and lists the other reasons people write to us.