Keyboard and accessibility

Atoi supports pointer, keyboard, touch, and assistive-technology use. Shortcuts are accelerators; every core action still needs an understandable visible control.

#High-signal web shortcuts

Open the shortcuts dialog for the complete current set and any custom overrides. Sequence shortcuts do not run while focus is in a text input, textarea, or editable region.

#Focus and navigation

Dialogs trap focus while open and return focus to the control that opened them. Lists use predictable arrow-key or tab navigation according to their role. Visible focus rings are part of the design system and should not be removed.

In these docs, Command-K or Control-K opens local search. Arrow keys move through results, Enter opens one, and Escape closes the dialog. The documentation sidebar also supports ArrowUp, ArrowDown, Home, and End.

#Motion and contrast

Navigation and menu-like state changes use no spatial animation. Controls may use short color transitions. Atoi honors reduced-motion preferences and uses semantic design-system colors so light, dark, and custom themes retain their intended contrast relationships.

#Content alternatives

Images need useful alternative text unless they are decorative. Diagrams should be accompanied by an equivalent text explanation. Tables must remain horizontally scrollable without trapping keyboard focus.

If an action is unreachable or unlabeled, report the exact route, control, input method, and assistive technology. See Troubleshooting for the report shape.