Accessibility statement
The important professional and product evidence should remain usable without perfect vision, motion, input, or graphics conditions.
Last reviewed 16 July 2026. Accessibility is treated as an operating constraint and release concern, not a decorative compliance badge.
Behaviours included in the release review
- Visible keyboard focus on primary links, buttons, form controls, product-lab tabs, and case-study actions
- Skip-to-content support and semantic page landmarks
- Responsive layouts at narrow mobile, tablet, and desktop widths
- Reduced-motion handling for site transitions and the interactive systems lab
- Readable fallback content when WebGL, JavaScript modules, or external graphics support are unavailable
- Labels, instructions, status messages, and privacy warnings on the enquiry forms
- Text alternatives and explicit captions for portfolio workflow diagrams
Keyboard
Primary navigation, forms, tabs, case links, theme control, and mobile menu actions are keyboard reachable.
Responsive reading
Content reflows for mobile and zoomed layouts without making the evidence dependent on a wide canvas.
Non-visual fallback
Visual maps have alt text and captions; the interactive lab always links back to standard HTML case studies.
Known boundaries
These are stated explicitly so an accessibility goal is not presented as independent certification.
- The site is designed toward WCAG 2.2 AA rather than claiming independent certification.
- Third-party checkout, scheduling, GitHub, and form-delivery surfaces have their own accessibility implementations.
- The Three.js lab is progressive enhancement; all factual case-study content remains available without it.
- PDF and EPUB accessibility is validated structurally, but assistive-technology behaviour may vary by reader application.
Report a barrier