Twilio Conversations accessibility parity gap during Programmable Chat migration

Migrating from Programmable Chat to Twilio Conversations involves a fundamental shift from channel-based abstractions to identity-centric models. While the API migration path covers data persistence, there is a lack of documented mapping for the accessibility semantics that bridge the legacy and modern SDKs.

Existing accessible UI components often rely on specific event triggers to manage ARIA live regions and maintain keyboard focus order. Because the Conversations SDK emits different event names and payload shapes compared to the legacy API, logic responsible for announcing typing states, new messages, or unread counts may not trigger correctly. This creates a compatibility boundary for users who rely on assistive technology to navigate real-time chat workflows.

What are the direct equivalents in the Conversations SDK for Programmable Chat events that trigger ARIA live region updates? How should focus management be reconfigured when the conversation lifecycle shifts from channel-based to an identity-based model?