Accessibility Statement

Our approach

Blueprint Code AI builds systems that make complex tasks easier to understand and use, and accessibility is part of that. We aim to design our own website and tools so that as many people as possible can perceive, understand, navigate and interact with them — including people who use a keyboard, screen reader, magnification or voice control.

The standard we work to

We use the Web Content Accessibility Guidelines (WCAG) 2.2 as our reference. We are working towards Level AA across blueprintcode.ai and our public tools. Some areas may not yet fully meet that standard.

What we build in

• Full keyboard operation, with a visible focus indicator and a “skip to content” link.
• Semantic headings, landmarks and labelled form fields, so assistive technology can describe each page.
• Colour contrast and readable type sizes on a dark background.
• Form errors and status messages that are announced, not just shown.
• Respect for your system’s reduced-motion setting.
• Meaningful alternative text for informative images.
• Pages that reflow on small screens and at high zoom.

Automated testing helps us catch some issues, but it doesn’t prove conformance on its own, so we also test important journeys by hand.

Known limitations

We are completing a full accessibility review of the site and will list any confirmed issues here, with what we are doing about them. Areas we already know need particular attention:

• Interactive 3D and configurator demonstrations, which may be hard to use without a mouse or sight.
• Older static demonstration pages, which were built before our current standards.

Third-party content

Some services or embedded content come from other providers and are outside our direct control. Where one creates a significant barrier, we will look for a practical alternative or improvement.

Tell us about a problem

If you have difficulty using any part of our website or tools, or need information in a different format, email hello@blueprintcode.ai. Please tell us the page or tool, and briefly what went wrong.

We aim to reply within 5 working days. Where we can’t fix something straight away, we’ll offer a practical alternative — for example, sending the information by email or going through it with you on a call.

Review

We will update this statement as the site develops and as reviews find improvements. The date at the top shows when it was last revised.