Accessibility Statement

Our Commitment

Mentra Labs is committed to ensuring that mentraglass.com is accessible to everyone, including people who use assistive technologies such as screen readers, keyboard navigation, and voice control. We are actively working to meet the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA (opens in new tab).

Current Status

We have completed five remediation sprints following a comprehensive adversarial accessibility audit. The most recent sprint (March 25, 2026) resolved 43 issues across 31 files, with particular focus on the critical purchase path, screen reader announcements, motion safety, and color contrast. The site now substantially conforms to WCAG 2.1 Level AA, with known gaps documented below.

Conformance Scorecard

Summary of WCAG 2.1 AA conformance status by accessibility dimension:

What We've Fixed

The following accessibility improvements have been verified in code across five remediation sprints:

• Purchase path fully accessible — screen reader users receive live announcements for add-to-cart, order processing, errors, and cart item removal
• Product title visible to all assistive technology on all viewports (aria-hidden removed from desktop product heading)
• Address form has visible <label> elements on all 10 inputs (replacing placeholder-only pattern)
• Skip-to-content link in the Header component targeting #main-content
• All custom pages wrapped in <main> landmarks via ContentShell — single id="main-content" with no duplicates
• Focus-visible rings on all interactive elements (buttons, links, inputs) with Windows High Contrast Mode support (outline: 2px solid transparent pattern)
• Reduced-motion support via dual-layer system (CSS media query + JS preference hook) covering hero videos, SmartVideo, carousels, canvas animations, stagger effects, and marquees
• Visible pause/play button on product image carousel and all auto-advancing content
• ARIA patterns on accordions, tabs (with arrow-key navigation and roving tabIndex), menus, and dialogs
• Modal, popup, and mobile menu overlays apply inert to background content — SortFilter panel uses inert when hidden
• Compare page FAQ tabs support ArrowLeft/ArrowRight/Home/End keyboard navigation
• Minimum 44×44px touch targets on all interactive elements
• autocomplete attributes on form fields (name, email, address, phone, etc.)
• aria-required on required form inputs with visible labels
• Contact and careers forms have per-field error messages, error summaries with anchor links, and success announcements via role="status" + aria-live
• Dark mode --ink-tertiary contrast fixed (#8f8f8f → #999999, ~4.7:1 on dark surface)
• Livestream text-white/40 and text-white/45 raised to text-white/70 (~8.7:1 contrast)
• Inline paragraph links underlined by default (not relying on color alone — WCAG 1.4.1)
• Error inputs use border-width: 2px for non-color error indication
• Placeholder focus opacity raised from 0.5 to 0.7 for better contrast
• Brand green color contrast fixed site-wide — AA-compliant --brand-text token deployed to all text usages
• Comparison feature rows on /compare page have ARIA table roles (role="table", role="row", role="rowheader", role="cell")
• Homepage specifications converted to semantic <dl>/<dt>/<dd>
• Cart Total rendered as semantic <dl>/<dt>/<dd>; cart lists use role="list" for Safari VoiceOver
• Sale price / original price distinction announced via sr-only labels in ProductCard
• Color swatch in cart has role="img" so aria-label is respected
• Blog content processor preserves existing alt attributes, adds iframe title fallback, uses empty alt for auto-detected decorative images
• ProductGallery fallback alt text uses indexed pattern ("Product photo 1", "Product photo 2") instead of generic "Product image"
• 30+ external links disclose "(opens in new tab)" via aria-label or sr-only text
• FAQ accordion panels remain in DOM with hidden attribute so aria-controls always references a valid element
• ChargingImageCarousel aria-live removed to prevent noisy auto-rotation announcements
• Duplicate investor marquee logo sets marked aria-hidden="true"
• Footer uses native <footer> role (removed redundant role="contentinfo")
• PageLayout <nav> has aria-label="Main navigation"
• SortFilter dropdown uses as="div" (not as="nav" — a sort menu is not a navigation landmark)
• SortFilter heading levels corrected (h4 → h3)
• Blog <aside> has aria-label="Related content"
• Modal fallback dialog label improved from "Modal" to "Dialog content"
• Video thumbnail buttons have descriptive aria-labels ("Play video 1", etc.)
• Phantom empty-src <track> removed from gallery lightbox (replaced with TODO comment)
• 404 page canvas, Hero3DCanvas, TVCanvas, StaggeredHeadline, YourDataSection, and newhome manifesto all draw single static frame or reveal instantly under reduced motion
• Automated WCAG 2.1 AA testing in CI with @axe-core/playwright
• ESLint accessibility rules enforced as blocking errors
• Windows High Contrast Mode and prefers-contrast: more support in global CSS

Known Limitations

We are aware of the following accessibility gaps and are actively working to resolve each one. We document these honestly — transparency about known issues is part of our commitment to accessibility.

This page is updated as fixes ship.

How to Report an Accessibility Issue

If you experience a barrier on our site that prevents you from accessing content or completing a task, we want to hear about it. We respond to all accessibility reports within 5 business days.

Please include:

• The URL of the page where you encountered the issue
• The assistive technology you are using (if any)
• A description of the barrier you experienced

Technical Approach

Our development process includes:

• Skip-to-content link in the Header component targeting #main-content
• All custom pages wrapped in <main> landmarks via the ContentShell component with a single unique id="main-content"
• Focus-visible rings on all interactive elements using the outline: 2px solid transparent pattern for Windows High Contrast Mode compatibility
• Reduced-motion support via a dual-layer system: CSS prefers-reduced-motion media query plus a JavaScript usePrefersReducedMotion() hook that detects Brave Browser spoofing
• WAI-ARIA Authoring Practices patterns on accordions, tabs (with arrow-key navigation and roving tabIndex), menus, and dialogs
• inert attribute on background content when modals, popups, and filter panels are open
• Minimum 44×44 px touch targets on all interactive elements
• autocomplete attributes on form fields (name, email, address, phone)
• aria-live regions for dynamic content: cart status, order processing, form submission, and search results
• Semantic HTML: <dl> for specifications and cart totals, ARIA table roles for comparison data, role="list" on styled lists for Safari/VoiceOver
• Automated WCAG scanning integrated into our deployment pipeline via @axe-core/playwright
• Manual accessibility review each quarter against WCAG 2.1 Level AA
• Accessibility checklist as part of our definition of done for new frontend features
• Third-party component review for accessibility compliance before adoption

Compliance Framework

Our accessibility programme is governed by an internal compliance protocol maintained by our Operations Manager. Key elements include:

• Quarterly manual audits against WCAG 2.1 Level AA, covering keyboard navigation, screen reader compatibility, focus management, and video caption accuracy
• Adversarial "plaintiff's attorney" audit methodology — testing from the perspective of ADA Title III litigation to identify and preemptively close legal attack surfaces
• Automated WCAG scanning integrated into our CI/CD pipeline — accessibility regressions block deployment
• An accessibility checklist that must be completed before any new frontend feature ships
• Mandatory third-party component review: vendors must provide a VPAT (Voluntary Product Accessibility Template) before adoption
• A maintained internal audit log tracking every known violation, its severity, owner, and resolution status
• Defined ownership: Operations Manager owns the protocol and audit log, frontend developers execute fixes, content team produces captions and alt text
• Planned evaluation of WCAG 2.2 Level AA requirements in Q4 2026

Standards We Reference

• Web Content Accessibility Guidelines (WCAG) 2.1 Level AA (opens in new tab) — W3C
• WAI-ARIA Authoring Practices Guide (opens in new tab) — W3C
• Section 508 of the Rehabilitation Act (where applicable)
• Americans with Disabilities Act (ADA) Title III
• European Accessibility Act (EAA) — monitored as Mentra expands internationally

Vendor Accessibility

We review third-party components for accessibility before adopting them on our site. Current vendor status:

If you encounter an accessibility barrier caused by a third-party component on our site, please report it to us and we will work with the vendor to resolve it.

Audit History

This statement was last updated on March 25, 2026 following the fifth remediation sprint (adversarial ADA audit — 43 fixes across 31 files). It is updated whenever material accessibility changes are made to the site. Known gaps are documented honestly above — we do not claim full WCAG 2.1 AA conformance until all Level A and AA criteria are verified, including production video captions. Our remaining issues are primarily content-dependent (video transcription), low-severity cleanup items (SVG aria-hidden, remaining new-tab disclosures), and a handful of secondary motion instances. Zero critical purchase-path barriers remain.