Open Bug 1899519 Opened 9 months ago Updated 8 months ago

Ubuntu Screenreader fails to read the "Cancel" button

Categories

(Firefox :: Screenshots, defect, P3)

Firefox 127
Desktop
Linux
defect

Tracking

()

Accessibility Severity s2
Tracking Status
firefox-esr115 --- unaffected
firefox126 --- unaffected
firefox127 --- affected
firefox128 --- affected

People

(Reporter: sbadau, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: access)

Attachments

(1 file)

Found in

  • Firefox 127.0b7

Affected versions

  • Firefox 127.0b7
  • Nightly 128.0a1

Tested platforms

  • Affected platforms: Ubuntu 23.10, Ubuntu 22.04
  • Unaffected platforms: Windows 10, macOS 13

Preconditions

  • Enable the Ubuntu integrated Screenreader

Steps to reproduce

  1. Navigate to any webpage.
  2. Enable Screenshots (Ctrl+Shift+S)
  3. Press the Tab key to reach the Cancel button.

Expected result

  • The Cancel button should be reached and read by the OS'es screenreader.

Actual result

  • The screenreader reads "Tab" instead of recognizing the Cancel button when it is reached.

Regression range

  • Not a regresssion.

Any idea what's going on here? Do you have time to take a look? This feels like a platform bug to me, instead of a screenshots-frontend one

Flags: needinfo?(eitan)
Accessibility Severity: --- → s2

Works for me. I did notice two issues:

  1. In MacOS VoiceOver reads the page title when the button is focused. If the title is long you have to hear everything before you hear "cancel button".
  2. In all platforms actually pressing space or enter does nothing in the cancel button.
Flags: needinfo?(eitan)

The severity field for this bug is set to S3. However, the accessibility severity is higher, .
:sfoster, could you consider increasing the severity?

For more information, please visit BugBot documentation.

Flags: needinfo?(sfoster)

I'm not sure how to reproduce this with Ubuntu's screen reader. I'm not getting much of anything in the browser when I enable it. It doesnt appear to read focused buttons or notify when I switch between browser windows. Is there some pref to flip or other thing I need to do to reproduce and get this screen reader working in Firefox?

Flags: needinfo?(sfoster) → needinfo?(sbadau)

(In reply to Sam Foster [:sfoster] (he/him) from comment #4)

I'm not sure how to reproduce this with Ubuntu's screen reader. I'm not getting much of anything in the browser when I enable it. It doesnt appear to read focused buttons or notify when I switch between browser windows. Is there some pref to flip or other thing I need to do to reproduce and get this screen reader working in Firefox?

I don't do any preference flipping, but I make sure to turn ON the Screenreader before opening Firefox, or I restart Firefox after enabling the Screenreader.

I just checked the issue again on Ubuntu 22.04. This time, the Cancel button was read the first time I opened the Screenshot tool but stopped being read after a Firefox restart. Here is a screen recording with audio of the steps I used: https://drive.google.com/file/d/1-BTW3TgCR_SeORPhjdJPscLvRV3Z9jhJ/view?usp=sharing

STR:

  1. Enable the Screenreader.
  2. Open Firefox.
  3. Enable the Screenshot tool (Ctrl+Shift+S) and navigate with the Tab key.
  4. Restart Firefox from the keyboard using Ctrl+Shift+J and then Ctrl+Alt+R.
  5. Enable the Screenshot tool again and navigate using the Tab key.
Flags: needinfo?(sbadau)

This is the first time I've run into bugs filed for behavior when using the Ubuntu Screenreader. Is that assistive tech we normally support? From the fact this works as expected in the other screen readers, and the steps in comment 5 it sounds like its more likely to be a platform bug or even a bug in the reader itself. Can you help us triage this Morgan?

Flags: needinfo?(mreschenberg)

I'm fixing the a11y activation issue in bug 1900668. Running into memory leaks so didn't land yet. Once it does, you should expect orca to work with a pre-running session of Firefox.

(In reply to Sam Foster [:sfoster] (he/him) from comment #6)

This is the first time I've run into bugs filed for behavior when using the Ubuntu Screenreader. Is that assistive tech we normally support? From the fact this works as expected in the other screen readers, and the steps in comment 5 it sounds like its more likely to be a platform bug or even a bug in the reader itself. Can you help us triage this Morgan?

Yes, we support screen readers on all desktop platforms. Our primary supported screen readers are: Orca on Linux, VoiceOver on macOS, and NVDA on Windows.

I initially thought this was a platform bug, since the reporter noted this was specific to Linux. However, in Eitan's testing in #c2 it seems like the Cancel button was inoperable across platforms. Is that still the case?

It sounds like there are two issues here: Orca doesn't consistenly read things in FF if FF was started before Orca, and the cancel button in screenshots is inconsistently (or unable to be) activated with screen readers across platforms. While Eitan works on the former, we should try to figure out if the latter is a platform issue or a frontend one.

:simona, have you tested that the Cancel button can be operated with VoiceOver on macOS or NVDA on Windows? what about with Orca, when Orca is able to read it?

Flags: needinfo?(mreschenberg) → needinfo?(sbadau)

(In reply to Morgan Reschenberg [:morgan] from comment #8)

:simona, have you tested that the Cancel button can be operated with VoiceOver on macOS or NVDA on Windows? what about with Orca, when Orca is able to read it?

Yes, I have tested the Cancel button with screen readers on both macOS and Windows. However, I observed the following behaviors, which I am unsure are intended:

On macOS with Voiceover - the Cancel button is accessible, but it is grouped separately from the 'Save visible' and 'Save full page' options.
On a blank page, reaching the Cancel button is straightforward. However, on a more complex page, I have to navigate through all the elements of the page to reach the "Drag or click..." text and the Cancel button, which are the last elements in the navigation order.

On Windows 10 with NVDA - the Cancel button can be reached using the Tab key and operated using the Space or Enter keys.
However, when focusing on the button, NVDA first reads the title of the tab before announcing the Cancel button.

Flags: needinfo?(sbadau) → needinfo?(mreschenberg)

(In reply to Morgan Reschenberg [:morgan] from comment #8)

I initially thought this was a platform bug, since the reporter noted this was specific to Linux. However, in Eitan's testing in #c2 it seems like the Cancel button was inoperable across platforms. Is that still the case?

I have since fixed the issue with the cancel button not working. see bug 1899801

Priority: -- → P3
Flags: needinfo?(mreschenberg)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: