Accessibility

Last updated: October 2, 2026

EyePrompt is made by Beonbrand Inc., a Canadian company. EyePrompt ships as a native app for iPhone and iPad, and a native Mac app. This page covers the iPhone app, and explains how it works with Apple's built-in accessibility features today; the Mac app is not yet documented here, and we would rather say so than let this page imply a commitment we have not tested. The iPad app is the same app with a wider layout; it has not been documented separately yet. We want EyePrompt to be usable by as many people as possible, and we treat accessibility as part of building the app well, not as an afterthought.

This statement describes what the current App Store version supports. Where something is planned but not yet built, we mark it clearly as future or aspirational so you know what to expect right now.

Our commitment

We build EyePrompt with Apple's standard interface tools and design toward the goals behind the Web Content Accessibility Guidelines (WCAG), such as content that is perceivable, operable, understandable, and robust. We aim for that spirit across the app. We do not claim any formal WCAG certification or third-party accessibility audit, and we will not overstate where we are. If you find something that does not work well for you, we want to hear about it, and we will work to improve it.

What EyePrompt supports today

VoiceOver

EyePrompt is designed to work with VoiceOver, the built-in screen reader on iPhone.

On most screens, including the Library, Editor, Rehearse, Review, Settings, and the subscription screen, controls carry standard labels so VoiceOver can describe them in the usual way.

The recording screen is different by design. It keeps its controls few and out of the way: Close, Record and Switch camera, a small settings rail before you record, and a Stop button and a speed tray during a take. For VoiceOver, the screen itself is one element that speaks its status, for example how long you have been recording and how far you are through the script, with a hint for the main action. The settings rail and the speed tray are separate elements you can reach normally. To reach the other recording controls, use the VoiceOver rotor, which offers these custom actions:

You can also leave the recording screen with the VoiceOver escape gesture (a two-finger Z).

Treating the recording screen as one spoken, status-announcing element is an intentional choice. Reading out every part of a live camera screen, item by item, would add noise rather than help. We know this is an unusual pattern, and we are open to feedback on how it feels in practice.

Dynamic Type

Text outside the prompter follows your Dynamic Type setting, so the app's labels, buttons, and other reading text scale to the size you have chosen in iOS.

The prompter text itself is separate on purpose. It is fully adjustable inside the app, so you set the prompter font size to what reads best for you while recording. The prompter starts at a comfortable default size, and your own prompter size choices take over from there.

Reduce Motion

If you turn on Reduce Motion in iOS, EyePrompt changes how its animations behave:

If you prefer the script to move line by line, choose Step as the scroll style in Rehearse. With Reduce Motion on, each step happens without a fade.

Higher contrast

If you turn on Increase Contrast in iOS, the shaded band behind the prompter text becomes a solid, opaque background. This favors plain legibility over the softer look, so the words stay clear against whatever is behind them in your shot.

Haptics always have a visual twin

EyePrompt uses gentle haptic taps to confirm things like the countdown, the start of recording, pausing and resuming, speed nudges, and stopping. Every one of these haptic cues also has a matching visual cue in the reading area, so you never have to rely on feeling a tap to know what happened. This matters for people who are deaf or hard of hearing, and for anyone who prefers to keep haptics off. The app does not depend on sound for any cue, and it plays no interface sounds while the microphone is live, so nothing is captured into your take.

Touch targets

On screens with buttons and other controls, we aim for touch targets of at least 44 points, following Apple's guidance, so they are easier to tap accurately. On the recording screen, the main actions also work with full-screen gestures and hardware buttons.

Eye Contact Score can be turned off

The Eye Contact Score is a measurement of how much of a take you spent looking toward the lens, calculated on your device. It may not work equally well for everyone, for example with glasses glare or certain eye conditions. Because of that, turning the score off is a first-class setting. If scoring does not work well for you, you can switch it off, and your recording is not affected in any way. The score never changes or alters your video. It is only a measurement.

Future accessibility roadmap

The items below are goals we are working toward. They are aspirational and not part of the current version. We share them so you can see the direction, but please do not rely on them being present today, and timing may change.

Tell us what would help

Accessibility gets better when people tell us where it falls short. If a screen, control, label, or interaction is hard to use, or if there is a feature that would make EyePrompt work better for you, please email us at hello@beonbrand.ca.

It helps to include:

A real person reads every message, and we use this feedback to guide what we improve next.


© 2026 Beonbrand Inc. EyePrompt is a product of Beonbrand Inc. Learn more at beonbrand.ca and eyeprompt.app.