Our commitment
Voffi targets WCAG 2.2 Level AA for the public website and aims to work with iOS accessibility features in the app. We prioritize tasks that affect account access, care completion, health records, caregiver permissions, and walk safety. Accessibility work includes design, engineering, content, support, and third-party integrations.
Current website support
- semantic headings, landmarks, lists, links, buttons, forms, tables, and native disclosure controls;
- a keyboard-visible skip link and visible focus treatment;
- keyboard-operable site navigation and frequently asked questions;
- text alternatives for meaningful images and decorative treatment for redundant graphics;
- responsive reflow for small screens and enlarged text;
- primary targets designed at 44 CSS pixels or more;
- color choices intended not to carry meaning alone;
- reduced or removed animation when the operating system requests Reduce Motion;
- more opaque navigation when Reduce Transparency is requested; and
- print-friendly Privacy, Terms, deletion, and accessibility pages.
App accessibility intent
The Voffi iOS app is designed around Dynamic Type, VoiceOver labels for icon controls, generous touch targets, light and dark appearances, Reduce Motion, and Reduce Transparency. Important map information should also have readable text context where practical. Individual screens can still vary, and behavior can change across iOS versions and assistive technologies.
Voffi should never depend on color alone for due, overdue, complete, public, private, or error states. Health, medication, walk, and caregiver flows require ongoing large-text and VoiceOver testing before release.
Known limitations
| Area | Current limitation | Planned remediation |
|---|---|---|
| Caregiver web modal | The modal now traps keyboard focus, closes with Escape, and restores focus, but it has not completed a documented multi-screen-reader test. | Complete VoiceOver and additional browser/screen-reader testing before caregiver access is publicly released. |
| Third-party surfaces | Maps, Apple/Google sign-in, App Store billing, and provider-hosted pages have their own accessibility behavior. | Keep accessible alternatives and provider escalation paths where Voffi can. |
| Maps and charts | Dense map or chart visuals can be hard to interpret nonvisually. | Pair essential values and events with summaries, tables, or lists. |
| Formal conformance | No complete independent WCAG 2.2 AA audit report has been published. | Run and document a structured audit after the final launch build and site are stable. |
| Contact alternatives | Pre-launch accessibility feedback currently depends on email; a non-email support channel is not yet available. | Add an accessible in-app or web support form with status tracking before scale requires it. |
Current assessment scope
The July 2026 website review includes semantic markup inspection, keyboard navigation, visible focus, responsive layouts, reduced motion, reduced transparency, zoom/reflow, image alternatives, contrast spot checks, and major screen-reader labels. Before claiming conformance, Voffi still needs documented testing with VoiceOver and at least one additional screen reader/browser combination, forced-colors or high-contrast behavior, 200% and 400% zoom, switch/voice input where practical, and the final caregiver and legal flows.
This statement is a product-owner self-assessment, not an independent accessibility certification.
Report an accessibility barrier
Email support@voffiapp.com with “Accessibility” in the subject. You do not need to disclose a diagnosis or disability. Helpful details include:
- the page, screen, or feature;
- the task you were trying to complete;
- what you expected and what happened;
- device, browser or iOS version, and assistive technology; and
- your preferred reply format.
If ordinary email is not accessible, the current site does not yet offer a separate channel. That is a known limitation, not a request that you disclose private information through someone else.
Updates
Prepared and last updated July 23, 2026. This statement will be revised when a material barrier is fixed, a new support channel opens, or the formal testing scope changes.