Our commitment
Ioka is committed to making ioka.online usable by the widest possible audience, including people with visual, auditory, motor and cognitive differences. We treat accessibility as a design discipline, not a compliance exercise.
Standards we aim for
We target Web Content Accessibility Guidelines (WCAG) 2.2, Level AA conformance as our working standard. We also follow the authoring guidance in the WAI-ARIA Authoring Practices Guide where applicable.
What we have done
- Semantic structure. Every page uses a logical heading order (one H1, nested H2 and H3), landmark regions (header, nav, main, footer) and ARIA labels on interactive controls where native semantics are not enough.
- Keyboard access. Every interactive element on the site can be reached and operated with a keyboard. Focus is visible, with a 2-pixel outline in brand indigo.
- Colour contrast. Body text meets WCAG AA contrast ratios (4.5:1 for normal text, 3:1 for large text) against its background. Interactive elements and focus states meet or exceed the 3:1 non-text contrast threshold.
- Reduced motion. Animations respect
prefers-reduced-motion. The Ioka Guide (our floating help icon), scroll-reveal effects, and hover transitions all gracefully fall back to static presentation when a visitor has reduced motion enabled. - Screen-reader labels. Icon-only buttons, decorative imagery and non-text controls have accessible names. The mobile menu uses correct
aria-expandedandaria-controlswiring. - Resizable text. The layout tolerates browser zoom up to 200% without loss of content or functionality. We use
rem-based typography and fluid clamp-based scaling. - Form accessibility. The booking flow routes to Calendly, which maintains its own accessibility documentation. Any native forms on ioka.online use associated
<label>elements and visible error messaging. - Skip-friendly structure. Our page lengths and heading rhythm are designed so that screen-reader users can skim via headings and skip to content.
Known limitations
We are honest about the places where we do not yet meet our own standard:
- A small number of embedded third-party widgets (Calendly, embedded video from external platforms) do not sit under our direct control and may have their own accessibility quirks.
- Some of our older insight imagery does not yet have detailed alternative text. We are backfilling this.
- Our floating Ioka Guide (the small animated face) uses an animated SVG. Where
prefers-reduced-motionis set, all animation is disabled. The guide can also be permanently dismissed by any visitor via the “Don’t show these” control on the first tooltip.
Assistive technologies we test with
- Screen readers: VoiceOver (macOS and iOS), NVDA (Windows), TalkBack (Android).
- Browsers: Latest two versions of Chrome, Safari, Firefox and Edge.
- Devices: Desktop (1280–1920px), tablet (768–1024px), mobile (320–430px).
How to contact us about accessibility
If you encounter an accessibility barrier on ioka.online — something you cannot read, operate, or understand — please tell us. Email hello@ioka.online with the subject line “Accessibility” and, if possible, include:
- The page URL where the issue occurs.
- Your browser and any assistive technology you were using.
- A short description of what you expected to happen and what actually happened.
We aim to acknowledge accessibility reports within two business days and to fix or respond substantively within ten business days for issues under our direct control.
Formal complaint
If you are not satisfied with our response, you may escalate to the data-protection or accessibility authority in your jurisdiction. In the European Union, you can lodge a complaint under the European Accessibility Act with your national enforcement body. In the United States, the Department of Justice administers Title III of the Americans with Disabilities Act (ADA).
Review and updates
This statement is reviewed every six months and updated when the site materially changes. It was last reviewed in October 2026.