Accessibility, built in from the start.

The standard we work to

We build to the Web Content Accessibility Guidelines (WCAG), version 2.2, at the AA level. This is the usual target for a public site run by an institution, and it is the bar we design the work against.

We are honest about where we are: no formal accessibility audit has been run on this site yet, and the work to bring every part of the site to that standard is still in progress. So this page describes the practices we have built in and the target we are working toward, not a certified result. When an audit has been run, we will say so here, with the date and who ran it.

What is already built into this site

These are in the site today, not plans.

• A clear structure. The pages are built with proper landmarks (header, navigation, main content, footer) and a sensible heading order, so software that reads the page aloud can move through it by structure. The page also states its language.
• A skip link. The first thing you reach with the keyboard on every page is a "Skip to main content" link that jumps past the navigation straight to the content.
• Keyboard use. The site is built to be used without a mouse. Links, buttons, and the assistant are all reachable and usable by keyboard.
• A visible focus outline. Every link and button shows a clear outline when you reach it with the keyboard, so you can always see where you are on the page.
• Readable contrast. Text is set to meet the AA contrast level against its background, on both the light and dark parts of the site.
• Motion you can turn off. Any animation on the site is decorative and stops if your device is set to reduce motion. Nothing you need depends on movement.
• A simple, static site. This is a static site with no login and no running application to get stuck in, which keeps it predictable for assistive software.

What we have not finished

We have not closed everything, and we will not pretend we have.

• No audit published yet. We have not yet run or published a formal accessibility audit of this site. Until we do, treat this page as a statement of how we build and what we are working toward, not a certified result.
• Limited testing on assistive software. We have not yet tested the site against a full range of screen readers and browsers, so we are not naming specific combinations as supported.
• The assistant. Aika, the assistant on this site, can be reached by keyboard, but we treat its chat interface as something we are still improving for assistive software.
• Content we do not control. Where the site links to or includes something hosted elsewhere, we cannot promise that other site meets the same standard.

If something here is hard to use

If any part of this site is hard to use, or an access need is not met, write to us at [email protected]. Tell us the page, what you were trying to do, and the device or software you were using if you can; that is usually enough for us to find the problem and fix it. We reply within one working day. If you need information from a page in a different format, ask, and we will provide one.

This is the same care we build into the sites we ship for universities, schools, and regulated bodies. You can read about that work on our web design page.

This statement covers kinyoubiatelier.com. It does not cover our products at separate addresses, which have their own pages. We review this page when the site changes.