Accessibility
inCommon is meant for everyone who wants to use it, including people who use a screen reader, a keyboard, switch access, magnification, or larger text. This page says what we aim for, what we have done, where we know we fall short, and how to tell us about a barrier.
The standard we work to
We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA, published by the World Wide Web Consortium. These guidelines explain how to make digital content usable by people with a wide range of disabilities.
inCommon has not yet had an independent accessibility audit. Based on our own testing, we believe it is partially conformant with WCAG 2.1 Level AA: most of it meets the standard, and the known exceptions are listed below.
What we have done
Seeing the screen
- Text is checked automatically against a contrast ratio of at least 4.5 to 1 in every colour theme, at phone and desktop widths. Purple and blue are used for text only in the lighter shades that pass.
- A Higher contrast setting in Settings strengthens borders and accents in whichever theme you use.
- Pages can be zoomed. Nothing in inCommon prevents pinch zoom or browser zoom.
- Colour is not the only way information is shown: rows, readings and chart points carry names and labels as well.
Using a keyboard
- Every control can be reached and used with a keyboard, and focus is always visible.
- A skip link at the start of each screen moves focus straight to the main content.
- Dialogs and sheets keep focus inside them while open, close with Escape, and return focus to the control that opened them.
- Menus can be moved through with the arrow keys, Home and End.
Using a screen reader
- Screens are built with landmarks and headings, and the interface language is declared so a screen reader uses the right voice.
- Changes of screen, tab and selection are announced, whether they are reached by touch, keyboard or a link.
- Form fields have visible labels, and errors are tied to the field they are about.
- The astrology wheel and the Human Design chart are drawings, and each comes with a written summary of what it shows for screen reader users.
- Decorative images and animations are hidden from assistive technology.
Touch and movement
- Controls are at least 44 by 44 pixels, so they can be tapped without precision.
- If your device asks for reduced motion, the animated sky and the moving image on the sign in page hold still.
- Swiping between screens is never the only way to move: every screen can also be reached from the navigation.
Known limitations
- House numbers on the chart wheel are smaller than 44 pixels, because twelve of them have to fit around a circle. The same information is available in the chart’s tables and its written summary.
- The image on the sign in page is a decorative animation drawn with WebGL. It carries no information, and the page’s title, sign in form and links work without it. On a device without WebGL the page shows a short message in its place.
- Contrast in every screen of every theme. Our automated contrast check measures the Today screen in every theme, and other screens are checked by hand when they change. A pairing we have not measured may fall short; please tell us if you find one.
- Services run by others. Payment pages run by Stripe, the sign in check run by Cloudflare, and the websites of crisis lines are outside our control. Each has its own accessibility commitments.
The inCommon apps
The inCommon apps for iPhone and Android, when they are available, are built from the same code as the web app, and this page applies to them too.
Tell us about a barrier
If something in inCommon is hard or impossible for you to use, we want to know. Use Contact Support in the app (Settings, Contact Support) and choose Something is not working. It helps to tell us the screen, what you were trying to do, and the device, browser and any assistive technology you use, but none of that is required.
We will reply to the email address you give us, and we aim to answer within 10 working days. If you need anything on this page or in our Terms or Privacy Policy in another format, ask us the same way.