Accessibility

The Quantrix website is engineered with an emphasis on clarity, high contrast, and structural integrity. Rather than relying on generic third-party compliance overlays, we implement accessibility natively within the component architecture, focusing on semantic markup, keyboard navigability, and responsive behaviors.

This statement outlines the actual technical capabilities and known limitations currently present in the repository, rather than making fabricated claims of automated certification.

The current implementation incorporates several core accessibility patterns:

• Strict semantic HTML5 landmarks (main, header, nav, section, footer, article).
• CSS-driven dark mode presenting high-contrast monochrome design (WCAG contrast-ratio conscious).
• Explicit aria-label, aria-labelledby, and aria-hidden attributes injected into complex architectural interfaces.
• Responsive layouts built on fluid typography scales that respond to user viewport and browser zoom levels.
• Graceful degradation for users expressing motion sensitivities.

We construct our navigation systems to support keyboard-only interactions.

• Skip Links: A dedicated "Skip to main content" mechanism is deployed at the root layout boundary to enable keyboard users to bypass top navigation.
• Search Overlay: Can be triggered via standard global hotkeys (Cmd+K or Ctrl+K), fully operable by keyboard (Arrow keys, Enter, Escape).
• Interactive States: Navigation menus, dynamic routing toggles, and modal interfaces utilize tabIndex for sequential focus routing and aria-pressed to expose active states.
• Focus Management: Standard browser focus indicators are preserved to aid keyboard navigation.

Content throughout the site adheres to strict hierarchical heading structures (H1 descending linearly to H6). We do not use headings for purely decorative visual styling.

Information architecture is decoupled from DOM flow where necessary, allowing screen readers to traverse technical content, research notes, and architectural grids linearly and logically.

Quantrix utilizes hardware-accelerated animations (GSAP and CSS) to communicate systemic relationships and transitions.

Reduced Motion Fallbacks: Core animated components (such as WorkScroll, ResearchScroll, and MethodScroll) actively listen for the (prefers-reduced-motion: reduce) media query. When detected, these systems override dynamic scrub animations in favor of static, immediate-state renderings to prevent vestibular discomfort.

The primary communication vector (the Contact system) implements robust accessible form patterns.

• Explicit <label htmlFor="..."> attributes bind text descriptors to their respective input fields.
• Stateful client-side validation correctly utilizes the aria-invalid attribute to communicate error states.
• Inputs are fully operable and submittable via standard keyboard events (Enter key).

As a technical studio, complex systems are often illustrated via SVG geometries.

Informational SVGs inject contextual aria-label strings describing the architecture being depicted. Purely decorative visual signatures, such as the footer wordmark or background grid coordinates, utilize aria-hidden="true" to remove noise from assistive technology readouts.

We acknowledge the following known limitations based on our ongoing technical audits:

• Complex Data Visualizations: Certain highly dynamic node-graphs or experimental vector diagrams may not expose a completely equivalent text-based data table.
• Custom Select UI: Native form elements are overridden for brand aesthetic in specific dropdowns; ARIA audits for these specific custom controls are pending final engineering review.

We do not currently maintain a dedicated standalone accessibility reporting email alias.

If you encounter a barrier while using the Quantrix website, or if you need assistance accessing technical research or product documentation, please utilize the primary intake system to initiate a conversation with our engineers.

Accessibility is treated as a continuous engineering constraint, not a one-time audit checklist. This statement is updated as our codebase evolves, components are refactored, and new rendering capabilities are introduced.