Streaming response
Partial text becomes paced updates instead of token-by-token announcements.
Interactive examples · live package APIs
Run common app scenarios through @generative-a11y/core and @generative-a11y/dom. Follow each app event, runtime update, and browser result.
Test scope: the transcript confirms what the library added to the page. Test with a real screen reader to confirm what it speaks.
Server-rendered guide
Each scenario dispatches public events through @generative-a11y/core and delivers the resulting announcement intents with @generative-a11y/dom.
Partial text becomes paced updates instead of token-by-token announcements.
Confirmed tool progress and results receive concise status updates tied to one tool identity.
A request for user input receives higher priority while routine activity leaves focus unchanged.
Failure, retry, stop, and stale-response events remain attached to the response that produced them.
Your app
generative-a11y leaves this interface and its focus behavior unchanged.
Accessibility layer
Browser results confirm the page update. Test with a real screen reader to confirm what it speaks.
Event timeline
| Time | Event | Identity | Observed result |
|---|---|---|---|
| Choose a scenario to fill the timeline. | |||