Interface Core C · Industry convention

Chat UI

A chat UI joins messages, sender names, a writing box, send states, and attachments. It also shows ways to fix errors.

Try an example
You might call it messaging UIconversation interfacechat window

Try an example

Chat UI

V.Which pattern are you building?

YouA compact picker with search.

A real example

An AI chat separates user and assistant messages. It streams replies, shows sources, and offers Stop and Retry.

Main parts

  1. 01Trigger or task context
  2. 02Primary control surface
  3. 03Feedback, focus, and dismissal

Use it when

Use it when taking turns in chat is the clearest way to finish the task.

Do not use it when

Never hide set steps, errors, permissions, or actions that can't be undone inside vague chat.

Name used in code

message list + composer + status

Before you ship

Before release, check the page structure, keyboard access, visible focus, contrast, and zoom. Also check loading, empty, error, success, cancel, and reduced-motion states.

Request you can copy

Outcome: Use Chat UI to solve this user need without losing the current context. User context: An AI chat separates user and assistant messages. It streams replies, shows sources, and offers Stop and Retry. Recommended pattern: Chat UI. Why it fits: Use it when taking turns in chat is the clearest way to finish the task. Do not use it when: Never hide set steps, errors, permissions, or actions that can't be undone inside vague chat. Product requirements: Define the default, loading, empty, error, success, and recovery states. Keep user input. Give clear feedback after every action. Accessibility and resilience: Use semantic HTML, full keyboard access, and visible focus. Make the layout work when zoomed and support reduced motion. Follow the project’s current rules. Do not add a new UI library unless the project already uses it. Acceptance criteria: The main task works with keyboard only and at 320px width. Focus and status changes are announced. Check loading, failure, retry, cancel, and reduced-motion paths. Evidence and limits (evidence boundary): No single official standard controls the whole term. Its meaning may change across teams, platforms, or frameworks. Unknowns to confirm: Product wording, data source, analytics events, supported devices and languages, and platform limits.

Check this request

Review the current use of Chat UI. Definition: A chat UI joins messages, sender names, a writing box, send states, and attachments. It also shows ways to fix errors. Release checks: Before release, check the page structure, keyboard access, visible focus, contrast, and zoom. Also check loading, empty, error, success, cancel, and reduced-motion states. Before changing code, report the evidence you found, gaps, severity, and the smallest safe fix.

C
How official is this term?

Industry convention

People often use this term at work. The listed sources may support practice or limitations. They do not define every part of the term.

No single official standard controls the whole term. Its meaning may change across teams, platforms, or frameworks.

Scope
Conversational-interface convention
Document status
recommendation
Checked on
2026-07-30

Evidence sources & scope

Authority source · W3C · recommendation Accessible Rich Internet Applications (WAI-ARIA) 1.2 Scope: Web accessibility semantics Role here: Helpful background, not a definition Source covers: canonical name, definition, semantics, implementation Authority source · W3C WAI · stable Feed Pattern Scope: Non-normative accessible feed guidance Role here: Helpful background, not a definition Source covers: canonical name, definition, interaction, keyboard behavior, accessibility

Copy it yourself

The browser could not copy this. Select the request below and copy it yourself.