Event work should be usable by people—not only devices.
Galaxy Cue is working toward an accessible public site and accessible core Business and Client workflows.
Accessibility target
Galaxy Cue uses WCAG 2.2 Level AA as its technical target for perceivable, operable, understandable, and robust experiences. Applicable disability-access laws may impose additional obligations depending on the operator, Business, location, and service.
Current design practices
- Keyboard focus indicators, skip links, labels, landmarks, and semantic controls.
- Responsive layouts for mobile zoom and narrow screens.
- Reduced-motion support and non-color text labels for important workflow state.
- Readable contrast targets, minimum touch targets, and form error/status announcements.
- Downloadable/reproducible Event documents where the workflow supports them.
Testing and remediation
Release verification should include keyboard-only navigation, screen-reader smoke testing, zoom at 200%, mobile reflow, form labels/errors, focus order, modal focus/escape, color contrast, reduced motion, and document preview/download access. High-impact booking, sign-in, contract, payment, and cancellation barriers take priority.
Third-party content
Hosted payment pages, app stores, social networks, email clients, and embedded external content are controlled by their providers. Galaxy Cue will choose accessible providers where reasonably possible and offer an alternative path when a critical third-party flow creates a known barrier.
Request assistance
A person who cannot complete a Galaxy Cue workflow should use the applicable Business contact or verified support channel and describe the page, task, device/browser, assistive technology, and preferred response method. Do not include a password, one-time code, payment credentials, or API secret.