You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I am blind from birth and use a screen reader, JAWS, to navigate and interact with software. Screen readers work by translating the visual elements of an interface into audio or braille output. They identify components such as buttons, text fields, and other interactive elements and rely on accessible labels to convey their purpose to the user. When a button is unlabeled or lacks a clear accessible name, the screen reader can only identify it as "button," leaving the user unaware of its function.
In the current preview version of NAPS2 (8.0), I have encountered several unlabeled buttons, which makes the application less accessible to users relying on assistive technology. Ensuring that all interactive elements are provided with clear and descriptive labels would make the software far more accessible and inclusive.
To Reproduce
Steps to reproduce the behavior:
Download a Screen Reader like NVDA and run it.
Open Naps2 and use your keyboard to navigate trough the software.
You will find some unlabeled buttons.
Expected behavior
All buttons should be labeled.
Desktop
OS: Microsoft Windows 11 Home Version 24H2 (OS Build 26100.2894), x64
Version 8.0.2+60384a472ca1d9cfecd0f165008fb34712d6bb17
The text was updated successfully, but these errors were encountered:
Describe the bug
I am blind from birth and use a screen reader, JAWS, to navigate and interact with software. Screen readers work by translating the visual elements of an interface into audio or braille output. They identify components such as buttons, text fields, and other interactive elements and rely on accessible labels to convey their purpose to the user. When a button is unlabeled or lacks a clear accessible name, the screen reader can only identify it as "button," leaving the user unaware of its function.
In the current preview version of NAPS2 (8.0), I have encountered several unlabeled buttons, which makes the application less accessible to users relying on assistive technology. Ensuring that all interactive elements are provided with clear and descriptive labels would make the software far more accessible and inclusive.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
All buttons should be labeled.
Desktop
The text was updated successfully, but these errors were encountered: