Accessibility
Checked against c1b2fa4 on 2026-11-10. The files it covers are unchanged since.
Mostly not built. niso doesn’t expose the page to screen readers yet: there’s no accessibility tree, so VoiceOver and TalkBack can’t read a niso page’s text or understand its structure, roles or ARIA attributes. Don’t ship an app that needs to be accessible on niso yet.
What works today
Section titled “What works today”- Native controls are the platform’s own buttons, switches, sliders,
pickers and text fields, so assistive technologies can find and operate
them. An accessibility activation of a button (with no touch) reaches the
page as a press (
NodeView.swift,Controls.kt). - Display settings reach the page: text size, bold text, dark mode, increased contrast and reduced transparency (System settings).
The plan
Section titled “The plan”DECISIONS.md, Accessibility: an AccessKit tree derived from the DOM and ARIA, exposed through AccessKit’s platform adapters, with native controls contributing their own nodes. The tree is derived from the DOM the same way the native view tree is. None of it is on main.