Accessibility

Platform integration, widget semantics and application responsibilities.

Teksilo builds an accessibility tree alongside the widget tree. Applications remain responsible for testing their interfaces and establishing conformance.

Framework support

• Platform bridges. AccessKit connects each window to AT-SPI on Linux (X11 and Wayland), NSAccessibility on macOS and UI Automation on Windows.
• Widget semantics. Widget::accessibility declares roles, names and actions. Semantically empty layout containers are omitted from the tree.
• Overrides. Set labels, descriptions, roles, live regions and actions on any widget. Use .access_customize(|b| ...) for direct builder access. Accessibility-only bindings update translated labels without rebuilding widgets.
• Contrast checks. CI checks text and focus-indicator contrast. Three of the four theme presets have a contrast gate.
• System preferences. Support includes increased contrast, text scaling from 80 % to 200 %, and reduced motion.

Application responsibilities

Widget::accessibility has an empty default implementation. Custom widgets must supply their semantics; missing implementations produce no accessibility node and no warning.

Test your application with keyboard navigation and real screen readers. Source inspection and framework tests do not establish application conformance. Any required accessibility assessment or conformance report remains the application publisher’s responsibility.

See the accessibility guide for labels, roles and tree customization.