Accessibility

Redi Always exists because most software assumes things about the people using it — a smartphone, a steady hand, good eyesight, patience for menus. We started from the opposite assumption. This page describes what we have built, what we have tested, and where we still fall short.

1. Why Redi Always Is a Phone Call

The most significant accessibility decision we made is the product itself. Redi Always works through an ordinary phone call. There is no app to install, no account to navigate on a small screen, no touch targets to hit, no text to read, and no updates to keep up with. Anyone who can make a phone call can use Redi Always in full.

That matters for people with low vision or blindness, arthritis or tremor, cognitive or memory difficulties, low digital literacy, or simply no smartphone. A phone call remains the most widely accessible interface there is, and it is our primary one — not a fallback.

2. The Website

You only need the website once, to set up your account. We have built it to be usable without sight, without a mouse, and without fine motor control:

• Screen readers — every control has a descriptive label, form fields are properly associated with their labels, and each step of sign-up is announced as you reach it, so you are never left wondering whether something happened.
• Keyboard only — every control can be reached and operated by keyboard, focus is always visible, and a "skip to the sign-up form" link is the first thing you reach.
• Text size — type is set in relative units, so if you have made text larger in your browser or phone settings, the page scales with your setting instead of overriding it. The page also works at 200% zoom.
• Contrast — body text and controls are set to meet WCAG 2.1 AA contrast ratios.
• Motion — if your device is set to reduce motion, all animation on the site stops. The decorative messages that drift beside the sign-up form are hidden from screen readers entirely; they carry no information you need.
• Typing less — the phone field raises a numeric keypad, and name, email and number can be autofilled by your device.
• No time limits and no CAPTCHA — nothing on the sign-up form expires while you are filling it in, and you are never asked to identify blurry images.

3. Redi Always Himself

• He is built to be spoken to normally. There are no commands to memorize and no wake words.
• He waits. If you need time to find something or think, the line stays open.
• He will repeat anything, more slowly, as many times as you want.
• He can read letters, forms, labels and screens aloud if you point a camera at them.
• He can stay on the line while you do something difficult, rather than hanging up and leaving you to it.
• You can reach him by text or email instead of calling, and he responds the same way in each.

4. Where We Fall Short Right Now

We would rather tell you this than let you discover it:

• We have not yet had an independent accessibility audit. Everything above is our own testing. We intend to commission one, and we will say so here when it is done.
• Our accessibility work so far has been built in and reviewed in code — not yet verified by hand with a real screen reader. Labels, announcements, focus order and contrast are all in place and checked against the standard, but we have not yet sat down with VoiceOver, NVDA or JAWS and worked through sign-up the way a blind user would. Until we have, treat this page as a statement of intent backed by careful construction, not by proof. It is our next piece of accessibility work.
• Redi Always speaks and understands English best. Other languages work but are not yet at the same standard.
• Redi Always does not currently support TTY or TRS relay calling. If you use one, please tell us — it moves up our list.
• Speech recognition is less accurate for some speech patterns, including strong dysarthria and some accents. If Redi Always mishears you often, tell us, and use text or email in the meantime.
• The waveform artwork on our pages is decorative and unlabelled by design; it carries no information.

5. Standard We Are Working To

We are working toward WCAG 2.1 Level AA. We are not claiming conformance, because we have not been audited. We are telling you the target we design and test against.

7. Telling Us It Is Not Good Enough

If you have reported something and are not satisfied with our response, say so directly to support@redialways.com with "escalate" in the subject line. That goes straight to the person responsible for Redi Always, not into a queue.

8. Keeping This Page Honest

We review this statement whenever we make a significant change to the website or to Redi Always, and at least twice a year. If something here is no longer true, that is a bug — please tell us.