Accessibility Statement

Effective May 28, 2026, WCAG 2.1 AA target

Honest version: we target WCAG 2.1 AA, mostly meet it, and openly list what we don't. Reachable accessibility contact: [email protected].

1. Conformance Target

We target Web Content Accessibility Guidelines (WCAG) 2.1 Level AA as our conformance benchmark. Last internal audit: May 2026 (see "Known Issues" below for what didn't pass).

2. What Works Well

  • Keyboard navigation, every interactive element is reachable with Tab; activate with Enter or Space; close overlays with Escape. Skip-to-main-content link is the first focusable element on every page.
  • Semantic HTML, headings are in order (H1 → H2 → H3, no skips), landmarks (<main>, <nav>, <footer>) are used throughout.
  • ARIA labels, sortable columns expose aria-sort; filter chips use aria-pressed; charts have sr-only textual fallbacks describing the data.
  • Color contrast, body text meets WCAG AA (4.5:1 minimum); large headings meet AA (3:1 minimum). Verified with automated tools across the dark palette.
  • Reduced motion, we honour prefers-reduced-motion: reduce by disabling animations.
  • Forms, every input has an associated <label htmlFor>; required fields are marked with aria-required; validation errors fire role="alert".
  • No keyboard traps, modal dialogs (compare modal, chatbot) return focus to the trigger on close.

3. Known Issues (Honest Report)

We don't hide gaps. As of May 28, 2026:
  • Light-mode is recent and still polishing. A toggle (sun/moon icon, top right) switches between dark and light. Preference persists across visits and respects prefers-color-scheme. Some component-level surfaces (a few borders, scattered translucent layers) still favour the dark palette; we are working through them.
  • Decorative video on Home (desktop only). The hero chip-animation video plays automatically on screens > 768px. It is muted, looping, and below the fold; it has aria-hidden and is disabled by prefers-reduced-motion.
  • Chart fallbacks are textual summaries, not full data tables. The bar / scatter / radar charts on the benchmark pages have a hidden sentence describing the top values. Full data is always available via the sortable HTML table beneath each chart.
  • Chatbot voice output not yet implemented. The chat widget is text-only; we don't do TTS or speech-to-text. Pasting and screen-reader read-back work fine for most users.

If any of these block you from using the Site, please write to us, we'll prioritize the fix.

4. Conformance Statement

MyAIHardware is partially conformant with WCAG 2.1 Level AA. "Partially conformant" means some parts of the content do not fully conform (see Known Issues above). We are actively working toward full conformance.

5. Assistive Technology Tested

We test with:
  • NVDA on Windows + Firefox (latest)
  • VoiceOver on macOS + Safari (latest)
  • Keyboard-only navigation on all major browsers
  • Browser zoom up to 200% without horizontal scroll

We do not currently test with JAWS, Dragon NaturallySpeaking, or iOS / Android screen readers on every release. If you use one of those and find an issue, the report goes to the front of the queue.

6. Feedback & Response Time

If you encounter an accessibility barrier, email [email protected] with subject line "Accessibility issue". Include:
  • The page URL where you hit the issue.
  • The assistive technology you were using (screen reader + browser + OS).
  • What you were trying to do and what went wrong.

Response target: 2 business days. Fix or workaround target: 14 days. For complex issues that need a longer fix, we will tell you that within the first 2 days and give you a target date.

7. Enforcement Procedures

If you are unsatisfied with our response, you can escalate to the accessibility regulator that has jurisdiction in your country, most jurisdictions have an equality or disability-rights body that accepts web-accessibility complaints.

Report a barrier

We respond within 2 business days. No issue is too small.

Email [email protected]

Or use the contact form.