microsoft / microsoft/BotFramework-WebChat

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

Open
#3,804 3 comments 0 reactions 1 assignee View on GitHub

@compulim is already working on this.

Since Mar 24, 2021.

area-accessibility backlog Bot Services customer-replied-to customer-reported ExemptFromDailyDRIReport front-burner
Dominant language
HTML
Stars
1.8k
Forks
1.6k
Avg merge
22h 58m
Merged PRs (30d)
2

Description

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 (#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 ?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.