spec 2 linked patterns checked

W3C ARIA23: Using role=log to identify sequential information updates

Documents role=log as a way to expose appended sequential updates such as chat conversation history to assistive technologies.

Read with a purpose

What this source can teach

Use this source to check a technical or accessibility requirement against its exact wording and scope.

  1. Start with the original. Open the source and find the guidance or example relevant to your task.
  2. Trace the connection. Use the claim notes below to see how this site applies the source to specific patterns.
  3. Check the setting. Compare the source's platform, people, and constraints with your own decision.

Pattern Decisions This Source Supports

Pattern Supported decision Required contract Claim note
Agent progress trace Choose agent progress trace when an agent or automation run has started and users need live status across multiple steps or tools. The trace belongs to one run ID, reviewed plan version, objective, actor, start time, current state, and final state. Supports exposing appended sequential updates to assistive technologies.
Chat interface Choose chat interface when the user task depends on turn-taking, follow-up prompts, assistant responses, and conversation history rather than a single request field. Every user-visible answer is tied to the exact user message and visible context that produced it. Supports accessible announcement of appended sequential chat messages.

Comparisons supported by this source

Evidence Role

This source is treated as spec evidence. Its value comes from the specific claims and setting described above.

Publisher: W3C WAI. Last checked: .

Saved items