[Screen reader - Bot Framework Web Chat - Card Breakfast]: Screen reader is announcing incorrect position information as '2 of 3' list items for the 'Snooze time' combo box. #5357
Labels
area-accessibility
Bot Services
Required for internal Azure reporting. Do not delete. Do not change color.
bug
Indicates an unexpected problem or an unintended behavior.
customer-reported
Required for internal Azure reporting. Do not delete.
external-adaptive-cards
Is it an issue related to Adaptive Cards?
No.
What is the PWD impact?
User Experience:
If the screen reader announces does not announce position count or incorrect position count for the controls, then the person who relies on screen reader will not be able get the correct information to activate and use the controls.
Note:
User credentials should NOT be included in the bug.
What browsers and screen readers do this issue affect?
Windows: Edge with Windows Narrator
Are there any code-based customization done to Web Chat?
No, I am using Web Chat without any customizations except "styleOptions".
What version of Web Chat are you using?
Latest production
Which area does this issue affect?
Others or unrelated
What is the public URL for the website?
No response
How to reproduce the issue?
What do you expect?
Screen reader should announce correct position information for the 'Snooze time' combo box.
Ex: Screen reader should announce as 'Snooze time 10 minutes combo box collapsed has pop up' after enter key '10 minutes 1 of 2 selected'
What actually happened?
Screen reader is announcing incorrect position information as '2 of 3' list items for the 'Snooze time' combo box.
Observation: Screen reader is announcing as 'Snooze time 10 minutes combo box collapsed has pop up' after enter key '10 minutes 1 of 3 selected'
Do you have any screenshots or recordings to repro the issue?
https://github.com/user-attachments/assets/43894366-93ab-4587-bf9b-7a33aeb4abcc
Did you find any DOM elements that might have caused the issue?
No response
MAS reference
MAS 1.3.1 – Info and Relationships
WCAG reference
No response
WAI-ARIA reference
No response
Adaptive Card JSON
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: