Accessibility

MindWiki aims to conform to Web Content Accessibility Guidelines (WCAG) 2.2 Level AA on the marketing site (mindwiki.io) and MindWiki Cloud.

On native apps we follow Apple's human-interface accessibility guidance — VoiceOver support, Dynamic Type, Reduce Motion, Reduce Transparency, increased contrast, and the iOS / macOS keyboard model. Where an iOS surface is rendered via React Native, we use the platform's accessibility APIs (role labels, hints, traits) so VoiceOver behaves the same way as on Swift-native surfaces.

• iOS— VoiceOver labels and traits on every primary control (Create FAB, Settings rows, navigation items). Dynamic Type respected for text content; the editor uses the user's preferred reading size. Reduce Motion honored on boot, modal transitions, and the cinematic landing hero.
• macOS — full keyboard navigation, VoiceOver landmarks for the sidebar, editor, and graph view; system contrast respected.
• MindWiki Cloud— semantic HTML, landmarks (header / nav / main / footer), keyboard focus indicators, ARIA labels on interactive elements that aren't native buttons, color contrast at or above 4.5:1 for body text and 3:1 for large text.
• Marketing site — the live hero on phones skips the JS-driven cinematic and shows the static end-state so users with motion sensitivity or low-performance devices can reach the CTAs immediately.

We're honest about where we're behind. The following are tracked and prioritized:

• The graph view on macOS and Cloud is primarily a visual surface; an equivalent text-list / backlinks view is the accessible alternative but it lives elsewhere in the UI. We're working on keyboard navigation of the graph itself.
• Some animated transitions (boot splash, modal entry) are subject to Reduce Motion but the cinematic landing hero on the marketing site respects the OS flag only when set — we don't expose an in-app override.
• Color-only state indicators (e.g., the sync chip and the System Status dots) include text labels for non-color signaling, but some smaller pills on the marketing site rely on color alone — being fixed.
• Live Conversation audio output does not yet include real-time captioning. Voice Capture produces a transcript at save time.
• The macOS app PDF viewer surfaces text as expected but doesn't yet provide a screen-reader- optimized linearized reading order.

We will update this list as items are completed and as we discover new ones.

If something doesn't work for you, please email support@mindwiki.io with "Accessibility issue" in the subject. Tell us:

• Which platform (iOS / macOS / Cloud / marketing site).
• What you were trying to do.
• What assistive technology you use (if any).
• What didn't work — "the button has no label", "keyboard focus skips", "contrast too low to read".

We commit to acknowledging accessibility reports within 5 business days. Critical accessibility blockers are prioritized into the next release; less urgent items land in our ongoing accessibility backlog.

The European Accessibility Act (Directive 2019/882/EU), in force from June 2025, applies to certain digital products and services in the EU market. MindWiki commits to ongoing alignment with its substantive requirements: perceivable, operable, understandable, and robust digital experiences, with documented progress and a feedback channel (this page).

Conformance is assessed through:

• Automated checks during CI (axe-core for the web surfaces; Xcode Accessibility Inspector on the native apps).
• Manual walkthroughs with VoiceOver and keyboard before each release.
• User-reported issues via the channel above.

We will publish a more formal conformance report once an EU representative is appointed under the Accessibility Act's applicability thresholds.

• Support & Contact
• Help Center
• Legal Notices / Imprint