1229622 - [Jaws] input with type file can not read the file name after open a file

Status: RESOLVED DUPLICATE of bug 782547

(Firefox :: Disability Access, defect)

Description

[hydrogenbear]

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/46.0.2490.80 Safari/537.36

Steps to reproduce:

In http://website-archive.mozilla.org/www.mozilla.org/access/access/qa/win-webcontent-jaws.html#html-forms, press space on input#fileinput, select a file and press enter. 


Actual results:

Jaws speak out the title of the browser and then nothing.


Expected results:

In IE and Chrome, Jaws speak out the name of the selected file and the aria info of the input element.

Comment 1

[Gingerbread Man]

What version of JAWS are you using?

You filed this for Firefox ESR, which only gets security patches until its next major version. Can you reproduce the issue with the current release of Firefox in a brand new profile?
https://support.mozilla.org/kb/profile-manager-create-and-remove-firefox-profiles
https://www.mozilla.org/firefox/all/

Comment 2

[:Gijs (he/him)]

Marco, can you reproduce this with JAWS, and is it any better with NVDA (ie do we know whose "fault" this is :-) )?

Comment 3

[Marco Zehe (:MarcoZ)]

(In reply to :Gijs Kruitbosch from comment #2)
> Marco, can you reproduce this with JAWS, and is it any better with NVDA (ie
> do we know whose "fault" this is :-) )?
This is definitely not a problem with NVDA. After completing a FileOpen dialog successfully, NVDA's virtual buffer reflects the file name before the Browse... button. And we even have a test for this AFAIK, so if something broke, our mochitests would catch it. My JAWS is a bit out of date, but the version I have didn't reproduce it when I just tested it quickly, either. So it would definitely be good to know, as Gingerbread Man requested, that the JAWS version be stated and we're told if this is still an issue with current Firefox versions. Basically anything below JAWS 15 is bound to have errors that stem from insufficient Firefox support.

Comment 4

[hydrogenbear]

I have tested that on Firefox 42.0 and JAWS 16.0.4350 again. I can still reproduce that problem.

After I press enter in the FileOpen dialog, the JAWS says "Testing web content with JAWS screen reader Mozilla Firefox" and nothing more.

I carefully did the test again. 
On Chrome 46.0.2490.80 m, JAWS says "Choose file button".
On IE 8.0.7501.17514, JAWS says "Testing web content with JAWS screen reader - Windows Internet Explorer Specify file name: Browse...".

Sorry for no file name was spoken out in your test case. That only happens in our own product. Although I can not figure out the difference between the Mozilla's test case and mine (on the usage of the input element).

Comment 5

[James Teh [:Jamie]]

If I'm not mistaken, I think Marco might have misunderstood the reporter's issue. The buffer does indeed reflect the updated file name. However, when you return from the Browse dialog, you just hear the title of the browser, not the currently focused document or button.

I believe this is a duplicate of bug 782547.

Comment 6

[Marco Zehe (:MarcoZ)]

Yes, in light of this updated report, Jamie's analysis is correct.