Accessibility statement

Accessibility at Remem

An app used one-handed, outdoors, in a hurry has to work for people who are not looking straight at it. Remem aims to make place-based capture and planning understandable and operable by more people. This page separates what the website already supports from the goals and limits still being tested in the Apple and Android apps, without claiming credit for either in advance.

Updated 31 August 2026

This website

Accessibility support built into these pages

Semantic structure

Pages use landmarks, ordered headings, descriptive links, labelled navigation and data tables with header cells.

Keyboard access

Links and disclosure controls can be reached by keyboard. A skip link moves focus past repeated navigation to the main content.

Visible focus

Keyboard focus receives a visible outline so the current interactive item is easier to identify.

Responsive reading

Layouts adapt to smaller screens, and navigation can scroll horizontally rather than forcing links outside the viewport.

Reduced motion preference

The website respects the operating system’s reduced-motion preference by suppressing non-essential transition duration and smooth scrolling.

Plain-language answers

Key pages lead with the answer, expand abbreviations such as CSV and GPX, and state feature limits without relying on colour alone.

Apple and Android apps

Current design goals

Multiple ways to capture

Remem offers voice and typed capture so speaking is not the only way to create a pin. When location is on and available, Remem saves it automatically. Signed-in Free allows up to two photos per pin; Premium allows up to ten for additional visual context.

Primary app controls are designed with a target of at least 44 by 44 device-independent pixels, but individual flows still require continued accessibility review.

Clear state and wording

The design goal is for labels to describe the action or result, with errors explained in direct language and destructive actions distinguished from ordinary controls.

Signed-out Home and List provide immutable examples before an account is required. Creating a real pin requires sign-in so ownership is exact from the start.

Known challenges

Areas that may still create barriers

Map-based information

A map is spatial and may be harder to interpret without sight or precise touch. The list view provides another way to approach saved pins, but equivalent detail should be checked flow by flow.

Voice and speech recognition

Speech recognition can mishear words, accents, names or speech affected by background noise. Review captured text and use typed input when it is more reliable.

Photos and recordings

A photo may need a written description to remain meaningful, while a recording may not suit users who cannot hear it. Add useful text where possible.

Third-party interfaces

Operating-system permission screens, email sign-in, purchase screens and exported-file destinations are provided partly by other services and may have their own accessibility behaviour.

Report an accessibility barrier

Tell us what stopped you

Include the page or app screen, what you were trying to do, your operating-system version, device model and assistive technology if relevant. You do not need to disclose a disability or send private pin content.

Email accessibility feedback