Accessibility Statement
The standard this site is built to, what has and has not been tested, the parts we know fall short, and how to tell us you hit one.
Contents · 4 sections
Plain-language overview. We build to WCAG 2.2 AA and we have not been audited, so this page tells you what is actually in place and what we know is missing rather than claiming a level. The CAD studios are the real gap and they are staff-only. Hit a barrier and one email gets it looked at, and if the barrier is stopping you sending us work, we will open the inquiry from our side.
Summary only. The numbered sections below are the document.
The standard we build to
We build to the Web Content Accessibility Guidelines, version 2.2, at level AA. That is the target the work aims at.
Nobody independent has tested this site. There is no audit report, no VPAT and no accessibility conformance report, so we do not say the site conforms. What follows is what has been built and what we know is missing, which is a smaller claim and one we can stand behind.
What is in place
Each of these is in the code today rather than on a roadmap:
| Measure | What it does |
|---|---|
| Skip to content | The first thing keyboard focus reaches on every page jumps past the navigation. |
| Reduced motion | A browser or system set to reduce motion switches off the page transitions, the pop animations and the live indicators. |
| Visible focus | Focus styling is drawn separately from hover, so tabbing through a page shows where you are. |
| Semantic structure | Headings run in order, the page language is declared, and navigation, main content and footer are marked as what they are. |
| Text alternatives | Every photograph carries alt text written for it, held in one registry that a check refuses to let a page skip. |
| Labels and state | Form fields have real labels, and controls that expand, select or disable report that to assistive technology rather than showing it only in colour. |
| Text, not pictures of text | Nothing on the site renders a sentence as an image, so text scales and reflows with your own settings. |
Where the site falls short
Known, not guessed. If you hit one of these, the cause is us:
- The CAD studios are not keyboard operable. They draw to a canvas and are driven by pointer gestures: dragging geometry, orbiting a model, picking a face. There is no keyboard path through that today. They sit behind a staff check, so no client meets them, and the way a client is shown a model is a read-only link to a view rather than the studio itself.
- Some data tables scroll sideways on a narrow screen. A table with more columns than a phone can hold scrolls inside its own frame. The content is all reachable, and getting to a cell on the right takes more work than it should.
- Nothing has been tested with a screen reader end to end. Individual controls carry the right roles and labels. A full pass through a real journey, from landing on the site to sending an inquiry, has not been done with a real reader by a real user.
- Contrast has not been measured against every state. The palette was designed for it and the ordinary cases hold. Disabled controls and faint helper text against a tinted panel are the places we have not checked with a meter.
Tell us you hit one
Write to support@spaltx.com with ACCESSIBILITY in the subject line. Say what page you were on, what you were trying to do, and what you use to browse. We answer within five business days and tell you whether it is fixable quickly or going on the list.
If a barrier here is stopping you from sending us a project inquiry, say that in the message and describe the work instead. We will take it from your email and open the inquiry from our side, so a defect of ours does not cost you the job.
The contact form reaches the same desk. Either is fine.