Audited, not asserted.
Lintel is a display people read in passing and an admin people work in. Both are tested against WCAG 2.2 AA on every screen, and this page says how, what that covers, what it does not, and how to tell us when something is wrong.
The standard
We aim for the Web Content Accessibility Guidelines 2.2 at level AA across the board and the admin. The board is a public display; the admin is a web application used with a mouse, a keyboard or a screen reader. Both are built without a framework, from semantic HTML, and both are tested the same way.
How we test
Every release is run through axe-core, version 4.10, in Chromium, with the WCAG 2.2 AA and best-practice rule sets, on every page of the admin and every slide type of the board. The current build reports zero violations. Beyond the automated pass, each admin page is walked by keyboard alone, and the board is read with a screen reader to check that slides are announced as they change. The last full pass was on 10 September 2026.
The board
- Every colour pair clears 4.5 to 1, including the smallest utility type. Muted tones are derived from the theme and pushed until they clear the same ratio.
- State is never carried by colour alone. A room is Occupied in words, in a filled pill and in its layout; the connection marker is a solid square when connected, hollow when the reading is old, a hollow diamond when offline, and the words say the same.
- Each slide is a labelled region. Slides not on screen are hidden from assistive technology; the health line is a polite live region; schedule blocks describe their times in words.
- Only opacity and colour animate, and the system's reduced-motion setting turns that off.
The admin
- A skip link, one main landmark, a navigation landmark with the current page marked, list semantics on row groups, tab roles on tabs, dialogs labelled by their heading, and a page title that changes with the route. On navigation the page heading takes focus so the change is announced.
- Every input, select and textarea has a programmatic label. Help text and errors are tied to their control, and errors are also written in words at the top of the field.
- Every control meets the 24 pixel target minimum; primary controls are 44 pixels.
- Sign-in requires a hardware security key or passkey. Keys work with the same assistive technology as any other WebAuthn sign-in; recovery codes are offered for the case where a key cannot be used.
Your theme
When you apply your brand, each colour pair is measured as you type and again on save. A pair below 4.5 to 1 is refused with the ratio it reached, so a theme that would fail cannot reach a wall. An accent close to the background is allowed; filled elements then draw an edge in the text colour so they still read.
Known limits
- The board is a display for people passing it. The same information is available in the admin, which is where a person who cannot see the wall would read it.
- Web embed and YouTube slides carry third-party content we do not control.
- Album art on the Spotify slide is decorative and has no alternative text by design.
- This website itself is tested the same way as the product, but it is early and will change; report anything that gets in your way.
Report a problem
If something on the board, in the admin or on this site does not work for you, write to us through the contact page or email [CONTACT EMAIL]. Say what you were trying to do, what happened, and which assistive technology you use, if any. We reply within two working days and fix confirmed problems in the next release.