Accessibility

Accessibility is part of BeeUI’s component behavior contract, not a visual add-on. Use semantic labels/descriptions/states, preserve focus order, keep touch targets usable, and let text/control surfaces grow under Dynamic Type or Web zoom.

Task guides

Keyboard & focus
RTL & localization
Large text & zoom
Reduced motion
VoiceOver & TalkBack expectations

Overlays need special attention: modal surfaces own a modal accessibility boundary while anchored overlays participate in the nearest overlay scope; Escape/back/outside-press and focus restoration follow each component contract rather than a one-size-fits-all rule. Status/Toast surfaces use live announcements where the component contract requires them.

Automated browser scans, Jest semantics, native compilation and device assistive-technology runs prove different things. BeeUI never treats an automated scan as accessibility certification or a native compile as VoiceOver/TalkBack runtime proof.

Canonical sources: accessibility contract, keyboard/focus matrix, and Web audit.