Back to Seamix Legal centre
Inclusion // WCAG Conformance

Accessibility
Statement.

How accessible the Studio currently is, the known barriers we have not yet fixed, and how to get help or report a problem.

Last updated: 6 September 2026 // Version 1.3 // Governing law: the laws of England and Wales

1. Our Commitment

2. What Works Today

  • Semantic headings, landmarks and page titles so screen readers can navigate structure.
  • Keyboard operation of the main navigation, forms, sign-in and checkout flows.
  • Text that can be resized and reflowed with browser zoom without loss of content.
  • Form fields with visible labels and inline error messages.
  • Generated documents can be exported so they can be read in your own accessible tooling.

3. Known Barriers

  • The Studio makes heavy use of animation and motion. We are working through full support for the reduced-motion preference across every component.
  • Text contrast is now measured directly in a browser, page by page, rather than estimated. Every public page, the studio workspace, the design library, the account screen, the upgrade screen, and the tech pack itself, including its viewer, the points of measure chart, the bill of materials, the assembly step list, the factory readiness report and the full screen drawing preview, meet the 4.5 to 1 minimum for ordinary text and 3 to 1 for large text.
  • Two panels have been measured from their markup rather than with the panels in front of us, because they only appear part way through a generation: the refinement questions and the specification review step. Their text was corrected to the same 4.5 to 1 standard, and we will confirm it on screen at the next opportunity.
  • Small type. The tech pack viewer, and the studio sidebar behind it, use a large number of 10 pixel labels. That is a floor we have set deliberately and now test for, and it replaced sizes as small as 6 pixels, but 10 pixels is still small and some readers will need browser zoom. Text in other parts of the app is smaller in places and we are working through it.
  • The three-dimensional viewport, turntable player and sketch canvas are inherently visual and do not have full keyboard or screen reader equivalents.
  • Automatically generated technical drawings and renders do not yet carry descriptive alternative text.
  • Some interface labels use heavy stylistic capitalisation and technical shorthand that can be difficult for screen readers and for non-native speakers.

4. Getting Help and Enforcement