Accessibility Statement

This statement describes the accessibility measures actually built into zerovyn.com, the gaps Zerovyn is aware of, and the channel to use when something does not work for you.

What has been done

• Semantic structure. Pages use proper heading order, landmark regions and a single h1 per page, so navigation by structure works.
• Skip link. A "skip to main content" link is present and is the first focusable element on the page.
• Keyboard operability. Every interactive element — navigation toggle, chat assistant, form controls — is reachable and operable by keyboard alone. Focus is left visible rather than suppressed.
• Labels on form fields. Every input has an associated label. Required and optional fields are stated rather than implied by colour.
• Text scaling. Layout uses relative units and viewport-based sizing, so text scales without breaking the page. Horizontal overflow is clamped, so zooming in does not push content off-screen.
• Reduced-motion support. Every animation respects the prefers-reduced-motion preference. Where motion is disabled, the resting state of the content is fully visible — nothing is hidden behind an animation that never runs.
• Decoration marked as such. Ornamental SVG and background layers carry aria-hidden so they are not announced.
• Colour contrast. Body text and controls were chosen against the dark surface for contrast. The palette is dark by design.
• HTML validity. Tag balance and structure are checked in the build pipeline, so malformed markup does not quietly degrade the tree.

Known gaps

The following are known and have not been resolved:

• The site has not been audited against WCAG 2.2 by an independent assessor. Conformance is therefore asserted at the level of implemented practice, not at a named conformance level.
• The interactive chat assistant is operable by keyboard, but its message log is not a fully compliant live region for all screen readers.
• Some motion-heavy sections depend on JavaScript being available. Without it the content is present and readable, but the staged reveal does not occur.

These are engineering gaps, not acceptable end states. They are prioritised by the number of people they affect.

Reporting a problem

If part of this site is not usable for you, that is a defect and it is wanted. Describe what you were trying to do, which page you were on, and the technology you were using. Send it to accessibility@zerovyn.com. Every report is read by a person, replied to, and treated as a bug.