search

microsoft / AdaptiveCards

A new way for developers to exchange card content in a common and consistent way.
https://adaptivecards.io
MIT License
1.75k stars 550 forks source link

[Teams][Accessibility] [TextRun element focusable on Android while all other elements are not] #5207

Open lindach167 opened 3 years ago

lindach167 commented 3 years ago

https://user-images.githubusercontent.com/29580478/102677799-0c593600-4159-11eb-9d26-6ba272b6a8e2.mp4

originalCardJson.txt

Platform

What platform is your issue or question related to? (Delete other platforms).

Author or host

Are you an author (like sending something to Outlook), or a host that is rendering your own cards? If host, please specify the corresponding host (app) name.

Host - Teams Mobile

If you're an author, who are you sending cards to?

Version of SDK

What version are you using? Ex: NuGet 1.0.2, or latest main, etc...

1.2

Details

Explain your issue. If you just have a question, please post on StackOverflow instead.

Using TextRun elements is causing accessibility focus issues on Android. See attached video and card JSON. It seems that for all other adaptive card elements, like TextBlock, they are set to fosuable: false, however, for some reason the TextRun elements is rendering with fosuable; true. This causes very unexpected results when used alignside other TextBlock elements. When the focus is on the whole card, it skips reading the TextRun elements. When swiping to next element, it then jumps only to the TextRun element, causing a very confusing user experience. See video for example, where "16 hours" is rendered using TextRun.

Currently we are recommending from Teams to not use TextRun next to TextBlock because of this accessibility issue. So while developers can work around this by using other types of elements, they will not be able to leverage the features of TextRun.

This does not repro on iOS or Web

ghost commented 3 years ago

please review this issue for target Milestone, Inconsistencies & Priority upon triage.

ghost commented 3 years ago

Hi @lindach167. We have acknowledged this issue report. Please continue to follow this issue for updates/progress/questions.

shalinijoshi19 commented 3 years ago

@golddove can you take a stab at this real quick? Thanks!