Glimmer — Accessibility Statement

Version 1.0 · Last reviewed 25 September 2026 · Glimmer, by Bitlitic LLC

Bitlitic LLC ("Bitlitic", "we") makes Glimmer, and we want everyone to be able to write in it, read it back and hear it — including people who use a screen reader, larger text, voice input or a switch. This statement covers the Glimmer app for iPhone and Android and the Glimmer pages on bitlitic.com.

Our commitment

Accessibility is part of how we build Glimmer, not a feature added at the end. We test with the accessibility settings built into iOS and Android, fix what we find in order of how much it gets in someone's way, and say plainly below what is not right yet. If something stops you from using Glimmer, we want to hear about it — see Feedback.

The standard we aim for

We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA, published by the W3C. For the app we apply them the way the W3C's guidance on applying WCAG to mobile and non-web software describes, alongside Apple's and Google's own accessibility guidelines.

Conformance status

Glimmer is partially conformant with WCAG 2.2 Level AA. "Partially conformant" means that some parts of the app do not yet fully meet the standard. The known gaps are listed below, with what you can do about each in the meantime.

What already works

  • Text size. The app follows your phone's text size setting, and the journal page has its own text size control in Settings → Writing.
  • Your choice of font. Entries can be written in several handwriting styles or in Urbanist, a clean, plain sans-serif.
  • Light and dark appearance, following your phone or chosen in Settings.
  • Listening instead of reading. Any day can be read aloud by a voice that runs on your phone.
  • Speaking instead of typing. Dictation puts your words on the page as you say them.
  • The website works with the keyboard alone and shows a visible focus outline.

Known limitations

We know about the following, and we are fixing them. Each one comes with a way around it for now.

  • Handwriting fonts can be hard to read. The handwriting styles are part of what Glimmer is, but some are less legible, especially at small sizes or for people with dyslexia or low vision. Workaround: switch to Urbanist in Settings → Writing, and raise the text size there. You can change back at any time, and nothing you wrote is changed.
  • Some colour contrast is too low. A few pieces of secondary text, some white text on the orange accent colour, and one of the green status colours in light mode fall below the WCAG AA contrast ratio. We are correcting them now. Workaround: dark appearance has better contrast for most of these, and turning on Increase Contrast (iPhone) or High contrast text (Android) in your phone's accessibility settings helps.
  • Very large text can cut off some labels. At the largest Dynamic Type and font-scale settings, some buttons and labels are truncated or clipped rather than wrapping. Workaround: a size or two below the largest keeps every label readable, and the journal's own text size in Settings → Writing can still be set large for the page itself.
  • Some controls are not labelled for screen readers yet. A number of icon-only buttons, and some switches, segmented choices and text fields, are not yet announced with a clear name by VoiceOver or TalkBack. Workaround: the main path — writing, sealing a day, reading a reflection and exporting — can be completed with a screen reader; if you get stuck on an unlabelled control, write to us and we will tell you what it does and prioritise the fix.
  • Reading aloud needs a large download. The read-aloud voice runs on your phone, so the first time you use it Glimmer has to download a voice of about 350 MB. The app asks before it downloads anything. Workaround: download it once over Wi-Fi. If you would rather not, your phone's own screen reader or Spoken Content / Select to Speak can read an entry aloud without the download.
  • Motion. Card flips and deck animations follow your phone's Reduce Motion setting only as far as the animation library does by default; they have not yet been designed specifically for it.

Feedback

If you meet a barrier in Glimmer, or need anything in the app or on these pages in a different format, email customer-service@bitlitic.com with "Accessibility" in the subject line. Tell us which phone you are on, which accessibility settings you use, and what happened.

A person reads every message. We will reply within 5 business days, and if a fix will take longer than that, we will tell you what we are doing and when to expect it.

How we assessed Glimmer

This statement is based on a self-assessment by Bitlitic: a review of the app's code and design against WCAG 2.2 Level AA, including measured colour contrast for every colour pair in the app's palette, and testing on iPhone and Android with the platforms' accessibility settings. Glimmer has not been audited by an outside organisation.

Date

This statement was prepared on 25 September 2026 and last reviewed on 25 September 2026. We review it whenever we release a fix listed above, and at least once a year.