Accessibility Statement
Life Maintenance · lifemaintenance.io
Effective September 7, 2026 · Version 1.0
The short version: we aim to meet WCAG 2.1 Level AA across the website, the web app, and the mobile apps. Most of it does. This page says honestly what does not, and gives you a direct route to tell us about anything blocking you. We answer within five business days.
Our commitment
Life Maintenance keeps track of the upkeep a household depends on: when the smoke alarm was last tested, when a prescription needs refilling, when the car is due for service. If someone cannot use it, they lose access to their own records. That makes accessibility a functional requirement here rather than a nicety.
We measure against WCAG 2.1 Level AA, which is the standard courts and regulators generally apply under the Americans with Disabilities Act, and which the European Accessibility Act references through EN 301 549.
Where we stand
Partially conformant with WCAG 2.1 Level AA. That means most of the Service meets the standard and some parts do not yet. We would rather say that plainly than claim full conformance we have not audited.
What is in place across the Service:
- Every interactive control has an accessible name, so a screen reader announces what it does rather than reading “button”.
- Images carry alternative text, and decorative images are hidden from screen readers.
- Headings follow a real hierarchy, so you can navigate a page by heading.
- Keyboard focus is always visible, and every control that works with a mouse works with a keyboard.
- Form fields have associated labels, and errors are announced rather than only coloured.
- Colour is never the only way information is conveyed. Status is carried by text or an icon as well.
- Animation respects your system “reduce motion” setting. Turn it on and transitions and celebratory animations stop.
- A “Skip to main content” link is the first thing a keyboard user reaches on every page.
- The mobile apps use native accessibility labels and roles, so VoiceOver and TalkBack announce controls correctly, and text follows your system text size nearly everywhere.
What we know is not right yet
Listing these is deliberate. A statement that claims everything works is not useful to someone who has just hit a barrier.
- No independent audit. Our conformance claim rests on our own testing. We have not commissioned a third-party accessibility audit, and we will update this page when we do.
- Colour contrast has not been verified everywhere. Some secondary and muted text may fall below the 4.5:1 ratio the standard requires.
- Complex tables and charts. The schedule and reporting views convey a lot at a glance, and their screen reader experience is worse than the rest of the app.
- The wall Dashboard is designed for touch on a landscape screen, and is the least tested surface with assistive technology.
- Parts of the mobile app do not handle the largest system text sizes. In the current version, the title at the top of most detail screens stays at a fixed size. At the largest sizes, the values in the schedule and item summary strips and the tab bar labels break in the middle of words. The next app update fixes these. Some numbers and links near the top of Home and a few list screens are still cut off at the largest sizes, and that is on our list.
- Documents you upload, such as a scanned manual or receipt, are stored as you provide them. We cannot make a scanned PDF accessible on your behalf.
Tell us about a barrier
If any part of Life Maintenance is difficult or impossible for you to use, tell us and we will fix it or find you another way through.
- Email accessibility@lifemaintenance.io
- Or use the support page, and mention accessibility so it reaches the right place
Tell us the page or screen, what you were trying to do, and what assistive technology you use if any. We reply within five business days. If a fix will take longer, we will tell you what we are doing and offer a way to get what you needed in the meantime, including doing it for you.
How we keep this from slipping
- Accessible names, labels, and keyboard access are part of how components are built, not a pass afterwards.
- Keyboard-only navigation is checked when a new screen is added.
- The mobile apps are checked with VoiceOver on iOS and TalkBack on Android before a store release.
- Reported barriers are treated as defects with a real priority, not as suggestions.
Formal complaints
We would rather hear from you directly and fix it. If you are not satisfied with our response, US users can contact the Department of Justice Civil Rights Division, and users in the EU can contact the accessibility enforcement body in their member state.
Revision history
- 2026-09-07 · Version 1.0
First published version.