BrailleKit is built with screen-reader and keyboard-only use as the primary workflow, not an afterthought:
- Screen readers: full support for NVDA, JAWS (Windows), VoiceOver (macOS), Orca (Linux) via platform-native accessibility APIs (MSAA/UIA, NSAccessibility, ATK).
- Keyboard navigation: every control reachable via Tab/Shift-Tab, every menu operable with Alt + access key. No mouse-only flows.
- High contrast: the app follows the OS high-contrast theme.
- Dark mode: system-synced, manual override available.
- Font scaling: scales with the OS DPI setting; no fixed pixel sizes in text.
- Reduced motion: animations disabled when the OS asks for it.
The API documentation (docs/api/html/index.html) ships with the
same treatment: keyboard-navigable tree view, focus rings, system-
aware dark mode with a user toggle.
Per-platform notes
Windows. UIA is the primary accessibility API. NVDA and JAWS both read all controls without custom scripts. Narrator works for the most common views but its UIA support has more gaps than NVDA/JAWS.
macOS. VoiceOver reads all controls. The app announces its name in the user's chosen UI language (not the system language), so non-English UIs read correctly with English VoiceOver speech.
Linux. Orca via ATK. Tested with GTK 3 widget set.
Next steps
- Troubleshooting — accessibility-related issues and fixes.