Accessibility
This is a health benefit, and a health benefit nobody can use is not a benefit. Our members are largely Medicare-age, with a wide range of vision, hearing, dexterity, and comfort with technology. We build for that range on purpose, not as an afterthought.
- Conformance target
- We build and test against WCAG 2.2 Level AA, on every screen, in both desktop and mobile layouts.
- How it is checked
- Automated accessibility checks run against every screen on every change, and a build fails if a serious or critical issue appears or if a new screen arrives without a check. Automated testing cannot catch everything, so it is a floor and not a claim of perfection.
- What we test beyond the automated checks
- Touch targets of at least 44 pixels, complete keyboard operation, that nothing fixed to the screen covers what you are focused on, that sliders work without dragging, and that signing in never depends on solving or remembering something.
- Known limitations
- [SOURCE NEEDED] Any known gaps are listed here honestly, with what we are doing about them and by when. An empty list is a claim, so this section stays until it has been reviewed rather than being quietly omitted.
If something does not work for you
Tell us and we will fix it. You do not need to know why it is broken or what the standard says; describe what you were trying to do and what happened, and that is enough.
[SOURCE NEEDED] A dedicated accessibility contact, a response-time commitment, and the process for requesting materials in an alternate format (large print, braille, audio, or a language other than English) are owed by Aevira. Committing to a response time is not ours to do on their behalf.
This statement describes a prototype built entirely on invented people and invented results. It will be reviewed before the product carries real member information.