Accessibility Statement

Fluctara is working towards WCAG 2.2 Level AA across the public site and current web application. This statement reports implemented support and unresolved work; it is not a certification or a claim of independent conformance.

Last reviewed: 8 August 2026.

Implemented support

  • Semantic landmarks, heading structure, labelled controls, visible keyboard focus, and skip links.
  • Keyboard-operable navigation and transport controls with enlarged touch targets.
  • Dark and light themes, a higher-contrast preference, larger text, and a system-font alternative.
  • Status and error announcements for preference saving, session rendering, and audio playback.

Motion, audio, and immediate stop

  • The public site does not start example audio automatically. Audio starts only after an explicit action and retains a visible stop control.
  • Current entrainment audio contains no speech or dialogue, so captions and transcripts are not applicable. Numeric frequency, duration, phase, and static waveform information provide non-audio alternatives for the interface state.
  • Operating-system reduced motion and the in-app reduced-motion preference suppress non-essential animation and use static waveform alternatives.
  • Session preparation can be cancelled before playback. Active playback has separate pause and immediate stop controls.
  • We avoid intentional strobe effects. Sensory alternatives preserve interface meaning but do not claim an equivalent physiological effect.

How we test

Current checks combine semantic source gates, automated component tests, keyboard journeys, browser accessibility-tree inspection, reduced-motion checks, focus-order checks, and zoom/reflow tests on desktop and mobile Chromium. Automation helps prevent regressions but cannot establish WCAG conformance by itself.

Critical journeys are reviewed for keyboard access, control names and roles, visible focus, status and error communication, touch target size, reduced motion, optional audio, and stop or cancel availability.

Known gaps

  • A complete independent screen reader matrix across all current application routes has not yet been completed.
  • Checkout, download delivery, support, and refund journeys are not all publicly available, so end-to-end accessibility for those processes is not claimed.
  • The older compatibility client under /static is outside this current-app review and may not provide the same support.
  • Reviewed German publication and broader assistive-technology coverage remain pending.

Contact and feedback

If an interface blocks you, tell us which page, control, browser, operating system, and assistive technology you used. Contact protoscience@anulum.li. We will acknowledge reproducible barriers and record unresolved gaps without overstating conformance.