347222 - Accessibility issues on Options-Privacy page

Status: RESOLVED DUPLICATE of bug 344572

(Firefox :: Disability Access, defect)

Description

[Wayne DeAngelo]

Test environment:
   Windows XP, Firefox 2 (Bon Echo) build 20060802, Inspect Objects
   Optional: screen reader (JAWS or Window-Eyes)

Description: 
Accessibility issues found on the "Privacy" tab of the Tools-Options dialog.
1. Missing MSAA Name in "Remember visited pages fo the last" text input field
2. Screen reader does not read sentences containing multiple user interface elements.

Steps to recreate:
1. Open Tools-Options dialog (press Alt+T, then "O")
2. Select the "Privacy" page  (Press Tab or Shift+Tab until focus is on one of the icons at the top of the page, then press Right Arrow or Left Arrow until "Privacy" is selected.)
3. Press Tab to move focus to the "Remember visited pages for the last" field in the History section.
4. Press Tab one more time to focus on the input box for number of days. 
5. Note the Inspect Objects output: The MSAA Name = "" (null).  It should contain a meaningful label.
6. When you Tab to the "Remember visited" checkbox, or to the text entry field, note that the screen reader  never reads the entire sentence.  (JAWS and Window-Eyes output differ slightly, but neither ever says the word "days".  

Note: Visual constructions like this (radio button, followed by another UI element like a input field or combo box), followed by more text are not very easy to understand when using a screen reader, since the screen reader often reads only one element at a time, and not the entire line, as a sighted user would naturally do.

Expected results:
1. The MSAA Name property should be set for all User Interface elements.
2. The "Remember visited pages..." option should be reworded so as not to depend on a visual sentence structure containing multiple UI elements.  A possible solution is to make the MSAA Name of the input field something like: Name="Number of days to remember".

Comment 1

[Jeff Walden [:Waldo]]

This should be fixed by bug 344572; is it?  You'll need to either use the next nightly or a tinderbox build to check.

Comment 2

[Mark Pilgrim (inactive)]

*** This bug has been marked as a duplicate of 344572 ***

Comment 3

[Firefox Bug Husbandry Bot]

https://bugzilla.mozilla.org/show_bug.cgi?id=1527381