Accessibility at Unsay Apps
Last updated: 5 October 2026
Our aim
Our apps are built around quiet, unhurried attention, and that only works if people can use them in the way that suits them. We aim for the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA on this website, and for each platform's own accessibility features in the apps. This page says what we have done, what we have checked, and where we know we fall short.
If something doesn't work for you, please tell us at unsayapps@pm.me. We read every message and will reply.
This website
The site is plain HTML and CSS with no scripts. What we have done:
- Structure. Every page has a language set, a unique title, one main heading, headings in order, and labelled landmarks for the header, navigation, main content and footer. A “Skip to content” link is the first thing a keyboard user reaches.
- Keyboard. Everything can be reached and used with the keyboard alone. The focus outline is a clear two-pixel line, and the current page is marked in the navigation.
- Colour and contrast. Body text is dark brown on parchment at about 14:1. Secondary text and links are at least 4.5:1. Links are underlined, so they never rely on colour alone. If your device is set to increase contrast, the site darkens its greys and lines.
- Text size. Type is sized in relative units, so it follows your browser's default text size, and pages zoom to 200% or more without losing content. Lines are kept to a comfortable length.
- Motion. Nothing moves, flashes or plays automatically. Smooth scrolling is switched off if you ask your device to reduce motion.
- Small screens. The layout reflows to a single column on a phone, with comfortable space around links and buttons.
- Plain language. We write simply and avoid jargon where we can.
How we checked
We calculated the contrast of every text and background colour pair, ran the automated axe-core checker over every page, and tested with the keyboard and at narrow widths. We have not yet had the site tested by people who use screen readers, magnifiers or voice control, and automated tools find only part of the problems. That feedback would be valuable.
The apps
These notes describe what is true today. Each platform's own accessibility settings are the main route to accessibility in our apps, and none of them has yet been independently audited.
Abeyance
Built with VoiceOver, Dynamic Type, Increase Contrast and Reduce Motion in mind. Controls are labelled, and a day's quote, its source and its tradition are read as one statement. Text follows your preferred reading size, Bold Text is honoured, and the quote is set larger on iPad and in the Mac window. Contrast has been calculated for every text tier on all nine palettes, with quiet text at least 4.7:1, and you can choose your light and dark colours separately. Decorative animation holds still when Reduce Motion is on. Standard system controls are used throughout.
We have not yet checked with VoiceOver or Voice Control on a real device. The Mac and Apple Watch versions have no automated accessibility audit yet, and we have looked at the largest text size only on the main screen and in Settings.
Hesychia
Key controls carry VoiceOver labels, including the full-screen control for logging a return, which is a real button rather than a hidden gesture, and the decorative scenery is hidden from VoiceOver. Every look of the sit tells VoiceOver the time remaining, the text boxes are named, each word you can keep in meditatio has a larger tap area, and the welcome page dots are a plain label rather than something to tap. Text follows your text size, with changes for the largest sizes. The clock digits follow Bold Text, and the sit's closing ring and the watch respect Reduce Motion. The typeface choice includes Atkinson Hyperlegible, which was designed for low vision, and there are nine colour palettes as well as your device's light and dark setting. A contrast test covers every palette.
Apple's automated accessibility audit runs on each screen, and our landscape tests, which also run on iPad, pass on iPhone and iPad. The audit still reports a few things we have chosen to leave: tab labels that stop growing at the largest standard size, because they broke letter by letter. Its own contrast check misread text over gradients, so contrast is held by a separate test of every palette instead. We have not yet checked with VoiceOver or Voice Control by hand, Reduce Motion has been checked by reading the code and not seen with the setting on, and there is no specific handling for Increase Contrast yet.
Kindwisp
Not yet released, and being tested privately. It is being built with VoiceOver descriptions for every element, a way to explore each room as a list of places, VoiceOver actions for untying a balloon and placing a gift, larger text sizes, Reduce Motion, and written words alongside voice gifts. None of this has yet been checked by hand on a device.
Reckon
Not yet released, but built and tested. Outcomes are shown with a shape and a word as well as colour. The calibration curve comes with a sentence summary and a table, and with VoiceOver the chart can also be played as sound (Audio Graphs). Text scales to every size, there is an optional dyslexia-friendly typeface for predictions, and animation follows Reduce Motion. The app is built for VoiceOver, Voice Control, Switch Control and Full Keyboard Access. Automated accessibility audits run on every screen, and contrast tests check WCAG AA in every appearance and accent colour. Still to do: checking by hand on a real iPhone with VoiceOver, checking the Mac version, and testing with people who use assistive technology. We will update this page with what we find.
Known limitations
- No dark mode on the website. The site is parchment only and does not follow your device's dark setting.
- Apps in development. Reckon is not yet released, and the notes above are intentions and known gaps rather than a finished record.
- Not yet tested with users. People who use assistive technology have not yet reviewed the site or the apps.
Contact and feedback
Email unsayapps@pm.me to report a barrier, ask for information in another form, or suggest an improvement. Please say which page or app, and which device and assistive technology you were using, if you can.