Accessibility

We design and build with accessibility as a requirement, not a retrofit: semantic HTML, visible focus states, labeled controls, and testing with assistive technology as part of development. Accessibility issues are triaged as bugs, not feature requests.

Every interactive element including the cookie banner and preference toggles is reachable and operable with a keyboard alone. Focus order follows the visual order, a visible gold focus ring marks the active element, and dialogs trap and return focus correctly.

Pages use landmarks, heading hierarchy, and ARIA only where native semantics fall short. Dynamic updates — like saving cookie preferences are announced through live regions. We test with VoiceOver and NVDA on current browsers.

Text and interactive elements meet WCAG 2.1 AA contrast ratios in both dark and light themes, and color is never the only carrier of meaning trends and states are also expressed in text and iconography.

Animations including the cookie banner entrance and smooth scrolling are disabled when your operating system sets prefers-reduced-motion. Nothing on the platform relies on motion to convey information.

Our target is WCAG 2.1 Level AA across the platform. We are working toward a formal conformance audit and will publish its results and any known exceptions here.

If any part of the platform is difficult to use with assistive technology, email accessibility@vibimine.example. Include the page and the technology you were using; we aim to respond within two business days and to fix verified barriers with priority.