Last Comment Bug 346722 - JavaScript Alert Popup window message not read by default
: JavaScript Alert Popup window message not read by default
Status: RESOLVED INVALID
: access
Product: Core
Classification: Components
Component: Disability Access APIs (show other bugs)
: Trunk
: x86 Windows XP
: -- normal (vote)
: ---
Assigned To: Aaron Leventhal
:
Mentors:
: 346708 (view as bug list)
Depends on:
Blocks: xula11y keya11y
  Show dependency treegraph
 
Reported: 2006-07-31 12:25 PDT by Wayne DeAngelo
Modified: 2007-09-12 18:17 PDT (History)
7 users (show)
See Also:
Crash Signature:
(edit)
QA Whiteboard:
Iteration: ---
Points: ---
Has Regression Range: ---
Has STR: ---


Attachments
testcase (70.28 KB, text/html)
2006-07-31 12:28 PDT, Wayne DeAngelo
no flags Details
Much simpler testcase (86 bytes, text/html)
2007-06-11 13:07 PDT, Aaron Leventhal
no flags Details

Description Wayne DeAngelo 2006-07-31 12:25:09 PDT
Env: Windows XP, Bon Echo nightly build 20060731, and JAWS 7.1.

Problem: When running FF2 with the javascript alert (see attached file)the contents of the popup is not read by JAWS.

Steps to recreate:

1. Download the attached file, start JAWS and FF2.
2. Ins + down arrow till you get the the example heading of "Javascript Popup current Time"
3.Tab to the button "Display the Current Time" button.
4. JAWS announces only the title of the Popup window which is "Javascript Application" and stops there. It should read the information inside the window which is "The current time is ...."

Expected results: FF2 & JAWS should read the string within the Popup window.
Comment 1 Wayne DeAngelo 2006-07-31 12:28:30 PDT
Created attachment 231455 [details]
testcase
Comment 2 Ryan Jones 2006-07-31 12:57:12 PDT
*** Bug 346708 has been marked as a duplicate of this bug. ***
Comment 3 Mark Pilgrim (inactive) 2006-12-07 13:54:40 PST
Does this work with WindowEyes?  If so, file a bug against JAWS.
Comment 4 Aaron Leventhal 2007-06-11 13:07:59 PDT
Created attachment 268002 [details]
Much simpler testcase

Indeed this is only a problem with JAWS, but I will try to use describedby or some other way to get this spoken.
Comment 5 Aaron Leventhal 2007-06-11 18:05:44 PDT
I'm unable to work around this. JAWS should notice that it's ROLE_ALERT and read all the static text in the dialog.

Tim, can you take this one up with Freedom Scientific using the "Much simpler testcase" file. Once there's a bug filed there you can close this one as INVALID.
Comment 6 Tim Keenan 2007-06-12 09:40:21 PDT
I've filed it with them, but I'll keep this around until I hear from them.  
Comment 7 Aaron Leventhal 2007-09-12 13:17:15 PDT
This is working correctly in Window-Eyes but not in JAWS. Marco, can you make sure it is filed with Freedom Scientific?

Joanie, this is something to try in Orca.
Comment 8 Aaron Leventhal 2007-09-12 13:17:33 PDT
Not a Firefox bug.
Comment 9 Marco Zehe (:MarcoZ) on PTO until August 15 2007-09-12 14:11:11 PDT
Aaron, confirmed that JAWS does not read the text inside the Alert. However, in looking at the window with AccExplorer, I notice that there are actually three children, the first of which is an invisible text object, the second one is the text object containing the word "hello", the third one being the OK button. What's up with this invisible first child?
Comment 10 Aaron Leventhal 2007-09-12 18:17:45 PDT
The invisible child is made visible when there is a different kind of alert. JAWS should just skip over invisible objects. I don't think that's the issue, but I guess I could be wrong.

Note You need to log in before you can comment on or make changes to this bug.