The chatbot interface appears to be inaccessible to screen reader and keyboard-only users.
Issue Summary:
Users cannot enter, navigate, interact with, or exit the chatbot interface using a keyboard and screen reader. This creates a significant barrier for people who rely on assistive technologies.
Observed Behavior:
Keyboard focus does not move into the chatbot interface.
Screen readers do not clearly announce the chatbot region, controls, or available actions.
Users cannot consistently navigate between messages, input fields, buttons, and other interactive elements using standard keyboard commands.
Some are not reachable via keyboard navigation or may not have accessible labels.
Once inside the chatbot interface, users may have difficulty exiting the chat area and returning to the rest of the page.
Expected Behavior:
All chatbot functionality should be fully operable using only a keyboard.
Interactive elements should receive keyboard focus in a logical order.
All controls should have descriptive accessible names and roles that are announced correctly by screen readers.
New chatbot messages should be announced automatically through appropriate live region support.
Users should be able to enter and exit the chatbot interface without becoming trapped in the component.
The chatbot should be compatible with common screen readers such as NVDA, JAWS, VoiceOver, and TalkBack.
Thank you for taking the time to provide such detailed feedback regarding the accessibility of the chatbot interface. We appreciate you highlighting these concerns and outlining the expected behavior for keyboard and screen reader users.
To help our team better understand the current experience and investigate the issue more effectively, would you be able to provide a screen recording demonstrating the behavior when using a screen reader and keyboard navigation? If possible, please include the screen reader being used (e.g., NVDA, JAWS, VoiceOver, or TalkBack) and the browser/device environment. This additional information would be very helpful for our assessment.
Thank you again for bringing this to our attention. We look forward to your response.
Thank you for taking the time to share your feature request. I have already forwarded it to our team for review and consideration.
While I’m unable to provide an estimated timeline for implementation at this time, any updates regarding this feature will be posted as soon as they become available.
We truly appreciate your feedback and your interest in helping us improve our product. Please feel free to reach out if you have any additional suggestions or questions.
Thank you for reaching out and following up. Let me check with our team to see if there are any updates available. I’ll get back to you as soon as I have more information.
Thanks for following up! This feature is already in progress and is currently awaiting deployment. We’ll let you know as soon as it has been implemented.
Don’t mean to hijack this very important thread…
You also have another related ADA issue that needs to be addressed. “iframe” and “frame” elements must have a title attribute. This is not in your current JavaScript. You need to either provide a configuration option for this or update your embedded code to include this WCGA/ADA required feature.
