Our core product promise
Accessibility statement
Last reviewed 11 August 2026. NaviWeb is designed for blind screen-reader users first.
Our commitment
We aim for WCAG 2.2 Level AA across the learning shell: sign-in, navigation, lessons, settings, progress, help, and administration. We use native HTML before ARIA, keep focus order aligned with reading order, and expose every control’s name, role, value, and state.
Intentional training barriers
Clearly marked Barrier Labs deliberately demonstrate selected accessibility failures. Those isolated examples do not conform to WCAG and are never used in global navigation, account access, completion controls, or settings. Every barrier has a safe exit and a conforming alternative.
Compatibility target
- NVDA with Firefox and Chrome on Windows
- JAWS with Chrome and Edge on Windows
- Windows Narrator with Edge
- VoiceOver with Safari on macOS and iOS
- TalkBack with Chrome on Android
- Keyboard-only, zoom, forced-colours, reduced-motion, and 320 CSS-pixel reflow
Automated checks support but never replace testing with actual assistive technology and blind users.
Standards and references
Report a barrier
When feedback channels are connected, NaviWeb will publish a direct email and issue form here. For now, report issues through the project’s GitHub repository after launch.