Conversation design · Explore this field ↗ · Practice · 2 min read
Accessible conversation is more than screen-reader support
Design message pacing, focus, alternatives, error repair, and help as one accessible system.
Conversation creates distinctive barriers
Messages arrive over time, histories grow, and controls change with state. A screen reader user needs new content announced without being thrown to the bottom. A user with cognitive or language disabilities may need more time, plain wording, and stable choices. A person with a speech disability needs an equivalent text path. W3C research notes that chatbot-specific questions—pacing, focus, message history, and embedding—are not fully solved by generic page compliance alone.
Keep the user oriented
Give the conversation a clear name and status. Keep help and human contact in consistent locations. Mark who sent each message semantically, not only by color. Let users pause, review, copy, and download where appropriate. Do not clear input on validation failure. Warn before session expiry and preserve recoverable drafts.
Offer equivalent routes
Buttons can reduce typing but must not trap users in predefined choices. Voice output needs captions or text; audio input needs a typed alternative. Complex choices may be clearer in a table or form than sequential chat. Accessibility sometimes means leaving the conversation metaphor.
Operator note
Test with keyboard only, screen magnification, a screen reader, reduced motion, 200% zoom, voice off, and slow network. Include users with disabilities in moderated studies. Automated checks catch markup failures, not whether a ten-message repair loop is usable.
An accessible transcript model
Represent the conversation as a named region with an ordered message list. Each message needs a programmatically identifiable sender and status. Announce new responses politely without moving keyboard focus. Keep the composer reachable in a predictable order, preserve text after validation errors, and let users navigate back through message groups. When a tool starts or a human joins, expose that state in text. These choices make the transcript work with assistive technology while also improving orientation for anyone returning after a pause.
Primary reading
Sources and limits
These links support the architecture, policy, or product behavior discussed above. Vendor documentation describes vendor features; it is not independent proof of performance. Current details should be rechecked before a production decision.