Accessibility#

Automexia is designed to remain usable with a keyboard, at high zoom, and on small or large displays. Accessibility claims stay limited to behavior the project can test and verify.

Keyboard access#

Core workspace actions have keyboard paths:

create and close tabs or panes;
move focus between visible panes;
open and dismiss search;
select and copy terminal text;
open the command palette;
leave dialogs without using a pointer.

Visible focus identifies the active pane and the control that will receive input.

Clear state#

Important states use text, shape, or position as well as color. Errors, selected items, active panes, and command results do not rely on color alone.

Flexible layout#

The interface is tested at narrow widths, large desktop sizes, high pixel density, and increased text scaling. Lower-priority chrome can move or disappear before the terminal becomes unusable.

Motion and contrast#

Short transitions avoid repeated flashing and do not move terminal content. Reduced-motion preferences keep persistent state cues while removing unnecessary animation.

Text and controls are checked against the project contrast rules in both light and dark surfaces.

Screen readers#

Standard text remains available through the terminal and operating-system text paths. Custom application surfaces use clear names and logical focus order where supported.

Native screen-reader behavior can vary by operating system, desktop environment, renderer, and assistive technology. Release notes must describe verified combinations instead of making a universal claim.

Reporting an accessibility issue#

Include the operating system, display scale, input method, assistive technology, the action you attempted, and the result. Do not include private terminal output, credentials, or personal paths.