"Elements from the “Customize Toolbar” list box cannot be added to toolbars using the keyboard alone.Įxpected Result: The “Customize Toolbar” list box is expected to be accessible and usable using the keyboard alone. This defect was previously identified on during testing of FireFox v17.0.6. "The contents of the “Customize Toolbar” list box are not available for JAWS v to read.Įxpected Result: The contents of the “Customize Toolbar” list box are expected to be made available for JAWS to read. When navigating between user interface elements using the keyboard, focus is expected to move directly to the next available element with each Tab press. When the user presses the Tab key again, focus next goes to the main Mozilla page thereby skipping the focus on the Downloads and Home buttons.Įxpected result: A well-defined on-screen indication of the current visual focus is expected to be provided at all times. As a result, focus skipped over the Reload button. When the user presses the Tab key again, the focus goes to the ""Search using Google"" input text field as the cursor is shown this text field. Also I want to highlight that we overlap two versions of the esrs before auto-updating folks to the next esr(24.2) to help pre-qualify the builds and help find any major issues in advance. For example, by tabbing to the ""Search or enter address"" input text box, the cursor appears thereby showing focus. Otherwise 24.2.0 is the next planned esr with a target release date of within next six weeks.
"Using the Tab key to navigate among different elements, note that the visual focus skips over certain elements. Reference: Section 508, Part 1194.21, Paragraph (d). "When specific combo boxes and list boxes are entered with JAWS v their labels are not made available for JAWS to read automatically when the element is accessed, or by using the JAWS virtual cursor.Įxpected Result: When a combo box or list box is entered with JAWS the label is expected to be made available for JAWS to read either automatically when the element is entered, or by using the JAWS “Virtual Cursor”. Are there plans in a future release to address these issues? If not, are there workarounds for users with disabilities? Details are below: To comply with federal government testing standards, my agency tested Firefox ESR 24.2.0 for 508 compliance.
0 kommentar(er)
