Lioma

Back to home

Accessibility Statement

Last updated: March 2026

Our Commitment to Accessibility

Lioma is committed to ensuring digital accessibility for people with disabilities. We continually improve the user experience for everyone and apply the relevant accessibility standards.

We strive to conform to the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA standards, as required by the Americans with Disabilities Act (ADA) in the US and the European Accessibility Act (EAA) in the EU.

Accessibility Audit Results

We conducted a comprehensive WCAG 2.1 Level AA audit of our application in March 2026, evaluating all 50 success criteria at Levels A and AA.

Overall Compliance: 90%+ WCAG 2.1 AA

Of 50 applicable WCAG 2.1 AA criteria, 47 fully pass and the remaining criteria are partially met with ongoing improvements.

What's Working Well

  • Form Accessibility: All forms use proper labels, inline error messages linked via aria-describedby, and aria-invalid states for validation feedback
  • Keyboard Navigation: All interactive elements are native buttons and links, fully operable via keyboard with no keyboard traps
  • Focus Visibility: All interactive elements show visible focus rings using the focus-visible CSS pattern, hidden for mouse users
  • Skip Links: Skip-to-main-content link available for keyboard users (WCAG 2.4.1)
  • Touch Targets: All buttons and interactive elements meet the 44x44px minimum size
  • Motion Preferences: All animations are wrapped in prefers-reduced-motion media queries
  • Dialog Accessibility: Modal dialogs use role="dialog", aria-modal, keyboard Escape to close, and proper focus management
  • Screen Reader Support: Comprehensive use of ARIA labels, live regions (aria-live), semantic HTML landmarks, and visually-hidden text
  • Live Regions: Toast notifications, conversation transcripts, recording state changes, loading states, and offline indicators all announce updates to screen readers
  • Semantic Structure: Navigation landmarks with aria-label, article elements for reflection entries, speaker identification on conversation messages
  • Mobile Accessibility: Safe area support for notched devices, native keyboard experience, optimized input modes per field type
  • Dynamic Language: HTML lang attribute automatically updates when the user switches language (WCAG 3.1.1)
  • Icon Buttons: All icon-only buttons include descriptive ARIA labels for screen readers
  • Automated Enforcement: ESLint jsx-a11y plugin with 20+ rules enforced at build time, plus runtime axe-core auditing in development

Areas Under Continuous Improvement

  • Color Contrast: We regularly test color combinations for 4.5:1 contrast ratio compliance (WCAG 1.4.3)
  • Heading Hierarchy: We are refining heading levels across card-based layouts for clearer document structure
  • Error Suggestions: Expanding form validation to provide more specific corrective suggestions

Accessibility Features

Navigation

  • Skip link to bypass navigation and go directly to main content
  • Consistent navigation structure with labeled nav landmarks
  • Heading hierarchy (H1, H2, H3) for easy document navigation
  • Landmark regions (header, main, footer, nav) with aria-labels for screen reader navigation
  • Multiple ways to reach all content (navigation bar, direct links, search)

Visual

  • High contrast text and UI elements
  • Text can be resized up to 200% without loss of functionality
  • No content relies solely on color to convey information
  • Animations can be disabled via system preferences (prefers-reduced-motion)
  • Content reflows properly at all viewport sizes without horizontal scrolling

Interaction

  • All interactive elements use native HTML buttons and links for full keyboard and assistive technology support
  • Visible focus indicators on all interactive elements (hidden for mouse users)
  • No keyboard traps; users can navigate freely with Tab and Escape
  • Touch targets are at least 44x44 pixels on all platforms
  • Form inputs have visible labels, inline error messages, and aria-invalid states
  • Swipe gestures always have keyboard alternatives (Escape key for modal dismiss)

Assistive Technology

  • Compatible with popular screen readers (VoiceOver, NVDA, JAWS)
  • ARIA attributes used appropriately for dynamic content, dialogs, and form validation
  • Live regions announce recording state changes, loading states, new messages, and notifications
  • Images have appropriate alternative text; decorative images are hidden from screen readers
  • Conversation messages identify the speaker ("AI assistant says", "You say") for screen reader context

AI Voice Feature

Our AI coaching feature supports both voice and text interaction:

  • Text Alternative: All voice conversations are transcribed and displayed as text in real time
  • Recording Announcements: Screen readers are notified when recording starts and stops via assertive live regions
  • Mute Option: AI audio can be muted in Settings if you prefer text-only interaction
  • Transcript History: Full conversation transcripts are saved and accessible in your Reflections

Known Limitations

While we strive for full accessibility, some limitations exist:

  • Third-party Content: Some embedded content (payment forms via Stripe) follows their own accessibility standards
  • AI-generated Images: AI-generated reflection illustrations may not have fully descriptive alt text
  • Real-time Voice: Live voice conversations require audio capability; text alternatives are always available

Testing Methods

We test accessibility using:

  • Manual keyboard-only navigation testing
  • Screen reader testing (VoiceOver on macOS/iOS)
  • Automated testing with ESLint jsx-a11y plugin (20+ rules enforced at build time)
  • Runtime axe-core accessibility auditing during development
  • Color contrast analysis tools
  • Browser developer tools accessibility audits

Feedback & Contact

We welcome your feedback on the accessibility of Lioma. If you encounter accessibility barriers or have suggestions for improvement, please contact us:

  • Email: info@lioma.eu
  • Response Time: We aim to respond within 5 business days

When contacting us, please include:

  • The URL or location where you encountered the issue
  • A description of the problem
  • The assistive technology you were using (if applicable)
  • Your preferred contact method

Enforcement & Complaints

EU Users: If you are not satisfied with our response, you may file a complaint with your national enforcement body under the European Accessibility Act.

US Users: If you believe Lioma does not comply with accessibility requirements, you may file a complaint with the U.S. Department of Justice or pursue other legal remedies available under the Americans with Disabilities Act.

Technical Specifications

Lioma's accessibility relies on the following technologies:

  • HTML5
  • WAI-ARIA 1.2
  • CSS3
  • JavaScript (React)

These technologies are relied upon for conformance with WCAG 2.1 Level AA.

Continuous Improvement

We are committed to continually improving accessibility. Our efforts include:

  • Regular accessibility audits
  • Accessibility training for our development team
  • Incorporating accessibility into our design and development process
  • Monitoring user feedback and addressing issues promptly

Lioma

Just a moment...