Accessibility statement

We build against the Web Content Accessibility Guidelines and the platform accessibility guidance from Apple and Google, and we treat accessibility problems as defects rather than enhancements.

We have not completed an independent third-party audit, so we do not claim conformance to a specific WCAG level. When that assessment is done, we will state its scope and result here rather than describe it in general terms.

These are the practices we design and build to, rather than guarantees that every page or component already meets them.

• Aiming for semantic headings, landmarks and page titles so screen readers can navigate structure.
• Aiming for keyboard operation of navigation, menus, dialogs and forms, with a visible focus indicator.
• Adding text alternatives to meaningful images, and hiding decorative images from assistive technology.
• Building responsive layouts that reflow to small screens and stay usable when text is enlarged.
• Associating labels with form fields and writing error messages that do not rely on colour alone.
• Respecting the operating system's reduce-motion setting for animated media.

In the app we work towards the following, screen by screen, as design aims rather than completed coverage.

• Preferring standard system controls so VoiceOver and TalkBack can read and operate them.
• Working towards support for the system text-size setting on the main screens.
• Placing primary safety actions within reach and giving them large touch targets.
• Avoiding colour as the only way state is communicated, with labels and text carrying the same meaning.

We would rather name these than imply everything is finished.

• Map surfaces are visual by nature. Screen-reader users get labelled controls and text summaries, but the spatial detail of a map is not fully conveyed.
• Some third-party components we embed, including checkout and payment steps, are outside our direct control.
• Older blog articles may contain images whose alternative text is thinner than our current standard.
• Colour contrast has not been verified on every single component variant across both themes.

If something on the website or in the app stops you doing what you came to do, email support@imsafe.app and describe the page or screen, the device and assistive technology you were using, and what happened.

We treat accessibility reports as defect reports. Support is not an emergency channel; if you are in danger, contact your local emergency number.