Accessibility

This website isn't legally required to publish an accessibility statement — that obligation applies to public administrations — but we built it with the WCAG 2.2, level AA guidelines in mind, and we want to tell you what we've done and what we haven't checked yet.

What we've taken into account

• Contrast. Text colours meet the minimum 4.5:1 ratio against their background, checked across both modes of the interior pages (light and space) and on the homepage.
• Keyboard. The whole site can be navigated without a mouse: a link at the top of every page jumps straight to the content, menus close with Escape and leave nothing hidden but focusable behind them, and the light/space mode selector moves with the arrow keys, like any radio-button group.
• Motion. If you have "reduce motion" turned on in your system, the homepage's animated journey doesn't render, and other animations are trimmed to the essentials.
• Structure. Every page has a single main heading and its sections are in order, without skipping levels, so a screen reader can navigate by headings.
• Images. Ones that carry information have alt text; ones that are purely decorative — the background grain, the product mockups — are marked so a screen reader ignores them.
• Colour. Nothing is explained by colour alone: the states in the product mockups ("in production", "queued"…) also carry their own word.
• Text size. Sizes are set in relative units, so if you increase your browser's font size, the text grows without breaking the layout. Nothing blocks zoom.
• Forms. Every field in the contact form has its own associated label, and errors are explained in text, not just with a colour on the border.

How we checked it

With automated accessibility analysis tools, and by checking the contrast of every colour by hand. It's a good first pass, but it doesn't replace a full manual audit or actually testing the site with a screen reader, which we haven't done yet. Something may have slipped past us.

If something doesn't work well for you

If you run into a barrier using this website — something that doesn't read well, can't be activated with a keyboard, or that a screen reader doesn't announce the way it should — tell us. Write to info@tuinbit.com or use the contact form, let us know which page and which browser or assistive technology you tested it with, and we'll look into it.