Legal
Accessibility statement
The standard we hold to, how every check runs, and every place it falls short.
What this page covers
This page covers both halves of Formbar: the Mac app you install, and the website at formbar.app. One standard covers both, and this page states it for both. Everything below is checked on every test run.
The standard we hold to
Formbar meets WCAG 2.2 level AA, with every exemption recorded and its reason stated.
Every exemption is written down with the reason it stands. The site holds one and the app holds four, and this page names all five below.
How we check it
We check the standard. On the site, two runs carry that, and both go with the rest of our tests every time.
The first one computes colour. It reads the site's own colour values and works out the contrast of every pair the site actually paints, in light and in dark. A pair that drops under its floor fails the run. Every pair is computed.
The second one drives the site. It runs an automated accessibility audit over every page we ship, in light and in dark. It walks the site with the keyboard and checks that focus lands where you would expect. It checks that every control tells a screen reader its name, its role and its state. It checks the site at 320 pixels wide and at 200 percent zoom, so every part of the page stays on screen. It checks what the site does when you ask your system for less motion.
The Mac app checks itself the same way. It keeps its own record of the standard and of every exemption on it, and its own tests read that record on every run. A row naming a part of the app that has since gone fails the run.
Where the site falls short
The demo bar on this site draws a red notification badge with white text on it. White on that red reaches 3.54:1. The WCAG floor for text is 4.5:1, so the pair falls short and an automated check flags it.
The colour is the Mac app's own. The app draws its badge exactly that way, and this site matches it. Recolouring it here to pass a ratio would show you a badge the product draws differently. So it stays.
The badge sits inside a picture of the bar. That picture carries its own description for a screen reader, and the bar drawn inside it is hidden from one. WCAG 1.4.3 exempts text inside a picture from the text floor, and the exemption rests on that.
The same colour run computes this exact pair every time and holds it to the number above. Change the badge and the run says so, so this paragraph stays true or the run turns red.
Two calls we made
Two places on the site needed a judgment. Here is each one, so you can weigh it yourself.
Skipping the header. Every page opens with a link that jumps you past the header to the main content. The place it lands takes focus, so a screen reader announces where you are. It takes focus when the link lands you there, and it leaves the focus ring to the controls, because it is a place to land.
Motion. Ask your system for less motion and the site stops its own smooth scrolling. The demo holds on its first beat and gives you a control to play it. Blocks still fade in once as they come into view. We judged a one-shot entrance sits outside the looping, drifting or autoplaying motion that setting is aimed at. Write to us if you read it differently.
Where the app makes an exception
The Mac app records four. Here is each one, with the reason it stays.
Two pictures the app draws are there for the eye alone, under rule 4.1.2. One shows the region a revealed bar stays inside while you size it. The other draws a released item on its way to the slot it lands in. Each is a picture to watch, and the text around it carries what a screen reader reads.
The app's Settings window uses the controls macOS draws itself, and rule 1.4.11 asks that a control's edge reach 3:1. A switch's own fill reaches 1.13:1 against the pane behind it. Those are the system's colours, and macOS alone picks them.
You set how big an item on the bar is, and rule 2.5.8 puts a floor of 24 points under anything you have to hit. What ships is 36 points, well clear of it. You can set it smaller than the floor, and that choice stays yours.
A moving background keeps moving when you ask your system for less motion, which rule 2.3.3 covers. That is a decision we made. Pick a background that holds still and everything on the bar holds still with it.
Report a barrier
Write to [email protected].
The Mac app opens the same message. In the app, open Settings, then General, and use the Accessibility Report section.
Tell us the page or the screen you were on, what you were trying to do, and what stopped you. Plain words are enough, and working out which WCAG rule it is stays our job.
The runs above are what keeps a fix from quietly coming undone.
Changes to this page
We rewrite this page when the standard or any recorded exemption changes, and we say so when we do.