Accessibility statement
This statement covers quantumcraft.uk, the blog included.
Partially conformant with WCAG 2.2 AA
We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. If something on the site gets in your way, email contact@quantumcraft.uk.
Last reviewed
Partially conformant means that most of the site meets the standard and some parts do not yet. The parts that fall short are listed under known limitations.
What we tested
We tested the site ourselves on 10 October 2026, in a Chromium-based browser, on every page in our sitemap and on the not-found page: the homepage, the three service pages, how we work, about, pricing, contact, security, this statement, the work page and its case studies, the legal pages and the blog. We used automated checks with axe-core, keyboard testing and contrast checks. On 11 October 2026 we tested again the pages that had changed (the homepage, the three service pages, how we work, about, pricing, contact, security, this statement, the work page and its case studies), repeating the axe-core, contrast, reflow, larger text and text spacing checks on all of them and the keyboard testing on the homepage and its menus. On 11 October 2026 we tested the homepage, the work page and the Karu and Treble case studies again, after the homepage gained a sixth case study and a list of the platforms we build on and the two studies' screenshots went in, repeating the axe-core, contrast, reflow and larger text checks at desktop and phone widths.
Keyboard
We moved through every page with Tab and Shift+Tab, once with the cookie banner showing and once after dismissing it, then tried the skip link, the Services menu, the mobile menu, the cookie banner and the contact form with Enter, Space, the arrow keys and Escape. The skip link leads to the main content. The gaps this found are listed below.
Structure and labels
Automated checks with axe-core on every page at a desktop and a phone width, and a survey of each page's structure: one main heading, no skipped heading levels, named landmarks, labelled form fields, a name on every button and link, and alt text on every image, with decorative ones hidden from assistive technology. Menus and choices carry their state (expanded, current, checked) in their markup. We did not use a screen reader.
Colour contrast
Text and controls against the WCAG AA contrast ratios, on the light pages and the dark sections. We calculated the ratios for the colour pairs in our palette (text, links, buttons, form edges and focus outlines), ran axe-core's contrast check on every page, measured from screenshots what sits behind the text axe could not decide, and checked the text of every control in its focused state. The exceptions are listed below.
Reduced motion
With your device's reduce-motion setting on, scroll animations, the highlighter's draw-in and all movement in the homepage drawing are switched off: it shows its finished state, and its pause button is hidden because there is nothing to pause. With the setting off, the drawing builds itself once as the homepage loads, in about four and a half seconds, then sways slowly. The pause button in its top right corner stops the sway and the drawing's movement with the pointer and with scrolling, and your browser remembers that choice. No content depends on any of it.
Zoom, reflow and text spacing
At 200 per cent and 400 per cent browser zoom, which is 640 and 320 CSS pixels wide, no page scrolls sideways, apart from the wide tables and code samples noted below. With line, paragraph, letter and word spacing raised to the values WCAG 1.4.12 sets, no text is cut off and no page scrolls sideways at 390 and 1280 pixels wide. The exceptions, and making only the text bigger on a phone-width screen, are listed below.
Where the site falls short
- The keyboard focus outline on a code sample in a blog post is the same colour as the page, so it cannot be seen. The sample still takes focus, and the arrow keys scroll it.
- A table or code sample in a blog post that takes up most of the height of the screen, or more, can sit partly under the fixed header when it takes keyboard focus.
- While the cookie banner is showing, tabbing into the message box of the contact form can leave part of the box behind the banner. Choosing Accept or Reject removes the banner.
- The name and email fields in the contact form do not yet carry the autocomplete attribute that tells browsers and assistive technology what each field is for.
- The contact form needs JavaScript. Without it, email us instead.
- Two case studies, TIYO and the B2B logistics marketplace, show indicative screens drawn with sample data. On the case study pages the screens are drawn in the page and hidden from screen readers, with a caption that says what they show. The cards that link to them use pictures with alt text. Some of the small labels in the TIYO and logistics screens fall below the 4.5 to 1 contrast the rest of the site meets. The figures in the TIYO heat map are down to about 2.5 to 1, and the place names on the logistics map are down to about 1.8 to 1.
- On a phone-width screen, raising only the text size, not the page zoom, to 150 per cent or more can push a line, a card or a button past the right edge of the screen. It starts with the homepage, the blog index and the main heading of the AI product development page, and by 200 per cent it reaches most pages, including the menu button and the send button on the contact form.
- On a desktop-width screen, raising only the text size, not the page zoom, makes the header overlap itself. At 175 per cent or more the company name runs over the Services menu and the last links go under the Start a conversation button, and on a narrower window it starts at a smaller size. On the case study pages, the list under Phases, team and price also runs past the right edge of the screen. It starts at 150 per cent on most of them and reaches all of them by 200 per cent.
- With text spacing raised to the WCAG 1.4.12 values on a screen 320 pixels wide, a long word runs past the right edge and is cut off in three large headings. They are the heading of the Services section on the homepage, the main heading of the AI product development page and the title of the blog post on the AI documentation pack. On the homepage the paragraph under that heading is pushed a few pixels too far as well.
- On a narrow screen, wide tables and code samples in blog posts scroll sideways inside their own box rather than reflowing. Each box takes keyboard focus, so the arrow keys scroll it.
- Screenshots in the case studies are pictures of software we built. Each has alt text describing what it shows, but the words inside a screenshot cannot be read by a screen reader or enlarged with the page's text.
- We tested in a Chromium-based browser only, and we have not used a screen reader such as NVDA, JAWS or VoiceOver. Our checks cover the structure and labels a screen reader relies on, not how any one screen reader reads the pages.
Tell us about a problem
If you find something on the site that is hard to use, or you need information from it in another format, email contact@quantumcraft.uk with the page address and what happened.
This statement was prepared on 10 October 2026, from our own testing of the site.