Jonathan Williams Reporter
	Description • 10 years ago

User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; InfoPath.3; .NET4.0C; .NET4.0E)

Steps to reproduce:


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)." 




Actual results:

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. 

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. 

Issue 3: 

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

Issue 4: 

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



Expected results:

Issue 1:
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”. 

Issue 2:
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. 

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

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

	:Gijs (he/him)
	Comment 1 • 10 years ago

David, I thought that toolbarbuttons in the toolbar were not /meant/ to be keyboard-focusable?

	David Bolter [:davidb] (NeedInfo me for attention)
	Comment 2 • 10 years ago

Hi I emailed Marco earlier about this support request. I'll pass the needinfo along to him for now to avoid duplicate effort.

	Marco Zehe (:MarcoZ)
	Comment 3 • 10 years ago

This is clearly specified as not accessible in our Voluntary Product Accessibility Template document which is still fully valid for Firefox 24 ESR, even though the version currently says Firefox 3.6 on it. We don't have a rapid-releasified version of the VPAT yet, but work is being done to address this. The current version of the VPAT which clearly specifies that the customziation of toolbars is not supported for screen reader users can be found here: http://www.mozilla.org/en-US/firefox/vpat-3.html