Accessibility
PaceOut is designed to be calm, readable and usable across the devices and input methods that families use. This page describes our approach and how to tell us when something gets in the way.
A commitment, not a certification
We work toward WCAG 2.2 AA principles on the website and use Apple accessibility capabilities in the app where supported. We do not claim that every page, state, device or third-party surface conforms in full.
We test keyboard navigation, visible focus, skip links, menu focus return and logical reading order on key website flows.
We use semantic headings, labels, status messages, responsive layouts and contrast checks for the main surfaces.
The website respects the reduced-motion preference. Motion is not required to read the product story or use the core controls.
The native app is intended to work with VoiceOver, Dynamic Type and system accessibility settings where the relevant Apple framework supports them.
1. Website accessibility
Key website flows are built with semantic HTML, labelled controls, skip navigation, visible focus styles, responsive text and layout, and status announcements for interactive tools. We check the home page, navigation, Plan Builder, support form and legal pages at mobile and desktop widths. Automated checks help us find defects but do not prove accessibility for every person or assistive technology.
2. PaceOut app accessibility
The native app uses SwiftUI and Apple platform services. Where supported by the interface, users can use VoiceOver, Dynamic Type, Reduce Motion, system colour settings and other Apple accessibility features. Family Controls, Screen Time, Apple Watch, widgets and notification surfaces are partly controlled by Apple and may behave differently across operating-system versions.
3. Known boundaries
We have not completed a conformance audit of every route, native screen, signed release, third-party provider, Apple extension or assistive-technology combination. Product artwork, animated states, browser differences and provider-generated surfaces can create barriers. A successful automated or visual check is evidence for the tested state only.
4. Tell us about a barrier
Tell us what you were trying to do, the page or app screen, device and operating system, assistive technology if relevant, and the barrier you encountered. Please do not include a child's name, private health information, Screen Time selection or other unnecessary personal information.
Contact support@getpaceout.com for product help or legal@getpaceout.com for a formal accessibility, privacy or safety concern. We will acknowledge the report and use it to prioritise a practical response. If you need an alternative format or route, say so in your message.