Accessibility.

What we build to

The Web Content Accessibility Guidelines, version 2.2, at level AA. In practice, on every page:

• Contrast. Body text and small print meet 4.5 to 1 against their background. The marketing site's faint text was darkened for exactly this.
• Targets. Every button, link in a menu, tab, switch and field is at least 44 pixels tall, above the 24-pixel minimum the guidelines set.
• Keyboard. Everything reachable by mouse is reachable by Tab and the arrow keys, with a gold focus ring that never sits on top of the thing it points at. A skip link is the first thing a keyboard reaches on every page.
• Labels. Every form field has a visible label or an accessible name; every icon-only button says what it does; every image that carries meaning has text, and every decorative one is hidden from readers.
• Real controls. Buttons are buttons, links are links, tabs are tabs, switches are switches, and a screen reader is told the state of each.
• Colour never alone. A right answer gets a tick and the word; a permission gets a word as well as a tint; a progress bar has a value a reader can hear.
• Motion. Animations stop for anybody whose system asks for reduced motion, including the room's opening sequence.
• Captions and transcripts. Any film we publish carries captions, and the words are on the page beside it.
• Structure. One heading hierarchy per page, landmarks for the menu, the content and the footer, and tables with real headers.

What does not meet the bar yet

Saying so is part of the promise.

• Documents you upload. A scanned PDF from a title company is an image, and we cannot make it readable for you. The document editor lets you place fields on it, but the document itself is what it was.
• The pathway map in the room. The climb is a drawing. Every milestone is also a real button with its name, and the list under the gold button carries the same information in words, but the picture itself is not described in full.
• Placeholders for photographs. Some frames on this site are still waiting for their photograph and say so in text. They are marked decorative until the picture arrives.

How we check

Automated tests refuse an image without alternative text, a button without a type, and an element that is clickable without being a button or a link. Beyond that, a person walks the site with a keyboard and with VoiceOver before a release that changes a page's structure. Neither catches everything, which is what the next section is for.

Tell us

If something on this site or in your room does not work for you, email hello@keighbor.com with “accessibility” in the subject, and say what you were trying to do and what happened. A person reads it, and it is fixed or you hear why. If you need something from your room in another form in the meantime, say so and we will send it.