Everyone should be able to read their own data. This statement describes the accessibility of the LMKFR website and local-first app, the standard we aim to meet, the gaps we know about, and how to reach us when something is not usable.
1. Our commitment
Summary
We want LMKFR to be usable by everyone, including people who use a keyboard, a screen reader, magnification, or the operating-system reduce-motion setting.
Full details
Accessibility is treated as a requirement, not an optional extra. We design and test the site so that it can be operated without a mouse, so that its content is exposed to assistive technology through meaningful markup, and so that it respects a visitor's motion and contrast preferences.
2. Conformance status
Summary
We consider LMKFR to partially conform with WCAG 2.1 Level AA.
Full details
“Partially conforms” means some parts of the content do not meet the standard yet. We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA across the marketing pages and the local-first app, and we list the gaps we know about below rather than overstate how compliant we are.
3. How we build for accessibility
Summary
Semantic markup, full keyboard operation, visible focus, and reduced-motion support.
Full details
- Semantic HTML landmarks (header, nav, main, footer) with a logical heading order in every page.
- Every interactive control can be reached and operated with a keyboard alone, and the focused element is always visibly indicated.
- Colour is never the only way meaning is conveyed, and text can be zoomed to 200% without loss of content or function.
- Motion, animation and parallax are suppressed when the operating system is set to reduce motion.
- Images and icons that carry meaning have text alternatives; decorative ones are hidden from assistive technology.
- Text uses scalable units and targets WCAG AA contrast for body and interface text.
4. Known limitations
Summary
Some visualisation and media features still have gaps, which we are working to close.
Full details
- Some data visualisations (for example heatmaps and wrapped-style summaries) rely on colour and canvas rendering and are not yet fully described to screen readers. The underlying numbers are available as text elsewhere in the app.
- Media you import (photos and videos) is played from your own browser storage using the browser's built-in controls, which are not under our control.
- Large archives can take time to decode; we show visible progress, but spoken announcements during long-running operations are limited.
5. Compatibility
Summary
Modern browsers and common assistive technologies.
Full details
The site is built with standard HTML, CSS and WAI-ARIA, and is intended to work with current versions of Chrome, Safari, Firefox and Edge, together with common screen readers (VoiceOver, NVDA, JAWS) and operating-system features such as zoom and high contrast.
6. Feedback and enforcement
Summary
Tell us when something is not accessible, and we will fix it.
Full details
If you encounter a barrier, email privacy@lmkfr.com with the subject line “Accessibility” and a short description of the problem, the page or feature involved, and the assistive technology you use. We aim to acknowledge your message within 7 days and to address the issue within 30 days.
We treat unresolved accessibility issues as bugs, not preferences. If our first response does not resolve the problem, say so and we will keep working on it.
7. Assessment approach
Summary
Self-evaluation against WCAG 2.1.
Full details
This statement was prepared by the LMKFR team through self-evaluation: manual keyboard testing, screen-reader spot checks, contrast checks, and automated audits. It reflects the site as described on this page as of the review date above.