Yenlio
Accessibility

Accessibility statement for Yenlio

Last reviewed: 1 July 2026

Nursery Room Ltd is committed to making Yenlio accessible, in line with the Public Sector Bodies (Websites and Mobile Applications) Accessibility Regulations 2018 where applicable, and as a matter of good practice for all our users — nursery staff, childminders and parents.

How accessible Yenlio is

We aim to meet Web Content Accessibility Guidelines (WCAG) 2.2 Level AA across:

  • the web admin app (desktop and mobile/responsive) at app.yenlio.app;
  • the marketing and support site at yenlio.app and the help centre at help.yenlio.app;
  • the iOS mobile app (assessed against WCAG 2.2 via WCAG2ICT / EN 301 549).

Yenlio is currently partially conformant with WCAG 2.2 AA: most of the guidelines are met, and the remaining items are being actively remediated.

What we have done

  • Brand colours that carry text meet the 4.5:1 contrast minimum (a deeper teal is used for buttons, links and teal text; the brand teal remains for larger fills and accents).
  • Icons, status symbols and photos used as meaningful content have text alternatives for screen readers; status is never conveyed by colour alone.
  • Forms have programmatic labels, errors are identified in text with suggestions, and inputs declare their purpose for autofill.
  • Two-factor and one-time-code entry supports paste and password-manager / OTP autofill (no "type each digit" boxes that block paste).
  • Sign-in does not require remembering a code. On the mobile apps you can sign in with Face ID / Touch ID / fingerprint (biometric unlock), as an alternative to entering a PIN — so authentication does not depend on recall.
  • Visible keyboard focus, skip-to-content / landmark navigation, and reflow at 320px / 200% zoom on the web surfaces; descriptive per-page titles on the marketing and help sites.
  • In-app dialogs are announced and keyboard-operable (Escape to close, focus moved into and restored from the dialog).
  • A "reduce motion" preference reduces non-essential animation on the web surfaces.

Documented exceptions (known and intentional)

Page titles inside the secure app (WCAG 2.2 SC 2.4.2). Within the secure app, browser page titles are intentionally generic ("Yenlio") to protect children's privacy — we keep page detail and children's names out of browser history and tab labels by design. The in-page heading on every screen describes its content, and the marketing and help sites use full descriptive page titles.

Known limitations (being worked on)

  • Screen-reader and keyboard verification (VoiceOver on iOS, NVDA on Windows, keyboard-only) was completed per surface on 30 June 2026. A full per-screen VoiceOver sweep of the long tail of mobile screens continues; some deep screens may still announce an unlabelled control.
  • The handwritten signature pad is, by its nature, a drawing gesture; the signer's name is captured separately so signing does not depend on fine motor drawing for identity, but the pad itself has no non-drawing alternative (a WCAG essential exception).
  • The Android app is not yet released; it reuses the same accessible code and will be verified before launch.

Feedback and contact

If you cannot access any part of Yenlio, or want to request information in a different format, contact us:

We aim to respond within 5 working days.

Enforcement

If you are not happy with our response, in the UK you can contact the Equality Advisory and Support Service (EASS).

Technical information

This statement applies to Yenlio's web app, marketing / support / help sites and iOS app. Yenlio is partially conformant with WCAG 2.2 AA; non-conformances and exemptions are listed above.

  • Statement prepared: 1 July 2026.
  • Last reviewed: 1 July 2026.
  • Last tested: 30 June 2026 by Arif Ali (Founder / Director) and the Yenlio team — method: axe-core (0 violations on the static sites and app public landing) plus VoiceOver (iOS), NVDA (Windows) and keyboard-only testing, per surface.
  • Approved by: Arif Ali, Founder / Director, Nursery Room Ltd.