Closed Bug 908358 Opened 12 years ago Closed 5 years ago

Save As dialog not completely read by screen reader (JAWS)

Categories

(Firefox :: Disability Access, defect)

23 Branch
x86_64
Windows 7
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: benjamin_gold, Unassigned)

References

(Blocks 1 open bug)

Details

Attachments

(1 file)

Static text on the Save As dialog is not read by JAWS.
Steps to reproduce: 1) Launch screen reader (JAWS 14) 2) Launch Firefox 3) Change the preference on the "General" tab, in the Downloads section, to "Always ask me where to save files" 4) Navigate to a web page to download a file 5) Click on the link/button/action to download the file Problem: The static text at the top of the dialog is not read by the screen reader. The screen reader reads the title of the file then reads, "What should Firefox do with this file?". It does not read, "You have chosen to open:", the name of the file, "which is: <file type>", and "from: <url>".
Attached image ff_download_dialog.png
Example File Save As dialog
Depends on: jaws
Blocks: jaws
No longer depends on: jaws
Marco, can you confirm this?
this should be fixed by a recent round of XUL markup improvements that are in Firefox 29 Aurora. Ben, can you re-test this please?
I have to download FF 29 Aurora, if I get a chance to do that I'll re-test.
This dialog still does not appear to be accessible. JAWS still skips the entire top section when opening the dialog (where the dialog states, "You have chosen to open", the file name, what type of file it is, and where it was downloaded from). The first thing JAWS reads for me is the title of the dialog, "Opening <filename>", then, "What should Aurora do with this file?". If I wasn't sighted, I would have never known that I missed content in the first place. If I tab multiple times I can eventually wrap around to the read-only text that is the file type, but even then I can never seem to get to the "from: " field.
I've got more feedback: "There are a number of label elements below the dialog but they are not related to the dialog. If you use the jaws keystroke (insert+b) JAWS will read the static text in the dialog. So the question is, should there be a labelledby relation from the dialog to the labels? I don't really know. Otherwise, JAWS is working as designed, the names of ancestors of the focused elements are read when focus moves into the dialog."

This is working now. All of the dialog text (including the bits reported as missing here) are exposed in the dialog's accDescription. I tested with JAWS 2019 and all of the text was read.

Status: UNCONFIRMED → RESOLVED
Closed: 5 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: