Remem aims to make place-based memory capture understandable and
operable by more people. This page separates support that is present
on the website from goals and limits that still need testing in the
Android app.
Updated 5 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.
Android app
Current design goals
Multiple ways to capture
Remem offers voice and typed capture so speaking is not the only
way to create a place pin. Photos can add visual context where
that is useful.
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.
Users should not have to sign in for core local use, reducing an
avoidable barrier to first use.
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
Android 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 Android version, device model and assistive technology if
relevant. You do not need to disclose a disability or send
private memory content.