How we make this site accessible.

Last updated: October 2026

Our target

We aim for tnttech.io to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. The site is new, so we treat this as a target we check against, not a claim we've certified.

What's in place

Color and contrast

• Every text and control color pair in our design meets AA contrast. We checked all of them when the design was set, and every change to the site is checked again before it's published.
• Color is never the only signal. Each stage color sits next to the stage's name, and status labels (Live, Tested, In build, Planned) use a shape and a word.

Keyboard

• The site works with a keyboard alone. The first stop on every page is a "Skip to content" link.
• Whatever has keyboard focus shows a clear outline.
• On smaller screens the menu opens from a Menu button with Enter or Space, and Escape closes it and returns you to the button.

Structure

• Each page has one main heading, and headings follow in order.
• Pages are marked up with a header, navigation, main content and footer, so screen readers can jump between them.
• Images have text alternatives, and decorative shapes are hidden from screen readers.
• Text sizes follow your browser's font-size setting.

Without JavaScript

• All content is in the page itself, so every page reads in full with JavaScript off or blocked. Nothing is hidden until a script runs.
• The forms need JavaScript. With it off, each form shows our email address and a link to book a call instead.

Motion

• Nothing moves when a page loads, and numbers are plain text, never animated.
• The only animation is a short color change on buttons, menu links and form fields, and it's switched off when your device asks for reduced motion.

Forms

• Every field has a visible label, and fields tell your browser what they hold (name, email, company, website) so it can fill them in for you.
• Buttons and form fields are at least 44 pixels tall, and checkboxes can be ticked by clicking their label.
• If something needs fixing when you send a form, the message appears next to the field, the field is marked as invalid for screen readers, and focus moves to the first one to fix.
• Sending, success and failure messages are announced as status updates.

Checks

• Before any change is published, every page passes an HTML validator that includes accessibility rules.
• Every preview of a change is also tested with axe, an automated accessibility checker.

Known limits

• Forms need JavaScript. If you can't use one, email info@tnttech.io and we'll take your Scorecard request or message that way.
• Booking a call happens on Microsoft's page. Microsoft Bookings is outside our control. If it doesn't work for you, email us a few times that suit you and we'll book the call for you.
• One error isn't read out yet. On the Scorecard form, the message for "What AI have you bought?" shows on screen, but screen readers don't announce it with the checkboxes. We're fixing it.
• Your Scorecard arrives as a PDF. If a PDF doesn't work for you, ask and we'll send it in another format, such as a Word document or plain text in an email.
• No assistive-technology testing yet. People who use screen readers or other assistive technology haven't yet tested the site end to end. Until they have, some things may not work as well as they should, and we want to hear about them.

Tell us about a problem

If something on the site doesn't work for you, email info@tnttech.io. Tell us the page and what happened, and what you use to browse if you can. A person replies within one business day. If you need anything from the site in another format, ask in the same email.

Changes to this statement

We update this statement when the site changes in a way that affects accessibility, and when we fix a known limit.