DayDare asks people to do something frightening: talk to someone. The app itself should never be the hard part. This page describes what DayDare supports today, how each feature was checked, and where the gaps still are.
01Supported features
VoiceOver
Every control has a label written as a phrase rather than a fragment: the fear scale reads “Before you started: 3 of 5”, a difficulty reads “Difficulty, 4 of 5”, and a ladder badge reads its full name instead of a letter. Section titles are marked as headings, so the rotor can jump through the longest screens instead of swiping past every control. The chosen outcome and the chosen fear rating carry the selected trait. Decorative marks — the DayDare logo, the paper texture, the forecast line in the debrief — are hidden rather than announced, because the numbers and sentences beside them already say the same thing.
The fear trend for each ladder and the calibration of your forecasts are also available as audio graphs: VoiceOver can play them as sound, so you can hear your fear falling rather than only read it.
Larger Text
All text uses Dynamic Type and scales to the largest accessibility sizes. Layouts change shape rather than truncate: rows stack when a line no longer fits, the forecast scale’s markers grow with its numbers, and outcome icons scale with their labels. The app was checked at the largest accessibility size on the smallest supported iPhone.
Sufficient Contrast
All three palettes — Ember, Slate and Paper — in both light and dark appearance are measured, not judged by eye: an automated test resolves every text colour against every background it is drawn on and holds each pair to the WCAG AA ratio of 4.5:1 on every run. The weakest text pair measures 4.5:1 or better; the one exception is held to the large-text threshold of 3:1 because it is only used for 17-point semibold button labels. A colour that fails the test does not ship.
Reduced Motion
With Reduce Motion on, DayDare removes movement rather than making it smaller: the mission card opens as a standard sheet instead of zooming, the logo’s two quotes appear already together, numbers change without rolling, and the forecast marker is simply in place. Press feedback stays as a change of opacity, never as movement.
Reduced Transparency and Increased Contrast
With Reduce Transparency on, footers use a solid surface instead of a blurred material. With Increase Contrast on, the paper texture behind light screens is removed.
Dark Interface
DayDare follows the system appearance or can be set to always light or always dark, independently of the three palettes. Every palette has its own complete dark version with its own measured contrast.
Touch Targets
Buttons, including small text buttons, have a tappable area of at least 44 by 44 points.
02What DayDare does not claim
- Voice Control and Switch Control are not declared. DayDare is built from standard SwiftUI controls with real labels, so both are expected to work, but we have not tested them thoroughly enough to state it — we would rather leave them unclaimed than overclaim them.
- Differentiate Without Color Alone is not declared yet. States such as the chosen outcome and the chosen rating are shown with a fill and announced as selected, but the six ladders are distinguished by colour together with a letter, and we have not audited every screen for this setting.
- Captions and Audio Descriptions do not apply: DayDare contains no video or audio content.
03How this was checked
Contrast is computed by an automated test on every build, for every palette in both appearances. Dynamic Type is checked by rendering screens at the largest accessibility size and looking for clipping rather than assuming there is none. VoiceOver labels and headings were audited screen by screen. Reduce Motion and Reduce Transparency are part of the app’s own rules: each animation and material in the code checks the setting explicitly.
04Found something we missed?
Please tell us. An accessibility problem is a bug, and we treat it as one: write to hello@daydare.app and describe what you were trying to do, which assistive feature you use, and what happened instead. If you can include the iOS version and whether VoiceOver, Larger Text or Reduce Motion was on, it will usually be enough to reproduce it on the first try.
We answer every report, and a confirmed accessibility defect goes to the front of the queue rather than into the backlog.