Accessibility statement
Our accessibility target, what we have tested, what we know is not yet conformant, and how to report a barrier. Draft pending attorney review.
Our conformance target
We aim to meet WCAG 2.2 Level AA. We do not claim full conformance, because we have not completed a formal audit — and a conformance claim with no exceptions listed is usually false.
What has been tested, and how
- Automated linting for accessibility issues in every build.
- Keyboard-only completion of the matching form, in an automated end-to-end test.
- Skip-link behaviour and focus management on step changes, in automated tests.
- Rendering at 320, 375, 390, 768, 1024, and 1440 pixels wide.
- Full functionality with JavaScript disabled, in a dedicated test project.
- Colour contrast checked against WCAG AA ratios when the palette was defined.
Accessibility features
- Semantic landmarks, correct heading hierarchy, and one h1 per page.
- A skip link to main content as the first focusable element.
- A visible focus indicator that is never removed.
- Form steps as fieldset and legend, with an error summary that receives focus.
- A polite live region announcing each step change.
- Minimum 24×24 pixel interactive targets, and 44 pixel minimum on primary controls.
- The language switcher is a real link with visible language names, not a flag.
- Full support for prefers-reduced-motion; no animation carries information.
- A text alternative for the coverage diagram that is the primary content, not an afterthought.
Known limitations
Stated because a statement without them is not worth reading.
- No formal third-party accessibility audit has been performed.
- No testing with actual screen-reader users has been performed. Automated checks and manual keyboard testing are not a substitute.
- Comparison tables scroll horizontally within their own container on narrow screens. The container scrolls; the page does not.
- PDF or third-party embedded content, if added later, has not been assessed.
Reporting a barrier
If something on this site is not usable for you, tell us what you were trying to do, what happened, and what you were using. We aim to acknowledge within three business days and to explain what we will do and by when.
TODO: supply an accessibility contact email before publication.
Written by: San Antonio Mobile Health Editorial TeamWritten and maintained by the San Antonio Mobile Health editorial team. We are not clinicians. Pages covering clinical topics are held out of search results until a named, credentialed reviewer has approved them.
Last reviewed: August 4, 2026
Last fact-checked: August 4, 2026
Related pages
- Contact San Antonio Mobile Health
We handle platform questions — corrections, privacy requests, provider participation. We cannot answer medical questions or schedule appointments.
- Terms of Use
The terms governing use of this site, including what we are and are not responsible for. Draft pending attorney review.