Accessibility

Last reviewed October 2026

Our commitment

We want everyone to be able to use ehllo, including people who use a screen reader, larger text, a keyboard instead of a mouse, or captions instead of sound. We design the ehllo website and the ehllo app for iPhone and Android to the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA, the standard the European Accessibility Act builds on.

We are not there yet. Today ehllo partially conforms to WCAG 2.2 level AA: some parts meet it and some do not. This page says which is which, as plainly as we can.

How we checked

In October 2026 we reviewed the code of the website and the app against WCAG 2.2 level AA: colour contrast, labels for screen readers, text alternatives for images, text size, the size of things you tap, keyboard use and focus on the website, and captions for spoken content. We have not yet tested ehllo with people who use assistive technology, and we would welcome your help with that.

What’s in place

On the website

  • Every image has a text description, or is marked as decorative so screen readers skip it.
  • The page language is set, so screen readers use the right voice and pronunciation.
  • We never block zooming, and text sizes follow your browser’s text size setting.
  • A “Skip to content” link is the first thing you reach with the keyboard, and links, buttons and fields show a dark outline when you reach them, which stands out on light and dark backgrounds.
  • Pop-up windows keep keyboard focus inside them, close with the Escape key, and return you to where you were.
  • Buttons that show only an icon, file pickers and text boxes have names a screen reader reads out.
  • Text meets WCAG’s contrast levels: body text is about 17 to 1 against the page and secondary text at least 4.5 to 1. Text boxes, checkboxes and switches have an edge of at least 3 to 1, and our green is never used for text on a light background.
  • Everything you click is at least 24 pixels across, or has that much room around it.
  • Text in the website itself is at least 12 pixels at the default size.
  • Every recording comes with its transcript, for the person who recorded it and for anyone they share the meeting with, next to the recording and the summary.

In the app

  • Text follows the text size you choose in your phone’s settings, with no upper limit.
  • Buttons, switches, tabs and text boxes have screen reader names and roles, and say whether they are on or selected. Headings are marked as headings.
  • When something finishes, such as a save, an error or a reply from ehllo, VoiceOver and TalkBack say so.
  • The app follows your phone’s Reduce Motion setting: animations stop and show a still picture. Decorative animations are hidden from screen readers.
  • Things you tap are at least 24 points across, and most have a 44-point tap area.
  • Text, edges and selected states meet WCAG’s contrast levels, including on every card colour.
  • When you talk to ehllo by voice, what you say and what ehllo says appear on screen as captions. Long replies scroll instead of being cut off, the whole conversation stays on screen during the call, and screen readers read out each reply. Each exchange is also saved as text in Ask ehllo.
  • You can use Ask ehllo by typing instead of speaking; it starts in typing mode.

Known limitations

These are the problems we know about. We plan to fix them and will update this page as we do.

  • Not yet tested with assistive technology users. We checked ehllo against WCAG 2.2 in our code. Until people who use screen readers, switch control or voice control have tried it, there may be problems we have not found.
  • Small text in pictures of the app. On our marketing pages, the pictures that show the app on a phone use small text. The number on the website’s notification bell is also small.

How to report a problem

If something in ehllo is hard or impossible for you to use, or you need information in another format, email us at product@ehllo.io. Tell us what you were trying to do, on which device, and with which assistive technology if you use one. We aim to reply within 5 working days, and we will help you get the task done in the meantime if we can.