Accessibility Statement

Individuate.me is partially compliant with WCAG 2.2 Level AA and EN 301 549 v3.2.1. The known non-conformances and their reasons are listed under “Known Limitations” below.

Individuate.me is committed to making our dream interpretation service accessible to everyone, including people with disabilities. We believe that exploring the meaning of your dreams should be an experience available to all, regardless of ability.

We aim to conform to the following accessibility standards:

• WCAG 2.2 Level AA — Web Content Accessibility Guidelines by the W3C, the internationally recognised baseline for web accessibility.
• EN 301 549 v3.2.1 (EU / Canada) — European standard for ICT accessibility, required under the European Accessibility Act (EAA), Web Accessibility Directive (WAD), and adopted by Canada as CAN/ASC-EN 301 549:2024 under the Accessible Canada Act (ACA).
• ADA Title III / Section 508 (US) — Americans with Disabilities Act and Section 508 of the Rehabilitation Act. WCAG 2.1 AA is the de facto technical standard.
• JIS X 8341-3:2016 (Japan) — Japanese Industrial Standard for web accessibility, aligned with WCAG 2.0 Level AA.

We have taken the following steps to make Individuate.me accessible:

• Semantic HTML — We use proper heading hierarchy, landmark regions, and meaningful document structure throughout the application.
• Keyboard navigation — All interactive elements are reachable and operable via keyboard, with visible focus indicators.
• Screen reader support — We use ARIA attributes, live regions, and descriptive labels to ensure content is announced clearly by assistive technologies.
• Colour contrast — Text and interactive elements meet WCAG AA contrast ratios against their backgrounds.
• Reduced motion — Animations respect the prefers-reduced-motion media query for users who are sensitive to motion.
• Skip navigation — A skip-to-content link is available on every page for keyboard users.
• High contrast support — The application respects prefers-contrast: more and forced-colors (Windows High Contrast Mode) for users who need enhanced contrast.
• Responsive design — The interface adapts to different screen sizes, zoom levels, and text scaling preferences.

While we strive for full conformance, the following areas have known non-conformances. For each limitation we list the reason and our remediation plan.

• AI chat streaming (WCAG 4.1.3) — Some dynamically streamed chat content may not announce perfectly with all screen readers. We use ARIA live regions to announce new messages, but the real-time streaming nature of AI responses may cause inconsistencies across different assistive technologies. Reason: Technical limitation of streaming LLM output. Remediation: Ongoing testing with NVDA, JAWS, and VoiceOver to improve announcement timing.
• Dark-mode only (EN 301 549 Clause 11.7) — The application currently provides a dark colour scheme only and does not automatically switch to a light theme based on prefers-color-scheme. We do support prefers-contrast: more (enhanced contrast) and forced-colors (Windows High Contrast Mode). Reason: Design decision; a light theme has not yet been implemented. Remediation: A light-mode theme toggle is planned.
• Third-party components — Some UI components from third-party libraries may have accessibility gaps that we are working to address. Reason: Upstream library limitations. Remediation: We contribute fixes upstream and apply local overrides where possible.

We are actively working to resolve these limitations and welcome reports of any specific issues you encounter.

We take accessibility feedback seriously. If you encounter any barriers when using Individuate.me, or if you have suggestions for improvement, please contact us:

• Email: [email protected]
• Postal address: DoYourAI, Nicosia, Cyprus

When reporting an issue, it helps if you can include which page or feature you were using, what assistive technology you use (if any), and a description of the barrier you experienced.

We aim to respond to all accessibility feedback within 30 business days and will work to resolve reported barriers as promptly as possible.

This statement was prepared based on a self-assessment using automated scanning tools (eslint-plugin-jsx-a11y, axe-core rules) combined with manual structural code review against all 55 WCAG 2.2 Level AA success criteria. The evaluation also covered EN 301 549 v3.2.1 beyond-WCAG requirements.

Accessibility is an ongoing effort, not a one-time task. We review and audit this statement and our application against WCAG guidelines at least once per year. We incorporate accessibility considerations into our development process for all new features and updates.

If you are not satisfied with our response to your accessibility feedback, you may contact the relevant enforcement body in your jurisdiction:

• EU — Contact your national enforcement body under the Web Accessibility Directive. A list is maintained by the European Commission (opens in new tab).
• US — File a complaint with the U.S. Department of Justice (opens in new tab).
• Canada — File a complaint with the Accessibility Commissioner of Canada (opens in new tab).
• Japan — Contact the Digital Agency (opens in new tab) for guidance on JIS X 8341-3 conformance.