Guardian Sarah

Accessibility

Written plainly, for the person using the app and the family they invite. Last updated August 2026.

Guardian Sarah is built for people in their seventies, eighties and nineties — which means accessibility is not a checklist for us, it is the product working at all. Eyes, ears and hands change with age. The app has to keep up, and where it does not yet, this page says so.

What we aim for

We work toward the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA, across the app the older adult uses, the app their family uses, and this website. For text contrast we hold ourselves to the stricter AAA bar of 7:1 wherever we can achieve it, because reduced contrast sensitivity is near-universal past 75 — a standard we chose, not one anyone required of us.

These rules are enforced by automated checks that run before every release, so a fix cannot quietly come undone. When we find something wrong, we record it and track it until it ships — not just fix it and forget.

What is not right yet

We would rather tell you than have you discover it:

No badge, on purpose

We do not claim conformance with WCAG or any other accessibility standard. A conformance claim is a promise that independent testing has verified every page and every screen, and ours has not finished. Until it has, printing a badge would be marketing, not truth. What we can honestly say is on this page: the standard we aim for, what meets it, and what does not yet.

Tell us when something is hard to use

If any part of Guardian Sarah — either app, or this website — is difficult with a screen reader, large text, voice input, a keyboard, or in any other way, we want to know. Email support@guardiansarah.com and describe what you were trying to do. A person answers, usually within one business day, and accessibility problems go to the top of the pile — for this product they are not edge cases.