Accessibility
A price is no use to someone who cannot reach it
The quoting widget goes on your website. If it is not usable with a keyboard or a screen reader, the part of your site that takes orders is the part that excludes people - and that is our doing, not yours. This page says what we target, what we have actually tested, and what is still missing.
WCAG 2.2 level AA, for the widget, the console and this site
Keyboard, everywhere
Every control the widget offers can be reached and operated from a keyboard, with a visible focus ring that is not the browser's faint default. The 3D preview orbits with the arrow keys, zooms with + and − and resets with 0.
Colour is never the only cue
Manufacturability warnings carry an icon and a sentence, not a red dot. The wall-thickness heat map has a numeric legend and the measurements are listed as text beside it.
Targets you can hit
Every button, swatch and stepper is at least 24 × 24 px, including the ones a shop has restyled: the density token a shop can set is clamped so a theme cannot shrink a control below the floor.
Motion you can turn off
We honour prefers-reduced-motion. Spinners slow to a crawl rather than stopping dead, so "busy" is still legible without anything moving quickly.
No 3D, no dead end
Without WebGL the viewer gives way to the part’s dimensions in text, and the Inspect tab lists its measures. Nothing about getting a price depends on the 3D view.
It works small
The widget is usable from 320 px wide and at 200 % browser zoom.
Automatically on every change, and by hand before a release
- axe on every commit. The component kit the console is built from is rendered and audited automatically; a violation fails the build.
- A repository-wide markup check. Two rules that break quietly and often - a form control in a table cell with no name, an empty column header - are enforced across every screen we ship.
- Contrast is computed, not eyeballed. Every colour pair the design system claims is recomputed from the tokens on every build.
- Target size is computed too. The stylesheets are read and the arithmetic done, so a control cannot drop below 24 px unnoticed.
- A browser audit of the running product. Upload, configure, compare, checkout; and the merchant console's editors, which is where the dense tables are.
What is not done yet
- No screen-reader audit by a person who uses one daily. Our checks are automated, which is not the same thing and we are not going to pretend it is. An audit by a daily screen-reader user is required before general availability.
- No published conformance report. No VPAT or EN 301 549 statement yet.
- The widget speaks three languages. English, German and French. More are coming; a shop can also override any string in any language it offers.
- Right-to-left is built but lightly travelled. The layout is logical rather than left-and-right, but no right-to-left language ships yet and no native reader has used it in anger.
- The console is English only. Merchant-facing translation follows the widget's.
Something in your way?
Tell us what you were trying to do, what got in the way and what you are using. An accessibility report is a bug report and we treat it as one - no forms, no triage queue, no asking you to prove it.