lumi. Accessibility Statement — current accessibility status, known issues, and commitments for improvement.

lumi.
Accessibility statement
Last updated: May 2026  ·  Private beta
lumi. is committed to being usable by as many people as possible. This statement is honest about where the app currently stands, what known issues exist, and what lumi. intends to improve. It is not a declaration of full compliance — lumi. is in early development and accessibility work is ongoing.
1 — About this statement

This accessibility statement covers the lumi. web application. lumi. is operated by Sarah-Jane Barton trading as lumi. It is a private individual's product, not a public sector body — it is therefore not legally required to meet the Public Sector Bodies Accessibility Regulations 2018. This statement is published voluntarily because accessibility matters to lumi. and to the users lumi. is designed to serve.

The target standard is WCAG 2.1 Level AA. lumi. does not currently meet this standard in full. The known gaps are documented below alongside a commitment to address them.

2 — What lumi. does well

The following accessibility considerations are built into lumi.'s design and reflect deliberate choices made during development.

In place
Colour contrast
The lumi. colour palette is designed with readability as a core constraint. Primary text (#2C2825 on #FDFAF7) exceeds the WCAG AA contrast ratio of 4.5:1 for normal text.
In place
No reliance on colour alone
Life area colour pips are always accompanied by a text label. Sentiment labels use language (Uplifting, Okay, Heavy) rather than colour alone to convey meaning.
In place
Sentence case throughout
All UI copy uses sentence case. No ALL CAPS labels anywhere in the interface — a deliberate design rule that aids readability for users with dyslexia and cognitive differences.
In place
Large tap targets
The primary record button is 76px — well above the WCAG 2.5.5 recommended minimum of 44px. Core interactive elements follow the same principle.
In place
Voice-first input
All entry capture can be done by voice. Text is always available as a fallback — no feature requires voice-only input. This benefits users with motor difficulties or those who find typing difficult.
In place
No time limits
No features in lumi. impose time limits on user interaction. There are no timed modals, auto-dismissing alerts, or session timeouts that would disadvantage users who need more time.
In place
No motion by default
lumi. uses minimal animation. No looping, flashing, or high-motion elements are present in the interface. Transitions are subtle fades only.
In place
Plain language
All UI copy, AI-generated content guidelines, and in-app text are written in plain English. The reading level is kept as low as the content allows.
3 — Known issues and gaps

The following are known accessibility gaps in the current version of lumi. They are documented honestly here and will be addressed in order of impact.

Issue Status Detail
Screen reader support Not tested lumi. has not been tested with screen readers (VoiceOver, NVDA, or JAWS). ARIA labels, landmark roles, and focus management have not been formally audited. This is the highest-priority accessibility gap.
Keyboard navigation Partial Basic keyboard navigation works via browser defaults, but focus order and visible focus indicators have not been fully verified across all screens. Some custom components may not be fully keyboard-accessible.
Audio transcription accuracy Variable lumi. uses OpenAI Whisper for transcription. Accuracy varies with audio quality, accent, and speech pattern. Users with speech differences may experience lower transcription accuracy. Text input is always available as an alternative.
Colour palette — secondary elements Partial Warm-mid text (#8C7B6E) on surface (#FDFAF7) is used for secondary labels and metadata. This combination has not been formally verified against WCAG AA for all text sizes. Primary text passes; secondary text is under review.
AI-generated content — readability Partial AI-generated summaries and signals aim for plain language but are not systematically checked against a readability standard. Some outputs may be complex depending on entry content.
Mobile browser compatibility Partial lumi. is tested primarily on Safari (iOS) and Chrome (Android). Compatibility with assistive technologies on mobile browsers has not been formally tested.
Error messages In progress Error states (failed uploads, processing errors) exist but have not been reviewed for clarity or screen reader accessibility. Improvements are planned.
4 — Neurodivergence considerations

lumi. has a particular interest in being usable by neurodivergent users — including people with ADHD, dyslexia, autism, and anxiety. Several design decisions reflect this directly, beyond standard WCAG requirements:

  • No streaks, scores, or gamification — these create pressure that can be counterproductive for many neurodivergent users
  • No notifications by default — the app does not interrupt; it waits to be opened
  • Sentence case and plain language throughout — aids processing for users with dyslexia and reading difficulties
  • Voice-first capture reduces the blank-page friction that can be a significant barrier for users with ADHD or executive function difficulties
  • The skip permission feature ("Nothing much today →") reduces the all-or-nothing pressure of daily journalling
  • One question at a time in onboarding — no overwhelming forms
Formal accessibility testing with neurodivergent users has not yet been conducted. This is identified as a priority for the period before public launch, particularly given lumi.'s potential fit for this audience. lumi. is exploring a connection through the Twocan mentoring network for input from people with lived experience.
5 — Commitments

Before public launch, lumi. commits to:

  • Conducting a screen reader audit (VoiceOver on iOS as the minimum, given lumi.'s mobile-first design)
  • Verifying keyboard navigation and focus management across all screens
  • Formally checking warm-mid text contrast ratios and adjusting if needed
  • Reviewing and improving all error message copy for clarity and accessibility
  • Seeking input from at least one neurodivergent user before launch

This statement will be updated as issues are addressed. The date at the top of this page reflects the most recent update.

6 — Feedback and contact

If you experience an accessibility barrier while using lumi., or if you have suggestions for improvement, please get in touch. Feedback on accessibility is taken seriously and responded to promptly.

Contact: lumi.journalling@gmail.com

If lumi. is not working for you and you need an alternative way to access your data or account, lumi. will work with you directly to find a solution.