Skip to main content
Batoi UIF Docs

Accessibility

Design UIF surfaces with keyboard access, readable contrast, predictable controls, and meaningful status.

Version 3.0.0 Version 3 active maintenance Reviewed Aug 11, 2026 Next review Nov 11, 2026
Start Reading Open GitHub Report documentation issue

Owner: Batoi Engineering Reviewed by: Batoi UIF Maintainers Source revision: b2f3478

Start FastLoad UIF in server-rendered pages and initialize declarative behavior. Chart SupportReview native SVG chart types, Flint mappings, and deferred advanced charts. Micro AppsBuild contained app surfaces that live inside larger Batoi routes. AI and MCPDesign approval UI while privileged tool execution stays server-side.
Browse Batoi UIF Documentation Accessibility
On this page

Accessibility

Batoi UIF surfaces should remain usable with keyboard navigation, assistive technologies, and different viewport sizes.

Baseline Expectations

  • labels for form controls
  • visible focus states
  • readable color contrast
  • meaningful button text
  • status text that does not rely only on color
  • responsive layout without overlap

Micro App Considerations

Interactive Micro Apps should keep controls reachable and outputs readable.

For generated charts, include an accessible label or textual summary.

For status badges, pair color with text.

Testing

Check:

  • keyboard tab order
  • mobile layout
  • text overflow
  • chart fallback meaning
  • form label association