Keyboard and focus
All non-mechanic actions should be reachable without a pointer, with a visible focus indicator and predictable focus after a dialog closes.
Accessibility
More ways to read, play, and take part.
Accessibility work should cover touch, keyboard, screen readers, contrast, motion, sound, language, devices, and printable tools, and state clearly what has actually been tested.
Nurturevia does not currently claim complete accessibility conformance. A scoped route, browser, device, and assistive-technology audit has not yet been published.
Test status
No complete public support matrix yet.
Display preference
High contrast changes the public shell and supported components on this device. Your browser also controls text size, zoom, and reduced-motion preferences.
Design targets
What every released route should support.
Touch and pointer
Important actions should remain large enough to distinguish and use, with no action depending on hover alone.
Visual access
Text, controls, states, and focus should maintain readable contrast. Meaning should not depend on colour alone.
Sound and motion
Sound should be optional, and essential information should have a visible equivalent. Reduced-motion preferences should replace rather than merely slow intense animation.
Small and large screens
Critical actions should remain visible without dock overlap or forced horizontal scrolling across the supported viewport range.
Print and offline use
A printable should identify its paper size, reading order, colour dependence, and whether a low-ink version has actually been checked.
Known limits
Current gaps must stay visible.
Story Steps candidate
The picture sequence communicates changes visually. Brief labels and input alternatives help, but they do not yet reproduce every visual relationship for every screen-reader user.
Claims not yet available
- No published WCAG conformance statement.
- No published assistive-technology and browser matrix.
- No verified language-equivalence or translation coverage.
- No verified camera alternative because camera play is outside the T1 release.
- No response-time promise for accessibility reports.
Report a barrier without sending sensitive information.
Use the adult contact route and include the page address, device or browser if known, what you tried to do, and the format you need. Please do not include a child’s name, diagnosis, records, photographs, or urgent safety information.