Closed Bug 290031 Opened 20 years ago Closed 19 years ago

A11y proxy login prompt from mozilla is not accessible.

Categories

(Core :: Disability Access APIs, defect)

1.7 Branch
x86
Linux
defect
Not set
normal

Tracking

()

RESOLVED EXPIRED

People

(Reporter: chandrashekhar.korlahalli, Assigned: Louie.Zhao)

References

Details

User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 5.0) Build Identifier: Mozilla 1.7 for Java Desk top system. Mozilla login dialog prompt text contents are not accessible. ------------------------------------------------------------- Steps to reproduce: 1. Install gnome 2.6 on suse linux version 9. 2. start gnopernicus, requires logout & login. Re-start the gnopernicus & wait till you hear the speech. 3. start mozilla web browser > a dialog prompt opens for proxy information. Expected: Prompt dialog contents such as " enter user name & password " should be read by the screen reader. It helps blind / low vision users. Reproducible: Always Steps to Reproduce: 1 Install gnome 2.6 on suse linux version 9. 2. start gnopernicus, requires logout & login. Re-start the gnopernicus & wait till you hear the speech. 3. start mozilla web browser > a dialog prompt opens for login. Actual Results: Observation: Screen reader reads only title bar content as " prompt " but does read the contents of the dialog. It is difficult for the blind / low vision user to know that the prompt is for what? & he will not be knowing what is next action to be performed. Expected Results: Prompt dialog contents such as " enter user name & password " should be read by the screen reader. It helps blind / low vision users.
Related to Gnopernicus meta bug 163832?
Assignee: general → Louie.Zhao
Component: General → Disability Access APIs
Product: Mozilla Application Suite → Core
Version: unspecified → 1.7 Branch
Blocks: gnoper
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/
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.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.