Closed Bug 2038203 Opened 6 months ago Closed 6 months ago

Navigation inside the search engine table does not work correctly with screenreader on

Categories

(Firefox :: Settings UI, defect)

Desktop
Windows
defect

Tracking

()

RESOLVED DUPLICATE of bug 2023928
Tracking Status
firefox152 --- affected

People

(Reporter: cbaica, Unassigned)

References

Details

(Keywords: access)

Affected versions

  • Fx 152.0a1

Affected platforms

  • Windows
  • Ubuntu

Preconditions

  • Turn on NVDA screenreader.
  • browser.settings-redesign.enabled set to true.

Steps to reproduce

  1. Launch Firefox and navigate to the about:preferences#search page.
  2. Use 'tab' to navigate to the 'Additional search engines' table.
  3. Use the arrow keys to navigate inside the table.

Expected result

  • Keyboard navigation using arrows can be done without issues inside the search engine table, and each element is correctly read and highlighted.

Actual result

  • Keyboard arrow navigation is done without highlighting elements while screenreader is on.
  • Keyboard navigation using left/right arrow keys, forces the screenreader to read each letter of the engine name and shortcut inside the table.

Regression range

  • This is not a regression.

Additional notes

  • The screen reader does not read out the 6dots, edit or toggle buttons on mouse over. Though they are correctly read out when reached via keyboard.

Moving across to settings as they're dealing with the accessibility issues of the search table.

Component: Search → Settings UI

I can more quickly navigate the table using Ctrl + Arrow Right, Ctrl + Arrow Left, Arrow Up, and Arrow Down when NVDA is enabled but I don't know if that's the expected navigation behavior for this sort of list. I'm also seeing the issue where the drag handle (6 dots), edit button and toggle button are not being announced when using a mouse.

Adding the access keyword to get a more accurate severity rating from the a11y team

Keywords: access
Status: NEW → RESOLVED
Closed: 6 months ago
Duplicate of bug: 2023928
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.