Sakai 2.3 Test Protocol--Firefox Accessibility Extension only

Here is the protocol for testing Sakai accessibility using Firefox and the Firefox Accessibility Extension. It is one of three accessibility test protocols for Sakai; another is a test that uses WAVE 3.5 and the third is a test using the JAWS screen reader. A template and a completed form for reference are contained in Attachments.

Background. This is a protocol for testing Sakai accessibility and, to a limited degree, functionality, using a PC (minor differences when using a Mac are in parenthesis) and the Firefox Accessibility Extension. It is anticipated that the next version of Sakai will be tested for adherence to WCAG 2.0 criteria, however, at this time evaluation tools are not available that can effectively test password protected, iFrame applications.

Tools. Two tools will be used: Firefox 2.0x and the Mozilla Accessibility Extension (installed on Firefox).

Results should be entered into a spreadsheet (see Attachments on the Test Template page), to facilitate developer repair and subsequent QA.

Methodology. The following sequence is recommended:

1. Add Firefox 2.0x as a browser (http://www.mozilla.com/firefox/)
2. Add the Mozilla/Firefox Accessibility Extension to your copy of Firefox (http://cita.disability.uiuc.edu/software/mozilla/). Note: You must first remove the Developer toolbar if you have it installed, or Firefox may crash. You can reinstall it after adding the Accessibility Extension.
3. Open the Sakai Collab site in Firefox: http://collab.sakaiproject.org
4. Login using your name/password combination for Sakai.
5. Go to the "WG:Accessibility" worksite in the tabs. Your assigned tool will be listed as one of the tools.
6. Click on your tool and the first page will appear.
7. Go to the Accessibility Extension toolbar, click on the Navigation icon and select "Links." Check for 1) redundant link names, and 2) meaningful link text. There should be no redundant links and links should have text that is self-explanatory. Move your cursor over links to see if additional information has been added to improve context through the use of the <title> attribute. Write your findings in the spreadsheet under "Links."
8. Go back to the Accessibility Extension tool bar, click on the Navigation icon, and select "Headers." Check for: 1) meaningful heading labels, 2) an accurate hierarchy (h1, h2, h3, etc.), and 3) a thorough use of headings. Write your findings in the spreadsheet under "Headings." (Mac: Select "Major/Minor Topics," rather than "Headers.")
9. Go back to the Accessibility Extension tool bar, click on the Navigation icon, and select "Accesskeys." Check that accesskeys are 1) present, and 2) unique. (Mac: Use the ctrl key rather than the option key to test accesskeys.) These are the accesskeys currently contained in Sakai:

Application-wide:
Alt + c = Skip to content
Alt + l = Beginning of Tools list (the letter "l")
Alt + w = Beginning of Worksite tabs
Alt + 0 = Accessibility page
Alt + 6 = Portal help page

Tool-specific:
Alt + e = Edit or Revise
Alt + h = Tool help page
Alt + s = Save
Alt + u = Manual refresh
Alt + v = View or Preview
Alt + x = Remove, delete or cancel

Write your findings in the spreadsheet under "Accesskeys."
10. Go back to the Accessibility Extension tool bar, click on the Navigation icon, and select "Frames." Check that frame titles are 1) unique and meaningful. Write your findings in the spreadsheet under "Frame Titles."
11. Go back to the Accessibility Extension tool bar, click on the Style icon, and select "Disable CSS." Click on the Images icon and select "Replace with Alt Text." (Mac: Choose "Text Equivalents" rather than the Images icon, and select "Show ALT text.") Check that 1) the page is readable, and 2) reading order makes sense. Write your findings in the spreadsheet under "Stylesheets/Linearization."
12. Go back to the Accessibility Extension tool bar and press "Zoom In" four times. Check that 1) text remains readable, and 2) that areas of the application do not overlap. Write your findings in the spreadsheet under "Zoom Text."
13. Press "Zoom Out" four times to restore page to normal size. Press the refresh button to restore page appearance.
14. Go back to the browser, and tab through the application. A dotted box will show you the focal point. As you tab through the application, check for the following: 1) tabbing moves in a logical fashion, 2) key items receive focus, and 3) tabbing does not trigger page actions. Write your findings in the spreadsheet under "Tab Order."
15. Move through the application using your browser and arrow keys. Make sure that you can access all text boxes, form inputs, and functions on the page. Write your findings in the spreadsheet under "Functionality".
16. Go to the next page of your tool.
17. Repeat steps 8 through 16 for each page of your assigned tool.
20. Save your review in the 2.4 Accessibility Test attachments section of confluence using a description such as "Wiki_2.4_Firefox_Review".