1. Scope
This statement applies to:
- The Willow mobile and tablet app on iOS, iPadOS, Android, and Fire TV
- The Willow Companion family web app at companion.nemorahealthcaresolutions.com
- Our marketing website at nemorahealthcaresolutions.com (this site)
2. Compliance status
Nemora aims for full conformance with Web Content Accessibility Guidelines (WCAG) 2.2 Level AA.
As of the last review date above, the marketing website and the legal-document pages return zero automated violations against WCAG 2.1 AA when scanned with industry-standard tooling (axe-core 4.11). A small number of best-practice items remain — see section 4 — and we are awaiting an independent third-party audit to confirm full WCAG 2.2 AA conformance.
The Willow mobile and tablet apps have not yet been independently audited. We are running internal accessibility checks scene-by-scene; known limitations are listed in section 4.
3. What we do for accessibility
Beyond WCAG baselines, Willow is specifically designed for residents living with dementia:
- Large tap targets (minimum 60×60 px) and reduced gesture complexity — single tap is the primary interaction.
- High-contrast colour palettes with carer-controllable contrast settings. Text-on-image avoided.
- Calm typography: minimum 16 px body text, 1.5+ line height, no all-caps in body copy.
- Voice prompts via TextToSpeech for incoming-call, message and orientation cards.
- Sundowning Mode automatically reduces brightness, dims notifications and quietens audio in the late afternoon.
- Screen-reader support via VoiceOver (iOS), TalkBack (Android), and ChromeVox (web).
- Reduced-motion mode respects the OS-level setting on iOS, iPadOS and Android; loading shimmer, fade-ins, calm-mode pulses, sundowning tint cross-fades and toasts all switch to instant-snap when the resident has Reduce Motion enabled.
- Captions on family video content where transcripts are provided.
- Carer override — every adaptive feature can be overridden by the carer for the specific resident's needs.
4. Non-accessible content and known limitations
The following content does not yet meet WCAG 2.2 AA. We are working to address each item. Items marked Fixed 06/05/26 were resolved in the most recent in-house pass and will be re-verified by the next external audit.
-
Skip-to-content link on every marketing and legal page,
visible on keyboard focus.
Fixed 06/05/26. -
Visible keyboard focus ring on every interactive element
across the marketing and legal sites, drawn only for keyboard-only users
via
:focus-visible.
Fixed 06/05/26. -
Reduced-motion support across the marketing site —
animations and smooth-scroll now respect the OS-level
prefers-reduced-motionsetting.
Fixed 06/05/26. -
Newsletter form has a programmatic label in addition to
its
aria-label, and now includesautocomplete="email".
Fixed 06/05/26. -
Marketing homepage heading hierarchy.
All marketing-card sub-headings now use
<h3>under their parent<h2>, eliminating level-skipping in the main content flow. Footer column headings remain at<h4>within the<footer>landmark (a separate hierarchy context).
Fixed 06/05/26. -
Mobile navigation menu now exposed as a navigation landmark.
The mobile menu was previously a
<div>outside any landmark; it is now a<nav aria-label="Mobile navigation">so it appears in the screen-reader landmark list.
Fixed 06/05/26. -
Some archival video has no captions.
Willow surfaces material from public archives (Internet Archive, BBC, BFI Player, YouTube). Where the original upload has no captions or transcript, Willow can't add them.
Status: we filter archive results to prefer captioned content, but full coverage is not currently possible. -
Live captions in family video calls.
Captions are generated in the family member's browser via the
Web Speech API and streamed into the active Agora call as a
data-stream message; the Willow app overlays the text on the
call view in 22pt white-on-black at the bottom of the screen.
Captions are off by default and the family member must opt in
per call (CC button in the call controls). Speech recognition
runs locally in the browser — no audio or transcript text leaves
the device for any third-party server, and nothing is retained
after the call ends.
Browser support: Chrome, Edge, and Safari 14.5+ are fully supported; Firefox is not (the CC button is disabled with a helpful toast).
Fixed 06/05/26. -
Personal-video transcript fallback (WCAG 1.2.3).
The Add Personal Video panel now includes an optional
"Transcript or description" field. When the carer fills it in,
the Willow video player reads the description aloud via TTS
when the resident plays the clip and announces it to
VoiceOver / TalkBack — covering home-video footage that has
no caption track on YouTube.
Fixed 06/05/26. -
Unity-app screen-reader labels are partial, not exhaustive.
The Willow app now exposes spoken labels for the persistent navigation
bar, scene transitions, and the privacy / telemetry toggle via a
native VoiceOver / TalkBack bridge (
ScreenReaderBridge+AccessibleButton). Some runtime-created UI inside individual scenes (browse rows, dialog buttons) does not yet have explicit labels; we are extending coverage scene-by-scene.
Status: bridge live as of 06/05/26; full per-scene coverage on the roadmap, expected in [QUARTER YEAR]. -
OS-level reduce-motion preference is now respected app-wide.
Loading shimmer, scene fade-ins, calm-mode colour pulses, sundowning tint
cross-fades and toast fade-in/out all snap instantly when the resident has
iOS Settings > Accessibility > Motion > Reduce Motion enabled, or
when Android animation scales are set to 0×.
Fixed 06/05/26. -
Carer-controlled telemetry opt-out.
Settings now exposes a "Share anonymous usage data" toggle wired to our
Telemetry layer. When off, no analytics events are sent. Persists across
launches and reflected in the carer-handover audit log.
Fixed 06/05/26. -
YouTube captions enforced by default.
Every YouTube embed surfaced inside Willow now passes
cc_load_policy=1&cc_lang_pref=enso captions are automatically on for any clip that has them.
Fixed 06/05/26.
5. Disproportionate burden
We claim no disproportionate-burden exemption. If we ever need to, we will publish the assessment and reasoning here.
6. How we tested
Accessibility was tested by:
- Automated tooling: axe-core 4.11 (axe DevTools) for the marketing website, the Companion web app, and every legal-document page. Accessibility Inspector for iOS and Accessibility Scanner for Android will be used as part of the upcoming Willow-app accessibility pass.
- Manual testing: keyboard-only navigation through every primary user journey on the website, plus visual confirmation of focus indication, skip-link behaviour, and reduced-motion handling. VoiceOver / TalkBack walkthroughs of the Willow app are scheduled for the next testing pass.
- Field review: ongoing — direct observation of residents and carers using the App in care-home settings, and feedback from the partner Care pilot site(s).
The most recent test took place on 06/05/26 by Nemora's in-house engineering team. The website and all legal-document pages returned zero automated WCAG 2.1 AA violations and zero best-practice warnings against axe-core 4.11. An independent third-party audit is planned ahead of any NHS or large care-home rollout.
7. Reporting an accessibility problem
If you find a problem we haven't listed, or you think we're not meeting WCAG 2.2 AA, please contact us so we can fix it:
- Email: info@nemorahealthcaresolutions.com
- Subject line: "Accessibility — <short description>"
We will reply within 5 working days and tell you when we expect to have a fix.
8. Enforcement
In the UK, the Equality and Human Rights Commission (EHRC) is responsible for enforcing the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018. If you are unhappy with how we have responded to your complaint, you can contact the EHRC by visiting www.equalityadvisoryservice.com.
Note: those Regulations apply to public-sector bodies. Nemora is a private company and is not directly bound by them, but we use them as our benchmark because Willow is sold into NHS Trusts and care homes that are subject to public-sector accessibility expectations.
9. Our roadmap
We treat accessibility as continuous work, not a one-off audit. Our current priorities are:
- Live captions in family video calls — shipped 06/05/26
- WCAG 2.2 AAA conformance for the Companion family app
- Independent third-party audit of the App in [QUARTER YEAR]
- Co-design sessions with residents living with later-stage dementia
10. Contact
Accessibility questions or feedback:
info@nemorahealthcaresolutions.com