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

In mobile scan mode, bot activity is read twice before focus moves to an attachment #3804

Open
tanuj01 opened this issue Mar 22, 2021 · 3 comments
Assignees
Labels
area-accessibility backlog Out of scope for the current iteration but it will be evaluated in a future release. 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. ExemptFromDailyDRIReport exempt from daily DRI report front-burner
Milestone

Comments

@tanuj01
Copy link

tanuj01 commented Mar 22, 2021

Issue description update: (by @corinagum)

When starting with focus at the top of the activity, mobile behavior is wonky where the activity repeats twice before the user can focus INSIDE of the Adaptive Card. Repro steps:

  1. Send 'card calendar', and focus on this activity from the user (I used tap as opposed to swipe)
  2. Swipe right multiple times:
    1. Speak timestamp of user's activity
    2. "Bot said, landmark:"
    3. "Showing calendar" (activity)
    4. "1 attachment"
    5. Speak timestamp of bot activity
    6. "Press enter to interact" <-- needs to be removed on mobile (Modify 'Use arrow keys...' aria label - doesn't work in Chrome, and remove on mobile #3758)
    7. "Bot said"
    8. "Showing calendar"
    9. "Bot attached"
    10. "Adaptive Card design session"

As seen in steps 2-4, then 7-9, double aria labels are being read twice when they shouldn't be.


Original text:

How to shift between adaptive cards on an Android phone using accessibility gestures. As per the latest 4.12.0 release, we can use up and down arrow key using keyboard but the same thing can't be achieved on using the bot in Android phone using gestures. Is there any alternative/solution for this ?

@stevkan stevkan added Bot Services Required for internal Azure reporting. Do not delete. Do not change color. customer-reported Required for internal Azure reporting. Do not delete. labels Mar 22, 2021
@corinagum corinagum added the support Internal request for assistance from the Support Team label Mar 22, 2021
@carlosscastro carlosscastro assigned corinagum and unassigned corinagum Mar 23, 2021
@corinagum
Copy link
Contributor

@tanuj01 are you saying Android gestures are not working on mobile (inside Adaptive Cards) when navigating the transcript?

@corinagum corinagum removed the support Internal request for assistance from the Support Team label Mar 23, 2021
@corinagum corinagum self-assigned this Mar 23, 2021
@tanuj01
Copy link
Author

tanuj01 commented Mar 24, 2021

@corinagum the Android gestures are working in case user wants to traverse from top to bottom of the webchat through each Adaptive card and it's adaptive buttons.

But my ask is, just like we use Up and Down arrow keys on keyboard to traverse directly between Adaptive cards and if user wants to interact with the card then only the user has to press Enter button otherwise using Up and down arrow keys, user can move to next message or Adaptive card.
So, can the same functionality be achieved in mobile through gestures. Currently I have tested all possible gestures but unable to achieve the above mentioned functionality on mobile through gestures.

@carlosscastro carlosscastro added the customer-replied-to Required for internal reporting. Do not delete. label Mar 24, 2021
@corinagum
Copy link
Contributor

corinagum commented Mar 24, 2021

I can only test on iOS as I don't have Android, but here are my notes: (@compulim can you verify this behavior on Android?)

  • Assuming the Adaptive Card is attached in the latest activity: when focused in the send box, swiping left multiple times will focus inside the transcript and automatically focus inside the last section of the Adaptive Card. Input items (if applicable) are interactable as normal.
  • 'Press Enter to interact' text should not be spoken on mobile - I have updated Modify 'Use arrow keys...' aria label - doesn't work in Chrome, and remove on mobile #3758 with this extra item
  • When starting with focus at the top of the activity, mobile behavior is wonky where the activity repeats twice before the user can focus INSIDE of the Adaptive Card. Repro steps:
    1. Send 'card calendar', and focus on this activity from the user (I used tap as opposed to swipe)
    2. Swipe right multiple times:
  1. Speak timestamp of user's activity
  2. "Bot said, landmark:"
  3. "Showing calendar" (activity)
  4. "1 attachment"
  5. Speak timestamp of bot activity
  6. "Press enter to interact" <-- needs to be removed on mobile (Modify 'Use arrow keys...' aria label - doesn't work in Chrome, and remove on mobile #3758)
  7. "Bot said"
  8. "Showing calendar"
  9. "Bot attached"
  10. "Adaptive Card design session"

As seen in steps 2-4, then 7-9, double aria labels are being read twice when they shouldn't be.

I'm updating this issue to reflect the bug described above.

@corinagum corinagum assigned compulim and unassigned corinagum Mar 24, 2021
@corinagum corinagum added backlog Out of scope for the current iteration but it will be evaluated in a future release. front-burner area-accessibility labels Mar 24, 2021
@corinagum corinagum changed the title Accessibility issue on using webchat on mobile app In mobile scan mode, bot activity is read twice before focus moves to an attachment Mar 24, 2021
@peterinnesmsft peterinnesmsft added the ExemptFromDailyDRIReport exempt from daily DRI report label Apr 5, 2021
@corinagum corinagum added this to the R14 milestone Apr 6, 2021
@Kaiqb Kaiqb removed this from the R14 milestone Jun 21, 2021
@compulim compulim added this to the R15 milestone Jun 29, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-accessibility backlog Out of scope for the current iteration but it will be evaluated in a future release. 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. ExemptFromDailyDRIReport exempt from daily DRI report front-burner
Projects
None yet
Development

No branches or pull requests

7 participants