290147 - down load manager text contents are not accessible.

Status: RESOLVED EXPIRED

(Core :: Disability Access APIs, defect)

Description

[chandrashekhar. korlahalli]

User-Agent:       Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 5.0)
Build Identifier: Mozilla 1.7 for Java Desk  top system.

Case 1:
Down load manager window  text  contents are not accessible.

Case 2:

Screen reader could not read the text content of the " file already exist, do 
you want to save ? " alert dialog.

Reproducible: Always

Steps to Reproduce:
1.Install gnome 2.6 on linux ( suse ) version 9.
2.Start gnopernicus, requires logout & loginn. Re-start gnopernicus & wait till 
you hear the  speech.
3. start mozilla web browser, from main menu.
4. Enjter proxy authentication values. enter known url. such as " www.sum.com ".
 or " www.yahoo.com ". The yahoo web page will open.
5. Select  " save page As  " from file  menu. Save as window dialog opens.
6. Give some valin file name. ex: yahoo_cbk. Press save push  button. Down 
load  manager window opens.

Actual Results:  
Case 1:
After selecting save page as, down load manager window opens. The text content 
of the down load manager is not accessible. The screen reader reads only title 
bar as " down load manager ". Screen reader dependent user will not know what 
is nexdt or what is happening.

Case 2:
In save page as window, give the already existing file name. alert dialog pops 
up.  The alert dialog text contents are not accessible. Screen reader reads 
only   title bar  as " alert ".

Expected Results:  
Case 1:
The screen  reader should read the down load status & its text content. Such as 
down loaded file with its details.

Case 2:
Alert dialog text  contents should be read by the screen reader.

It helps blind / low vision user. Other wise he gets stuck & he will not know  
what operation to be performed

Comment 1

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 2

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.