Accessibility statement

Wamid is built so that anyone — including people who rely on assistive technology — can capture an idea, get it back when it matters, and trust the experience. This page declares where we stand against the standards we measure ourselves against, and how to tell us when we fall short.

Our commitment

We aim to meet WCAG 2.1 Level AA on the website wamid.app and the Wamid Android application. Where we can, we go beyond AA toward AAA (color contrast on text, motion control, plain language). We treat accessibility as a product quality, not a compliance checkbox.

Standards we follow

• WCAG 2.1 Level AA — Web Content Accessibility Guidelines, World Wide Web Consortium.
• EN 301 549 v3.2.1 — European harmonised standard, alignment with the European Accessibility Act (EAA) applicable from June 2025.
• Section 508 Refreshed (United States) for the web components.
• Android accessibility best practices — TalkBack, Switch Access, Voice Access, dynamic font sizing, contrast, target size 48dp minimum.

Conformance status

This site partially conforms with WCAG 2.1 Level AA. "Partially conforms" means most content meets the standard, but some parts do not yet. The known limitations are listed below in good faith.

This declaration is a self-assessment performed internally on May 19, 2026. An independent third-party audit is planned before the Wamid V1.0 public launch.

What works well

• Keyboard navigation: every interactive element (links, buttons, language switcher, form fields) is reachable with Tab / Shift+Tab, and visible focus is preserved on all interactive elements via :focus-visible.
• Skip link: a "Skip to main content" link is the first focusable element on every page (WCAG 2.4.1 Level A).
• Screen readers: headings follow a logical h1 → h2 → h3 order. Decorative SVGs are marked aria-hidden="true". Status messages use aria-live="polite" (waitlist counter, welcome-back banner).
• Color contrast: body text contrast on #FBF9F6 background exceeds 7:1 (AAA). CTA contrast on Cradle #264653 exceeds 12:1.
• Reduced motion: all animations (Hero choreography, Idea Point breathing, Memory Cradle pulse, scroll-driven effects) collapse to a static frame when the operating system requests prefers-reduced-motion: reduce.
• Forced colors / Windows High Contrast Mode: CTAs, radio cards and focus rings remap to system colors (CanvasText, Highlight) when forced-colors: active is detected.
• Reduced transparency: shadows compensate opacity when prefers-reduced-transparency: reduce is set so that elevation remains perceivable.
• Right-to-left: the layout uses CSS logical properties (padding-inline-start, margin-inline-end, border-inline-start) and Arabic line-height tokens prepared for an Arabic locale.
• Mobile target size: all CTAs and tap targets are at least 48 × 48 CSS pixels (WCAG 2.5.5 AAA).

Known limitations

We list these honestly so you can make an informed choice and so we can be held accountable.

• SVG titles: some inline SVG icons in the Hero and Footer rely on aria-hidden="true" because they are decorative companions to a visible text label. SVGs that carry semantic meaning standalone will be enriched with <title> elements in the next release.
• Arabic locale: the website is currently published in English and French. Arabic and Spanish layouts exist in the i18n backbone but are not yet published. RTL screen-reader testing is therefore not yet complete.
• Memory Cradle illustration: the breathing cradle SVG on Hero has no narrative <title> yet. Screen readers currently skip it (it is marked decorative). A short description is planned to expose the brand metaphor on request.
• Cookieless analytics: the welcome-back banner is announced as a polite live region; we are still validating the exact wording across VoiceOver, NVDA and TalkBack.
• Independent audit: no formal third-party VPAT is published yet. It will be commissioned before V1.0 launch.

Assistive technology we test against

• VoiceOver on macOS (Safari) and iOS (Safari).
• NVDA 2024.x on Windows (Firefox, Edge).
• TalkBack on Android 13+ (Chrome).
• Keyboard-only navigation (Tab, Shift+Tab, Enter, Space, Escape, arrow keys).
• Browser zoom up to 400% without horizontal scroll on a 1280-px viewport.
• Forced colors mode on Windows 11.
• prefers-reduced-motion and prefers-reduced-transparency system settings.

How to report a barrier

If you encounter a page or a feature that blocks you, please tell us — your report is the fastest path to a fix. Include the URL, what you were trying to do, the assistive technology and browser you use, and what happened.

• Email: accessibility@wamid.app (preferred channel for accessibility issues).
• Fallback: contact@wamid.app if the dedicated mailbox is unavailable.

We aim to acknowledge accessibility reports within 5 working days and to ship a fix or a workaround within 30 days for blocking issues (WCAG Level A or AA failures).

Enforcement and escalation

If you live in the European Union and our response does not satisfy you, you can escalate to your national accessibility authority. For France this is the Défenseur des droits. For other EU member states, see the European Commission disability portal.

Review schedule

This statement is reviewed at least every six months and after every major release. Last review: May 19, 2026. Next scheduled review: November 2026.

Contact

Any question, suggestion or report on accessibility: accessibility@wamid.app.