Keyboard-first interaction
Core navigation, forms, dialogs, controls, and recovery actions should be reachable without a mouse. Focus states are kept visible so a person can tell where they are.
ChuskyAccessibility
A product people can
use in their own way.
Accessibility is part of making an agent understandable: people should be able to read what it is doing, reach the next action, recover from an error, and review an approval with the tools they already use.
Our approach
The agent’s state should never be hidden behind a visual effect.
Chusky has long-running work, tool activity, approvals, and provider failures. Each of those states needs a text equivalent and a clear next step, whether someone is using a keyboard, screen reader, magnification, voice control, or a small touchscreen.
Readable visual language
The interface uses semantic headings, meaningful labels, restrained decoration, and contrast-conscious surfaces. Status should not be communicated by color alone.
Content that can be heard
Progress, approvals, failures, and completion states are written as text and exposed through appropriate labels so assistive technology can follow the same lifecycle.
Reduced motion
Decorative reveals should not be required to understand or complete a task. The interface respects reduced-motion preferences and keeps important feedback available without animation.
Agent activity
Progress, waiting, failure, and completion are different states.
We aim to make agent activity concise enough to scan and detailed enough to act on. A run should explain whether it is working, waiting for approval, missing a connection, retryable, cancelled, or complete. Raw provider payloads and secrets should stay out of the user-facing view.
When work is running
Show a plain-language progress label and preserve the run identifier for reconnecting.
When a decision is needed
Name the action, target, and consequence before asking someone to approve it.
When something fails
Explain what can be retried, what was not confirmed, and how to get back to the saved work.
Known limits and feedback
Accessibility is an ongoing product responsibility.
Some provider-hosted consent screens, embedded documents, generated files, and third-party browser surfaces are outside the control of the Chusky web interface. We still want reports about barriers so we can improve our surface and document the boundary honestly.