Structure
WCAG is built on four principles – perceivable, operable, understandable, robust – with testable success criteria. Each criterion has a level: A (minimum), AA (the usual target) and AAA (enhanced) [1].
The criteria that matter most for 3D
| Criterion | Level | What it means for a configurator |
|---|---|---|
| 2.1.1 Keyboard | A | every function works from a keyboard [2] |
| 2.5.1 Pointer Gestures | A | zoom and the like also without multi-finger gestures [3] |
| 2.5.7 Dragging Movements | AA | rotate without dragging too, e.g. with view buttons [4] |
| 2.5.8 Target Size (Minimum) | AA | controls at least 24 × 24 CSS pixels or enough spacing [5] |
| 4.1.3 Status Messages | AA | check results and price changes announced to screen readers [6] |
| 2.3.3 Animation from Interactions | AAA | motion can be switched off, see reduced motion |
The basic pattern
A canvas with 3D graphics is, to a screen reader, just a surface. So: everything essential lives in the HTML – options as real form controls, check results as text, the summary as a table. The 3D model adds to it; it is never the only source.
WCAG and German law
Germany's Accessibility Strengthening Act (BFSG) applies, among other things, to e-commerce services provided to consumers after 28 June 2025 [7]. Whether and how it affects your configurator is a question for an accessibility specialist or legal adviser. This is general information, not legal advice.
Example from the library
In the sectional door example the fit-check result sits in an area screen readers can announce as a status message, and transitions are dropped under reduced motion. That is one slice, not a full WCAG audit. Example configurator, fictional product.