Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Hierdie gesprek is in die argief. Vra asseblief 'n nuwe vraag as jy hulp nodig het.

Firefox ESR 24 is not 508 Compliant

  • 2 antwoorde
  • 2 hierdie probleem
  • 13 views
  • Laaste antwoord deur MarcoZ

more options

To comply with federal government testing standards, my agency tested Firefox ESR 24.2.0 for 508 compliance. It failed. Are there plans in a future release to address these issues? If not, are there workarounds for users with disabilities? Details are below:

Issue 1:

"When specific combo boxes and list boxes are entered with JAWS v15.0.4203 their labels are not made available for JAWS to read automatically when the element is accessed, or by using the JAWS virtual cursor.

Expected 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”.

Reference:  Section 508, Part 1194.21, Paragraph (d).

This defect was previously identified on 6/3/2013 during testing of FireFox v17.0.6. (see TPR 4436)"

Issue 2:

"Using the Tab key to navigate among different elements, note that the visual focus skips over certain elements.  For example, by tabbing to the ""Search or enter address"" input text box, the cursor appears thereby showing focus.  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. As a result, focus skipped over the Reload button.

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.

Expected result: A well-defined on-screen indication of the current visual focus is expected to be provided at all times. When navigating between user interface elements using the keyboard, focus is expected to move directly to the next available element with each Tab press.

Reference: Section 508, Part 1194.21, Paragraph (c)."

Issue 3:

"The contents of the “Customize Toolbar” list box are not available for JAWS v15.0.4203 to read.

Expected Result: The contents of the “Customize Toolbar” list box are expected to be made available for JAWS to read.

Reference:  Section 508, Part 1194.21, Paragraph (d).

This defect was previously identified on 6/03/2013 during testing of FireFox v17.0.6. (see TPR 4438)"

Issue 4:

"Elements from the “Customize Toolbar” list box cannot be added to toolbars using the keyboard alone. 

Expected Result: The “Customize Toolbar” list box is expected to be accessible and usable using the keyboard alone.

Reference:  Section 508, Part 1194.21, Paragraph (a)."

To comply with federal government testing standards, my agency tested Firefox ESR 24.2.0 for 508 compliance. It failed. Are there plans in a future release to address these issues? If not, are there workarounds for users with disabilities? Details are below: Issue 1: "When specific combo boxes and list boxes are entered with JAWS v15.0.4203 their labels are not made available for JAWS to read automatically when the element is accessed, or by using the JAWS virtual cursor. Expected 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”. Reference:  Section 508, Part 1194.21, Paragraph (d). This defect was previously identified on 6/3/2013 during testing of FireFox v17.0.6. (see TPR 4436)" Issue 2: "Using the Tab key to navigate among different elements, note that the visual focus skips over certain elements.  For example, by tabbing to the ""Search or enter address"" input text box, the cursor appears thereby showing focus.  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. As a result, focus skipped over the Reload button. 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. Expected result: A well-defined on-screen indication of the current visual focus is expected to be provided at all times. When navigating between user interface elements using the keyboard, focus is expected to move directly to the next available element with each Tab press. Reference: Section 508, Part 1194.21, Paragraph (c)." Issue 3: "The contents of the “Customize Toolbar” list box are not available for JAWS v15.0.4203 to read. Expected Result: The contents of the “Customize Toolbar” list box are expected to be made available for JAWS to read. Reference:  Section 508, Part 1194.21, Paragraph (d). This defect was previously identified on 6/03/2013 during testing of FireFox v17.0.6. (see TPR 4438)" Issue 4: "Elements from the “Customize Toolbar” list box cannot be added to toolbars using the keyboard alone.  Expected Result: The “Customize Toolbar” list box is expected to be accessible and usable using the keyboard alone. Reference:  Section 508, Part 1194.21, Paragraph (a)."

Gekose oplossing

hello williamsjon, this forum is primarily run by volunteers so we cannot provide you with any plans of future development. since it is quite a specialised question you might be getting a better answer when you post your request to the accessibility mailing list or open a new bug for it at bugzilla.mozilla.org

https://wiki.mozilla.org/Accessibility/Contribute#Get_Help

Lees dié antwoord in konteks 👍 0

All Replies (2)

more options

Gekose oplossing

hello williamsjon, this forum is primarily run by volunteers so we cannot provide you with any plans of future development. since it is quite a specialised question you might be getting a better answer when you post your request to the accessibility mailing list or open a new bug for it at bugzilla.mozilla.org

https://wiki.mozilla.org/Accessibility/Contribute#Get_Help

more options

As stated in our VPAT for firefox 3.6, this particular dialog isn't accessible. Unfortunately, this situation hasn't changed until today, so this statement from the VPAT is still valid. We're currently working on updating our VPAT so it keeps up with current releases, but statements given in this VPAT are so far all still valid.