Accessibility statement
Recoverion is committed to making its content usable by everyone, including people who rely on assistive technology or who have visual, hearing, motor, or cognitive disabilities. This page explains the standard we aim for, what we have done, and how to flag a problem.
WCAG 2.1 AA target
The standard we aim to meet across all primary pages.
Contrast verified
All text color pairings checked against AA contrast ratios.
Keyboard navigable
All pages and tools are operable without a mouse.
Issues fixed promptly
Reported accessibility problems are prioritised and fixed.
01 Our commitment
Recoverion covers a topic that affects real people at difficult moments. The information here needs to be readable and usable by everyone who needs it, regardless of how they access the web. That is the reason for the commitment to accessibility, not a legal checkbox.
Recoverion aims to conform to the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA across all primary pages. This is the widely recognized international standard for web accessibility and the level required by most accessibility legislation.
What WCAG 2.1 AA means in practice
Content is perceivable (readable by screen readers, sufficient contrast, text alternatives for images), operable (keyboard-navigable, no seizure-inducing content, enough time to read), understandable (plain language, predictable behavior, error identification in forms), and robust (compatible with current assistive technologies).
02 What we do
Accessibility is built into the design of Recoverion at a code level, not added on top. The following practices are applied across all primary pages.
Semantic HTML structure
One H1 per page. Logical heading hierarchy (H2, H3). Landmark regions (header, main, nav, footer) for screen reader navigation.
Color contrast
Body text on background colors exceeds the 4.5:1 contrast ratio required for WCAG AA. Large text meets the 3:1 ratio. All pairings are verified before publishing.
Keyboard navigation
All interactive elements (links, buttons, form fields, navigation) are reachable and operable using a keyboard. Focus states are visible on all focusable elements.
Image alt text
All informational images have descriptive alt text. Decorative images are marked so screen readers skip them. Icons used as buttons have accessible labels.
Reduced motion support
All animations and transitions are disabled automatically for users who have enabled the "reduce motion" preference in their operating system.
Plain language
Content is written in plain English with short sentences and everyday words. Technical terms (such as TRICARE plan names or clinical vocabulary) are defined when first used.
Form accessibility
All form fields have explicit labels. Required fields are identified. Error messages are specific and actionable. No sensitive data is required to use any tool.
Responsive layout
All pages reflow cleanly at any viewport width from 320px upward, without horizontal scrolling or loss of content.
03 Conformance status
Recoverion is working toward full conformance with WCAG 2.1 Level AA. The primary pages listed in the site map have been built to meet this standard. Any known issues and their current status are noted below.
| Area | Status | Notes |
|---|---|---|
| Text contrast on all primary pages | Meets AA | Ink on parchment and white on dark green both exceed 4.5:1 |
| Keyboard navigation | Meets AA | All primary pages fully keyboard navigable with visible focus states |
| Reduced motion | Meets AA | All animations disabled via prefers-reduced-motion media query |
| Interactive tools (coverage checker, cost estimator) | Meets AA | Coverage checker and cost estimator are keyboard navigable with visible focus states and tested with screen readers |
| Third-party embedded content | Monitored | Accessibility of third-party scripts (analytics) is outside Recoverion's direct control |
04 Assistive technology compatibility
Recoverion is designed to work with the following assistive technologies. Testing is carried out using common combinations of browser and screen reader.
- NVDA with Firefox on Windows
- JAWS with Chrome on Windows
- VoiceOver with Safari on macOS and iOS
- TalkBack with Chrome on Android
- Keyboard-only navigation on Chrome, Firefox, and Safari
If something does not work as expected with a technology not listed here, please report it using the process below and we will investigate.
05 Report an issue
If you encounter a barrier that prevents you from accessing content or using a tool on Recoverion, please let us know. We take accessibility reports seriously and treat them as high-priority fixes.
How to report an accessibility issue
Use the contact page and include as much detail as you can. We aim to acknowledge reports within two business days and resolve confirmed issues as quickly as possible.
06 Ongoing work
Accessibility is not a one-time task. As new pages and tools are added to Recoverion, each one is built to the same standard before it is published. Existing pages are reviewed when they are substantially updated.
- New pages are reviewed for contrast, structure, and keyboard operability before publishing
- New interactive tools are tested with screen readers before they go live
- Reader-reported issues are treated as high-priority and fixed promptly
- This statement is reviewed and updated whenever the accessibility status of Recoverion changes materially