Back to home

Last updated: June 9, 2026

Accessibility statement

GoalRilla should be usable without needing one perfect way to see, move, or read.

We design GoalRilla so people can use the app with screen readers, voice navigation, larger text, dark mode, high contrast preferences, and reduced motion settings.

VoiceOver

GoalRilla uses semantic page structure, readable labels, visible headings, and named controls so screen reader users can move through goals, chat, matching, and settings.

Voice Control

Primary actions use clear visible text or explicit accessible names, including goal entry, status updates, date selection, sign in, sign up, and theme controls.

Larger Text

The app allows system/browser text scaling and page zoom. Layouts are built to wrap and scroll instead of locking users into a fixed scale.

Dark Interface

GoalRilla includes a persistent dark interface for common tasks, including the dashboard, chat, goals, matching, settings, authentication, and the public app pages.

Differentiate Without Color Alone

Goal states use text labels and icons such as complete, progress, not done, and tomorrow. Selection states also include borders, labels, and pressed states.

Sufficient Contrast

Core screens use high-contrast text, dark outlines, visible focus rings, and system high-contrast fallbacks where supported.

Reduced Motion

GoalRilla honors the reduced motion system preference by disabling decorative motion, animated backgrounds, pulse effects, and nonessential transitions.

Captions and audio descriptions

GoalRilla does not currently require users to watch video or listen to audio to use the app. Captions and audio descriptions are not applicable to the current release. If we add video, voice, or recorded media features, we will provide text alternatives or equivalent accessible controls.

Contact

If something in GoalRilla is hard to read, hear, navigate, or control, contact us at support@goalrilla.app. Include the device, browser or app version, assistive technology used, and the screen where the issue happened.