Accessibility improvements for carousel #5117

Activity

1. William Wong (compulim)

   added

   area-accessibility

   feature-requestAzure report labelAzure report label

   on Apr 1, 2024
2. OEvgeny commented on Oct 21, 2026

   

   Eugene (OEvgeny)

   on Oct 21, 2026

   Collaborator

   More actions

   Thanks for the suggestion.

   The carousel is now easier to use with the keyboard:

   • When a card has focus, Left and Right move the focus to the previous and next card (mirrored in right-to-left), and Home and End to the first and last card. The card is scrolled into view, as the flippers do (Move focus between carousel cards with arrow keys #5904).
   • Left and Right on a button or link inside a card no longer scroll the carousel away from the focused control (Keep the carousel still when arrow keys are pressed on a button or link inside a card #5917).
   • A card that receives focus with Tab is scrolled into view (Scroll carousel cards into view when focused with Tab #5926).
   • The keyboard help screen of point 3 was removed in 4.19.0 (remove keyboard helper screen from web chat #5234). The arrow keys are documented in docs/ACCESSIBILITY.md.

   We chose plain arrow keys on a focused card instead of Ctrl + arrows (point 2), because they move the focus with the scroll, so keyboard and screen reader users stay on the card they see. The flippers are still in the Tab order (point 1), because keyboard users who do not know the arrow-key shortcut still need a visible control to scroll (WCAG 2.1.1). These changes are on main and will ship in the next release.

   We are closing this issue as fixed by #5904. Please reopen if the flippers should still leave the Tab order.
3. Eugene (OEvgeny)

   closed this as completedon Oct 21, 2026
4. OEvgeny commented on Oct 22, 2026

   

   Eugene (OEvgeny)

   on Oct 22, 2026

   Collaborator

   More actions

   The fixes (#5904, #5917, and #5926) are now available in the nightly build botframework-webchat@4.19.3-main.20261021.71a806e (npm tag main), and will ship in the next release.