Closed
Bug 290164
Opened 19 years ago
Closed 19 years ago
( A11y ) End of find text alert dialog text content is not accessible.
Categories
(Core :: Disability Access APIs, defect)
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. Case 1: End of find text alert dialog text content is not accessible. Case 2: Already with this file name file exist. Do you want save on it? Alert dialog text contents are not accessible. 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. select edit > find menu item> find text dialog opens. 5. Enter required text in find edit text box. press find push button. keep pressing find push button till end. Actual Results: Case 1: Find alert dialog box pops up. screen reader does not read the dialog text content. It reads only title bar as " alert ". It is didfficult for the blind / low vision user to make out. with out accessibility support. Case 2: Save the web page with the existin file name. Thus alert dialog pops up. Screen reader dois not read the alert dialog text content. It reads only title bar as " alert ". Expected Results: Alert dialog box text content should be read by the screen reader in both cases. Without ATK support blind / low vision users gets stuck.
Reporter | ||
Comment 1•19 years ago
|
||
Case 3; Fill in form alert dialog box text contents are not accessible.
Assignee: general → Louie.Zhao
Component: General → Disability Access APIs
Product: Mozilla Application Suite → Core
Version: unspecified → 1.7 Branch
Comment 2•19 years ago
|
||
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 3•19 years ago
|
||
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.
Description
•