Accessibility

Last updated: August 31, 2026

We want ct.kitchen to be usable by as many people as possible, including people who use screen readers, keyboard navigation, magnification or voice control. This page sets out what we aim for, what we have done, what we know is not there yet, and how to get help.

1. Our aim

We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA. We treat that as the standard to build against and to measure ourselves by.

We are not claiming to have met it in full. No independent accessibility audit has been carried out on this site, so we cannot honestly describe it as conformant. We would rather tell you that plainly than publish a claim we have not verified. The list below describes what is actually in place; the section after it describes what is not.

2. What is in place

• Keyboard access. Navigation, menus, filters, forms and buttons can be reached and operated with the keyboard alone, and the element you are on shows a visible focus outline.
• Screen-reader labelling. Interactive controls carry accessible names. Where meaning is carried by a symbol rather than words — the price-level indicator on product pages, for example — it is exposed as readable text such as “Price level 2 of 5” rather than being read as decoration or skipped entirely.
• Page structure. Pages declare their language, use a single main landmark, and follow a heading order that reflects the content, so a screen reader can navigate by heading and skip between regions.
• Images. Product and project images carry alternative text; images that are purely decorative are hidden from assistive technology so they do not add noise.
• Contrast. Body text, links and accent colours are chosen for contrast against the surface they sit on, and the accent colour is defined separately for light and dark backgrounds so it stays readable on both.
• Reflow. Layouts are fluid and reflow to a single column on small screens without horizontal scrolling, and text can be enlarged by browser zoom.
• Motion. Where the site animates, it respects the reduced-motion setting in your operating system.
• Current page. Breadcrumbs and navigation mark the page you are on, so your position is announced rather than implied by styling alone.

3. Known gaps

We would rather list these than let you discover them:

• No skip-to-content link. The site does not yet offer a link that jumps past the navigation to the main content, so keyboard and screen-reader users currently tab through the header on every page.
• No independent audit. Our accessibility work has been done in-house and has not been checked by an external specialist or against the full WCAG test suite.
• Embedded third-party panels. The request form and appointment calendar on our contact page are supplied by our CRM provider and rendered inside their own frame. We do not control their markup or their accessibility. If either is difficult for you to use, please call or email us instead — the same information reaches us either way, and we would rather take it over the phone than have you struggle with a form.
• Product data from suppliers. Descriptions and specifications come from manufacturers. Some are terse or inconsistently written, which affects how clearly they read aloud.

4. Alternatives to using the site

Nothing on this website is the only way to do business with us. Anything you can do here you can do by talking to a person:

• Browse the catalog, request a quote, book a consultation, or ask about a specific product — by phone or email.
• Ask us to read out product details, prices or specifications, or to send them in a format that works better for you.
• Ask us to complete the design survey with you over the phone rather than filling it in yourself.

There is no charge and no disadvantage to any of these routes.

5. Tell us about a problem

If you hit a barrier on this site, please tell us. It is the most useful thing you can do for us, and we treat it as a defect rather than a suggestion. It helps if you can mention the page address, what you were trying to do, and the browser or assistive technology you were using — but please get in touch even if you would rather not go into detail.

We aim to acknowledge accessibility reports within two business days and to tell you what we are going to do about it, including a timescale if the fix is not immediate. Where something will take time, we will offer you a way to get what you needed in the meantime.

6. Ongoing work

Accessibility is not a task we expect to finish. We review it as we build, we act on the reports we receive, and we will update this page — including the known-gaps list above — as things change. The date at the top shows when it was last reviewed.