Accessibility

Measured, not claimed.

This page says how accessible VASE 3D actually is. The figures below are read straight out of the test run, so they change when the product changes and they cannot say more than was measured. Anything that is not accessible yet is named here rather than left for you to discover.

What the measurement says

Status: conformant with WCAG 2.2 AA on every page and viewport measured below. This is a self-assessment, not a third-party audit.

Standard we hold: WCAG 2.2 AA. The contrast gate additionally records WCAG 2.2 AA / EN 301 549 / IS 5568.
How it was measured: axe-core 4.13.0, run over the built bundles this product actually serves, at desktop-1440x900 and reflow-320x800.
Pages and viewports checked: 126, with 0 violations and 0 that failed to load.
Text contrast: 845 colour pairs sampled from the painted page, 0 failing, 1 that could not be measured.
Touch targets: 0 below the 44 px floor on a touch pointer. A further 55 are links written inside a sentence, which WCAG 2.2 exempts by name and which are listed one by one rather than waved through as a class.
Assessed: 2026-09-06

What we hold, and how it is checked

The target is WCAG 2.2 level AA. That is the standard EN 301 549 carries for the European Accessibility Act, the one Israel's IS 5568 is built on, and the one a UK or US claim is normally argued against. Holding one target rather than three keeps the answer the same in every market.

Every page is run through axe-core, the same rules engine an outside audit would use, over the built bundles this product actually serves rather than over the sources they came from. It runs at a desktop width and again at 320 px, which is the reflow width WCAG asks about. Text contrast is sampled from the painted page rather than modelled from the stylesheet, because a colour written in CSS is not always the colour that lands on screen.

Alongside that:

Keyboard. Every page opens with a skip link. In the studio the 3D viewport itself is focusable, and the arrow keys, +, − and Home orbit, zoom and reset the same camera the mouse drives, clamped so a keyboard user cannot end up looking at the vessel upside down.
Touch targets. Controls hold 44 px on a finger, which is above the 24 px WCAG 2.2 asks for and matches Apple's guidance for the app shell. The rule is keyed on the pointer rather than the window width, so a tablet gets the touch layout even though it is not a narrow screen.
Motion. If your system asks for reduced motion, the studio and the site both honour it: transitions stop, and the moving backdrop stops with them.
Reflow. No page scrolls sideways at 320 px. Wide things like tables, diagrams and code scroll inside their own box instead of pushing the page.

What is not accessible yet

VASE 3D is a tool for shaping a three-dimensional object by hand, and some of that resists a text description. These are the limits we know about:

The vessel itself has no text alternative. A screen reader can reach every control that shapes the form, but it cannot describe the form. If you cannot see the preview, the numbers are the only account of what you have made.
Dragging on the model is a pointer gesture. The handles that sit on the vessel are pointer-first. Every value they change is also a numbered control in the panel beside them, so the same shape is reachable without the drag — but it is a different, slower route, and we are not going to pretend otherwise.
The live preview is a WebGL canvas. It needs hardware that can run it, and on a device that cannot it falls back to a still image rather than to nothing.
No third-party audit has been done. Everything above is our own testing. An outside audit finds what a self-assessment is structurally bad at finding, and we have not commissioned one yet.

Tell us when we get it wrong

If something here stopped you, write to afekhershko@vase3d.io. It reaches a person, not a queue. Tell us the page, what you were using (screen reader, keyboard, magnifier, voice), and what happened, and we will answer you and say what we are going to do about it.

If our answer does not satisfy you, you can escalate. In the EU, each member state names an authority for the European Accessibility Act; in the UK, the Equality Advisory and Support Service; in Israel, the Commission for Equal Rights of Persons with Disabilities. We would rather fix it first.