为提升您的使用体验,本站正在维护,部分功能暂时无法使用。如果本站文章无法解决您的问题,您想要向社区提问的话,请到 Twitter 上的 @FirefoxSupport 或 Reddit 上的 /r/firefox 提问,我们的支持社区将会很快回复您的疑问。

搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

Firefox ESR 24 is not 508 Compliant

  • 2 个回答
  • 2 人有此问题
  • 4 次查看
  • 最后回复者为 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)."

被采纳的解决方案

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

定位到答案原位置 👍 0

所有回复 (2)

more options

选择的解决方案

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.