Accessibility

Make ZoneGaze pages usable by everyone.

ZoneGaze aims to make its public website and documentation usable for keyboard, screen-reader, low-vision, and reduced-motion visitors.

This page describes practical commitments and feedback routes. It is not a certification claim or a promise that every issue has already been found.

Contact about accessibility

Usability

Clear, usable pages help everyone.

Keyboard and screen-reader support

Public pages use semantic headings, native links and form controls, visible focus states, and keyboard-reachable navigation patterns where possible.

Forms and errors

Waitlist and contact forms use labels, required-field semantics, standard browser validation, and clear sensitive-data warnings.

Responsive reading

Launch, documentation, support, and legal pages are designed to reflow cleanly on common mobile and desktop widths.

Reduced motion

Core reading and form workflows do not depend on motion. Product videos support the story without becoming the only way to understand it.

Media and documentation

Screenshots, concept visuals, demos, Flow media captions, and documentation should include useful captions, alt text, or surrounding text when they communicate product state.

Downloads and artifact verification

Download cards expose product, Mac type, version, size, SHA-256, signing, and status text so Matrix artifacts can be understood without relying on color alone.

Testing scope

Checks focus on the tasks visitors actually need.

Keyboard navigation

Check visible focus, tab order, links, buttons, forms, and skip paths on public pages.

Screen reader review

Review semantic headings, labels, link text, form instructions, and page landmarks.

Responsive layout

Check that pages reflow without horizontal scrolling on common mobile and desktop widths.

Media alternatives

Check captions, labels, alt text, surrounding copy, and non-video paths for product understanding.

Download workflow

Check Matrix for Mac download cards, hash text, signing notes, and file actions without relying only on visual status color.

Report issues

Help us improve access.

Reports are most useful when they include the page URL, the task you were trying to complete, browser or device context, assistive technology if relevant, and whether the issue blocks reading, navigation, forms, media, or documentation.

Accessibility feedback

Include the page URL, browser, device, assistive technology if relevant, expected result, and what blocked the workflow.

Open contact

General contact

Use contact routing for accessibility, partnership, press, privacy, legal, security, and product questions. Do not send sensitive details; ask for a safe follow-up channel if needed.

Open contact