Summary
Since the application was rewritten using the Qt framework (version 3.x), it has become completely inaccessible for blind and visually impaired users who rely on screen reading software. This is a severe regression, as previous versions (2.x) were fully accessible and worked perfectly.
Description of the Problem
In the latest versions, standard keyboard navigation is broken, making it impossible to use the application without a mouse.
When the app is launched, the only UI element that can be focused with a keyboard is the URL input field. The keyboard focus then becomes "trapped" in this field. Pressing the Tab key or Shift+Tab—standard keys for navigating between UI controls in Windows—does not move the focus. Instead, it incorrectly inserts a tab character into the input field.
As a result, users who rely on screen readers and keyboard navigation cannot access any buttons, menus, or other controls, rendering the application unusable.
Steps to Reproduce
To demonstrate the regression, you can compare the behavior of an old version with the current one.
1.
Start a screen reader. The built-in Windows Narrator can be used, or NonVisual Desktop Access (NVDA), which is a widely used free screen reader available at nvaccess.org.
2.
Test the previous, accessible version:
•
Launch an older version of the app (e.g., 2.8.0.0).
•
If an update prompt appears, dismiss it.
•
Use the Tab and Shift+Tab keys to navigate.
•
Result: You will notice that all controls are focusable and are correctly announced by the screen reader.
3.
Test the current, inaccessible version:
•
Launch the latest version of the app (e.g., 3.0.4.43 as of this writing).
•
Attempt to navigate with Tab and Shift+Tab.
•
Result: You will notice it's impossible to move focus away from the initial URL input field.
Expected Behavior
Users should be able to navigate between all interactive UI elements (buttons, input fields, lists, etc.) using the Tab and Shift+Tab keys. All controls should be properly labeled so they can be identified and announced by screen reading software.
Actual Behavior
Only the URL input field is focusable. Keyboard focus is trapped, and no other UI elements can be reached. The application is completely unusable for anyone who relies on a screen reader.
Additional Context
I am not a developer, but I understand this issue likely stems from the migration to Qt. The Qt framework (especially Qt6) has robust accessibility APIs and documentation available to resolve these kinds of issues.
It would be wonderful if you could restore accessibility to the application. If you decide to work on this, I would be happy to provide further feedback or help test any potential fixes.
Thanks in advance for your consideration.
Summary
Since the application was rewritten using the Qt framework (version 3.x), it has become completely inaccessible for blind and visually impaired users who rely on screen reading software. This is a severe regression, as previous versions (2.x) were fully accessible and worked perfectly.
Description of the Problem
In the latest versions, standard keyboard navigation is broken, making it impossible to use the application without a mouse.
When the app is launched, the only UI element that can be focused with a keyboard is the URL input field. The keyboard focus then becomes "trapped" in this field. Pressing the Tab key or Shift+Tab—standard keys for navigating between UI controls in Windows—does not move the focus. Instead, it incorrectly inserts a tab character into the input field.
As a result, users who rely on screen readers and keyboard navigation cannot access any buttons, menus, or other controls, rendering the application unusable.
Steps to Reproduce
To demonstrate the regression, you can compare the behavior of an old version with the current one.
1.
Start a screen reader. The built-in Windows Narrator can be used, or NonVisual Desktop Access (NVDA), which is a widely used free screen reader available at nvaccess.org.
2.
Test the previous, accessible version:
•
Launch an older version of the app (e.g., 2.8.0.0).
•
If an update prompt appears, dismiss it.
•
Use the Tab and Shift+Tab keys to navigate.
•
Result: You will notice that all controls are focusable and are correctly announced by the screen reader.
3.
Test the current, inaccessible version:
•
Launch the latest version of the app (e.g., 3.0.4.43 as of this writing).
•
Attempt to navigate with Tab and Shift+Tab.
•
Result: You will notice it's impossible to move focus away from the initial URL input field.
Expected Behavior
Users should be able to navigate between all interactive UI elements (buttons, input fields, lists, etc.) using the Tab and Shift+Tab keys. All controls should be properly labeled so they can be identified and announced by screen reading software.
Actual Behavior
Only the URL input field is focusable. Keyboard focus is trapped, and no other UI elements can be reached. The application is completely unusable for anyone who relies on a screen reader.
Additional Context
I am not a developer, but I understand this issue likely stems from the migration to Qt. The Qt framework (especially Qt6) has robust accessibility APIs and documentation available to resolve these kinds of issues.
It would be wonderful if you could restore accessibility to the application. If you decide to work on this, I would be happy to provide further feedback or help test any potential fixes.
Thanks in advance for your consideration.