-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Webchat Widget Accessibility issue #4263
Comments
[proposed labels] Bot-framework, Webchat Widget, A11Y , ADA Accessibility |
@jason-walgreens Thanks for the input. I'll add this as a feature request for future consideration. |
If the message is interactive (card or contains buttons), the screen reader will narrate one of the followings and it should guide the end-user how to navigate to the message content.
However, if the message is not interactive, we will not narrate these instructions as non-interactive elements (such as There are 2 possible failures for WCAG 2.4.3:
|
Hi @tracyboehrer . Is there a release plan for this fix? Thanks |
In my previous reply, I mean, the issue you mentioned should not contribute to failure of WCAG 2.4.3. I have listed reasons above that why it does not contribute to failure of this success criterion. |
As mentioned above:
Closing due to inactivity. |
When hidden or new content is revealed or available on the same screen because of any user interaction then focus need to move to the new content either immediately or with one additional keystroke, so that a screen reader user can relate and access the new content without any interruption. In current implementation when a user types something and because of this input a new set of options are available on the chat modal for user to select options from, focus remains in the input field (Type your message, field). Screen reader reads the appearance of the new content but does not read the location of the content and how to access them.
In order to access the options a user need to press “shift+tab” key multiple times. Which is not logical. Since user does not know the location of the newly available content, so he is also not sure on how to access them.
Expectation is, when a new content is available on the screen focus should also move to the new content so that a user can easily access them by pressing “tab” key.
WCAG references: 2.4.3
The text was updated successfully, but these errors were encountered: