Accessibility issue : Elements that have scrollable content should be accessible by keyboard

[tejamora]

Running a fast pass on WebChat bot, getting this error

Path | .react-scroll-to-bottom--css-qgskw-1n7m0yu

Fix ONE of the following:
Element should have focusable content
Element should be focusable

Screenshots

Same replicable on Web Chat's minimizable sample: https://microsoft.github.io/BotFramework-WebChat/06.recomposing-ui/a.minimizable-web-chat/

Version

"botframework-webchat":
"version": "4.10.1",

Steps to reproduce

1. Go to chatbot icon
2. Click on chatbot
3. when there are numerous activities between the bot and user

[Bug]

[CezaryMarcjan]

Hi @tejamora the team will review and follow up on this. Thanks for the report.

[corinagum]

This needs a team discussion, as right now the transcript intentionally only allows focus on interact-able elements. Will report back here.

[compulim]

A previous issue on "should not focus on non-interactive element" (#1340) and WCAG 2.4.3. Since transcript is not interactive element, it should not be focusable based on the issue and WCAG criterion.

Since this accessibility issue is conflicting to one we previously fixed, we should raise this issue to internal accessibility team and ask them to clarify, and possibly a correct/reference implementation.

For instance, WhatsApp Web does not allow focus on the transcript thru TAB keys. But pressing PGUP/PGDN keys will page the transcript up/down.

[corinagum]

For consolidation, I am closing this issue in favor of #2996. Sorry for the inconvenience. This bug is still a high-priority fix for the Web Chat team.

[edemehmetcan]

Please fix this problem asap. The government in Europe is asking that the chatbot is fully compatible with WCAG

[corinagum]

Please note that this is available as of the 4.12.0 release.