Closed UdhayaKumarDuraisamy closed 11 months ago
@UdhayaKumarDuraisamy welcome to the NVDA project. This is due to the fact that NVDA provides a virtual navigation mode called browse mode in which the keyboard is overtaken by the screen reader in order to provide a more efficient way of navigating. You can turn browse mode off by pressing nvda key+space bar or by disabling the coresponding setting in NVDA browse mode settings. Closing as invalid.
Also please don't use only screen shots to describe things, but insert a text showing what is on the screenshot. There are lots of blind developers who cannot investigate because we cannot read what's on the screenshot.
I also encourage you to study the user guide of NVDA, there is everything you need to know about browse mode and focus mode and how NVDA works.
Summary
I have a custom MultiSelect component that I built using a Blazor server application. After selecting multiple values, the selected values are appended as chips. I have provided support to move focus to the chips when the user uses the Left or Right arrow keys. This functionality works well except when using the NVDA screen reader. When NVDA is enabled, after selecting values, if the user uses the Left key, it announces the value properly. However, if the user uses the Left key again, it reads each letter of the word instead of reading the word as a whole. Additionally, it breaks the Left/Right key navigation. You can refer to the below shaed videos for more details.
DOM Structure:
Actual behavior:
If the user uses the left key again, it reads each letter of the word instead of reading the word as a whole. Additionally, it disrupts the left/right key navigation.
Expected behavior:
The NVDA reader needs to announce the selected values chip properly, and it should not break the functionality of keyboard navigation.
NVDA logs, crash dumps and other attachments:
[Without NVDA]
[With NVDA]
System configuration
NVDA installed/portable/running from source:
NVDA version:
Windows version:
Edition : Windows 11 Enterprise Version : 22H2
Does the issue still occur after restarting your computer?
Yes.