Accessibility Statement
Crew Sheet is used on a working day, often one-handed, often by someone who cannot look at the screen for long. That is close to how the app is used with VoiceOver, so accessibility work here is not a separate track.
Our commitment
We hold Crew Sheet to WCAG 2.1 Level AA. Where we fall short we say so on this page rather than leaving you to discover it. The known limitations below are specific, current, and include two that affect iPad.
If something is harder than it should be with VoiceOver, Switch Control, Voice Control, or any other assistive technology, email crewsheet@xymex.app. Tell us what you were doing, what you were using, and what happened instead. We reply within five working days.
What is verified on every build
These are enforced by the release pipeline, so they cannot quietly regress between versions.
| Property | How it is enforced |
|---|---|
| Dynamic Type | Every text style scales with your system text size, up to the largest accessibility size. A build fails if any text is declared at a fixed point size — that kind of text looks identical at default settings and only diverges at accessibility sizes, so it cannot be caught by eye. |
| Colour contrast | Thirteen automated checks assert WCAG AA contrast for every text-and-background pairing in the design system, in both light and dark appearance. |
| Colour is never the only signal | Cue phases and custom tag colours always carry a text label or symbol as well, so the information survives without colour vision. |
| Consistent design tokens | Views cannot use raw colours, fonts or spacing. Everything routes through one token set, which is what makes the contrast and text-size guarantees hold app-wide instead of screen by screen. |
What is supported
Vision
| Feature | Status |
|---|---|
| VoiceOver | Interactive controls carry labels, and hints where the result of an action is not obvious from the label alone. A cue announces whether it is done or not done, not just its title — the state is exposed as a value, so it is read on focus. |
| Dynamic Type | Supported to the largest accessibility size. At those sizes some decorative elements are deliberately dropped rather than allowed to crowd the text. |
| Bold Text and Increase Contrast | Honoured through system text styles and semantic colours. |
| Dark appearance | Fully supported and contrast-tested to the same standard as light. |
Motion
Reduce Motion is respected across the app — the first-import celebration, the list stagger, and the Wedding Mode pulse all check the system setting rather than animating regardless. Motion is never the only way something is communicated.
Motor
Crew Sheet uses standard controls and standard gestures — tap, swipe, long-press. No feature requires a multi-finger gesture, so Switch Control, Voice Control and AssistiveTouch work through the system focus order. On iPad see the first known limitation below.
Hearing
Nothing in Crew Sheet requires audio. Cue reminders are notifications with text; sound is the system's, and silent mode and Focus are respected.
Known limitations
These are current as of 1.0 and each has a fix planned.
- Creating an event on iPad, using VoiceOver or a hardware keyboard. The add-event control is a pop-up menu, and iPadOS does not build a menu's contents until it is opened. Two consequences: the ⌘N shortcut does not register, and we have not been able to confirm the trigger is reachable by VoiceOver. The empty state points at that same control rather than offering a button of its own. On iPhone none of this applies. If this affects you, email us — it is first in the queue.
- Seven strings are English in the eleven non-English languages. One of them is the done / not-done state VoiceOver announces on a cue, so a VoiceOver user working in, say, German will hear that one word in English. The rest of the app is translated.
- The Apple Watch app is verified by hand, not automatically. The automated accessibility checks above cover iPhone and iPad. Watch coverage is a manual pass on a real device before each release, which is weaker, and we would rather say so.
How we test
- Automated checks on every build, listed above — text scaling, contrast in both appearances, and design-token conformance.
- Screen captures taken at accessibility text sizes, not only the default, because most layout failures are invisible at default size.
- A manual VoiceOver pass on a physical device before release, covering the main path: event list, event detail, cue detail, marking a cue done.
- This website is checked for a working skip link, correct heading order, and AA contrast in both light and dark, on every build.
Conformance
Crew Sheet 1.0 is partially conformant with WCAG 2.1 Level AA. "Partially conformant" means most of the standard is met, with the documented exceptions above. We have not claimed full conformance because the first limitation may affect a success criterion for keyboard and assistive-technology access on iPad, and we would rather state that plainly than test it loosely and claim more.
Feedback and enforcement
Accessibility problems go to crewsheet@xymex.app. We reply within five working days, and a problem that blocks a core task for an assistive-technology user is fixed in a patch release rather than held for the next feature version.
If you are not satisfied with our response, you may contact the market surveillance authority for the European Accessibility Act in your EU member state.
Legal
This statement is published under the European Accessibility Act (Directive (EU) 2019/882) and refers to EN 301 549 and WCAG 2.1 Level AA. It was prepared on 28 July 2026 by self-assessment against the automated checks and manual passes described above.