Accessibility statement
Accessibility at MediAttune.AI
MediAttune.AI is built for independent physicians, including those who rely on assistive technology. We design for accessibility from the start and are working toward WCAG 2.2 Level AA. This statement is an honest account of where the app stands today, what it already does well, what still needs work, and how to reach us.
- Target: WCAG 2.2 Level AA
- Platform: iOS
- Status: self-assessed · formal audit in preparation
Conformance status
MediAttune.AI is partially conformant with WCAG 2.2 Level AA. "Partially conformant" means some parts of the app do not yet fully meet the standard, or have not yet been formally evaluated.
The assessment on this page is a self-review of the app's design and implementation by the MediAttune.AI team. An independent evaluation and a full Section 508 / VPAT® conformance report are in preparation, and this page will be updated when that work is complete.
01Accessibility features built into the app
These are provisions in the current design. Where they map to a specific standard, that is reflected in the summary below.
Designed to work with VoiceOver
The app is built with SwiftUI and standard iOS controls, and uses SF Symbols with text labels rather than emoji, so the iOS VoiceOver screen reader can announce most controls by name and role.
Scalable, high-contrast type
Large type and a high-contrast deep-teal palette support limited vision, with generous spacing so text and targets have room to grow.
Status is never color alone
Important states — such as the warning that a note field is already filled — are conveyed with text and an explicit confirmation step, not by color by itself.
Visual confirmation of audio
A live waveform shows that audio is being captured during recording, so clinicians who are deaf or hard of hearing can visually verify the device is picking up sound.
Biometric sign-in
Face ID reduces manual typing at login and at signing, easing use for people with motor or dexterity limitations.
One action per screen
Primary actions are large and presented one at a time, lowering the precision and cognitive load needed to operate the app.
02Self-assessed conformance summary
Selected WCAG 2.2 success criteria most relevant to a native iOS app. Values reflect the team's current self-review, not an independent audit.
| Success criterion | Level | Status | Notes |
|---|---|---|---|
| 1.1.1 Non-text Content | A | Partially supports | Icon controls carry text labels; alt-text for custom graphics such as the recording waveform is under review. |
| 1.3.1 Info & Relationships | A | Partially supports | Standard SwiftUI structure exposes relationships; custom views are being reviewed. |
| 1.4.1 Use of Color | A | Supports | Color is never the only way status or data is conveyed; text and confirmation steps accompany it. |
| 1.4.3 Contrast (Minimum) | AA | Partially supports | A high-contrast palette is used throughout; a full contrast audit across all screens is pending. |
| 1.4.4 Resize Text | AA | Partially supports | Designed for iOS Dynamic Type; testing at the largest text sizes is pending. |
| 1.3.4 Orientation | AA | Not yet evaluated | Behavior across portrait and landscape has not yet been formally verified. |
| 2.1.1 Keyboard | A | Not yet evaluated | Operability with an external keyboard has not yet been formally tested. |
| 2.4.7 Focus Visible | AA | Not yet evaluated | Visible focus indication is pending verification. |
| 2.5.8 Target Size (Minimum) | AA | Supports | Primary targets meet or exceed the native 44×44 pt guidance; one-action-per-screen keeps targets large. |
| 4.1.2 Name, Role, Value | A | Partially supports | Standard controls expose name, role, and state; custom controls are being reviewed. |
| 4.1.3 Status Messages | AA | Partially supports | Recording and interruption states are shown visually; screen-reader announcement of every status change is pending verification. |
03Known limitations
We would rather be candid than overstate. The following areas are still under review and have not been independently verified:
- Full screen-reader and keyboard operability of custom components — the recording waveform, the e-signature capture, and the Office Ally web-view bridge.
- A complete color-contrast audit across every screen and state.
- Dynamic Type behavior at the largest accessibility text sizes.
- A formal, independent Section 508 / VPAT® conformance evaluation, which is in preparation.
04Feedback
If you run into an accessibility barrier in MediAttune.AI, please tell us — we treat these reports as a priority and aim to respond promptly. Email info@mediattune.ai and describe the problem, the screen, and the assistive technology you were using.