Skip to content
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

[Accessibility] [Omnichannel] Screen reader is not notifying the user when the agent is typing #4099

Closed
elopezanaya opened this issue Dec 20, 2021 · 4 comments · Fixed by #4210
Assignees
Labels
area-accessibility Bot Services Required for internal Azure reporting. Do not delete. Do not change color. customer-replied-to Required for internal reporting. Do not delete. customer-reported Required for internal Azure reporting. Do not delete. external-omnichannel feature-request Azure report label needs-team-attention

Comments

@elopezanaya
Copy link

Environment Details:
Application Name: Microsoft Dynamics 365 Omnichannel Online Chat – CRA Online Chat Agent
#URL: Omnichannel Agent Dashboard
Windows Version: Win10
Chromium edge Version 98.0.1089.1 (Official build) dev (64-bit)

Describe the bug

When the user tabs to the minimized chat window and opens it after hearing that a message has been received, the screen reader does not automatically start reading the messages they received.

Steps to reproduce

  1. Start Narrator/jaws.
  2. Hit the URL "Omnichannel Agent Dashboard" and login with appropriate credentials
  3. Tab to Omnichannel Administration app and hit enter
  4. Tab to "chat" menu item and hit enter, select a chat and tab to code snippet under general settings.
  5. Open url "aka.ms/omniwidget" and paste the code from code snippet .
  6. Tab to the Let's chat button and initiate a conversation
  7. Hit URL: Omnichannel Agent Dashboard and log in with appropriate credentials in another browser as an agent.
  8. Tab till accept button in the new chat dialog and press enter.
  9. From the agent chat, reply the message from the customer
  10. Narrator should notify the user that the agent is typing.

Expected behavior

Narrator should start to read the new messages send by the agent.

Additional context

[Bug]

@elopezanaya elopezanaya added Bot Services Required for internal Azure reporting. Do not delete. Do not change color. bug Indicates an unexpected problem or an unintended behavior. customer-reported Required for internal Azure reporting. Do not delete. labels Dec 20, 2021
@elopezanaya elopezanaya changed the title Screen reader is not notifying the user when the agent is typing [Accessibility] [Omnichannel] Screen reader is not notifying the user when the agent is typing Dec 20, 2021
@tdurnford
Copy link
Contributor

@compulim Any updates on this issue?

@carlosscastro
Copy link
Member

@compulim could you please update this issue?

@msomanathan
Copy link

@compulim Could you please provide an update to this issue?

@compulim
Copy link
Contributor

This is a new feature and will be triaged.

@compulim compulim added needs-team-attention customer-replied-to Required for internal reporting. Do not delete. feature-request Azure report label area-accessibility external-omnichannel and removed bug Indicates an unexpected problem or an unintended behavior. labels Feb 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-accessibility Bot Services Required for internal Azure reporting. Do not delete. Do not change color. customer-replied-to Required for internal reporting. Do not delete. customer-reported Required for internal Azure reporting. Do not delete. external-omnichannel feature-request Azure report label needs-team-attention
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants