Accessibility Statement

1. Our commitment

Veltrix builds software for a living, so we hold our own website to the standard we would want applied to anything we ship. Accessibility is treated as part of the build, not a pass at the end. That said, this is an honest statement rather than a marketing one, the gaps in section 4 are real and we have not hidden them.

2. Conformance status

We aim to meet WCAG 2.1 Level AA. Our current status is partially conformant, which means most of the standard is met but some parts have not been fully verified.

We have tested this site ourselves, keyboard navigation, colour contrast measured programmatically against the actual rendered backgrounds, screen-reader landmarks, and layout from 390px up to large desktop widths. We have not commissioned an independent third-party audit, and we have not tested with every combination of assistive technology. We would rather say that plainly than claim conformance we cannot evidence.

3. What we have done

• Skip link. A "Skip to content" link is the first focusable element on every page, so keyboard and screen-reader users can jump past the navigation.
• Landmarks and headings. Every page uses real header, nav, main and footer landmarks, with a single h1 and a heading order that does not skip levels.
• Colour contrast. Body text is measured against its actual rendered background, including gradients, rather than eyeballed, and targets the 4.5:1 ratio AA requires (3:1 for large text).
• Keyboard access. Every interactive element is reachable and operable by keyboard, with a visible focus indicator. The mobile menu reports its state with aria-expanded, and the current page is marked with aria-current.
• Images. All content images carry alt text; decorative graphics and icons are hidden from assistive technology with aria-hidden so they are not announced as noise.
• Forms. Every field in the contact form has a real associated label. Validation errors are tied to their field with aria-describedby and marked aria-invalid, so an error is announced rather than only shown in red. Errors clear as soon as you correct the field.
• Works without JavaScript. Every page, including the contact form, has a server-rendered fallback that functions with JavaScript disabled or blocked.
• Language. Every page declares lang="en".
• No horizontal scrolling. Verified at 390px and 500px; wide tables scroll inside their own container rather than forcing the whole page sideways.

4. Known gaps

These are the things we know are not right yet. We are working on them.

• No independent audit. All testing so far has been our own. An external review would likely surface issues we are too close to the work to see.
• Screen-reader coverage is partial. We have tested with a limited set of assistive technology, not the full matrix of screen readers, browsers and operating systems.
• Animation-heavy sections. The homepage uses scroll-driven frame sequences. These respect reduced-motion preferences (section 5), but the underlying content is visual and its full meaning may not carry to a screen reader.
• Decorative video has no captions. The background video carries no speech or information, so no captions are provided. Any future video with meaningful audio will be captioned.
• Third-party pages. Booking a call hands you to Calendly, whose accessibility we do not control.

5. Motion and animation

This site uses scroll-triggered reveals and animated sequences. If you have set "reduce motion" in your operating system, the site honours it: animations are disabled or reduced to a simple fade, and content appears in place rather than moving. Nothing is hidden behind an animation, if motion is off, you still get all the content.

You can turn this on in:

• Windows: Settings › Accessibility › Visual effects › Animation effects
• macOS / iOS: Settings › Accessibility › Display › Reduce motion
• Android: Settings › Accessibility › Remove animations

6. Technology it relies on

Accessibility here relies on HTML, CSS, JavaScript and WAI-ARIA. JavaScript improves the experience but is not required, the site is built so that every page still works, and the contact form still submits, with scripting unavailable.

7. Tell us about a problem