Feature Request: Accessibility Audit WCAG-Guidelines

Request 1:

When the chat widget is clicked, it opens, but the focus does not move to the chat window. Instead, the focus stays on the chat button, making it difficult to navigate the chat widget.

Request 2:

The issue means that when a user opens a chat widget, pressing the Escape key does not close it. This can make navigation difficult for keyboard and screen reader users, who expect the Escape key to quickly close the chat widget. Not supporting this behavior can slow down navigation and make the site less accessible.

Hi @Rathna,

Thanks for reaching out.

  1. Would you like the widget to open directly in the Chat view where the customer can start typing?

  2. Great find. I’ll speak with the team to see if we can minimise the widget when a user hits the ESC key whilst the widget is maximised.