• The chat window is exposed to screen readers even when it is closed, which may cause confusion for users who rely on assistive technologies.

• When the chat window is opened, it appears at the very end of the reading order because the screen reader follows the DOM structure rather than the visual layout. As a result, users may need to navigate through the entire page before reaching the newly opened chat interface.

Potential Improvement Considerations

Is it possible to hide the chat window from assistive technologies while it is closed by applying display: none and only making it visible when the user opens it?

When the chat window is opened, could the focus be automatically moved to the chat’s input field to ensure that users immediately understand its location and can begin interacting without additional navigation?