Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3

Anchor
ComprehensiveReview
ComprehensiveReview

Comprehensive Accessibility Review Protocol for PC


This is the protocol for more in-depth accessibility testing. It contains three accessibility test protocols for Fluid: Internet Explorer 7 with the AIS Toolbar Extension, the JAWS Screen Reader and the Web Accessibility Checker tool. A form for entering results and a completed form for reference are contained in Attachments.

...

This is a combination protocol for testing Sakai accessibility and, to a limited degree, functionality, using a PC (a . A parallel review for evaluating accessibility with a Mac can be found in the Mac Accessibility Protocol using the Firefox browser and the Firefox Accessibility Extension). In particular, this protocol will enable you to evaluate Fluid components and tools for: compliance with WCAG 2.0 Priority Two, accessibility-related functionality, and usability with the JAWS screen reader.

There are four three steps: 

...

...

...

...

...

...

Anchor
Setup
Setup

Tools

Four tools will be used: Internet Explorer 7.0, the AIS Toolbar Extension (installed on Internet Explorer), the Web Accessibility Checker tool from University of Toronto, and the demo for JAWS.

...

This is to review accessibility using a PC. Nearly all persons with disabilities use the PC format with Internet Explorer because of widespread adoption of the MSAA protocol developed by Microsoft. If you want to review accessibility using a Macintosh, see this parallel protocol for macs, but note: JAWS and Window-Eyes are available only for the PC, so you will have to either use a plug-in for Firefox (Fangs) to simulate JAWS output or use a PC.

...

This is a manual review of the usability and accessibility of the page using the JAWS screen reader. Specific keystroke combinations using JAWS commands are shown in parentheses. There are five essential questions that we want to answer when reviewing a tool with JAWS:

  • Does the page provide the user with a clear understanding of its purpose?
  • Does the page enable the user to accomplish his/her objectives?
  • Can the user move logically and easily within the page?
  • Is the page fully functional?
  • Is content relevant, clear and concise?

We can answer those questions by listening to JAWS as we use the navigation methods frequently used by JAWS users:

  1. Open JAWS
  2. Open your browser and type in the address you want to check
  3. Experience the page using JAWS:
    • Listen to page (ins + down arrow)
      • Is all the content read?
    • Listen to page title (insert + t)
      • Does it describe page content?
    • Tab through links and form inputs (tab)
      • Are they read in an order that makes sense?
    • Scan through headings (h)
      • Does the page have headings?
      • Are the heading levels read?
      • If the page does not have headings, scan through page paragraphs (p)
    • Review link phrases (insert + f7)
      • Do the individual phrases make sense?
    • Review headings (insert +f6)
      • Do the individual headings make sense?
      • Does the hierarchy of headings make sense?
  4. Review page functionality
    • Links
      • Does each link work? (enter)
      • Does each link phrase match the destination page title?
    • Forms
      • Are form labels announced with input boxes or operations? (enter)
      • Do the forms work? Can items be entered and the form be submitted?
    • Tables
      • Are table captions and/or summaries read?
      • Are column and row headings read when moving between column or row cells? (down or up arrows)
      • Are column and row headings read for the current cell? (alt + control + numeric keypad number 5)
  5. Quit JAWS

...

Many issues requiring manual checks will have been addressed by Steps II 1 and III2.

  1. Load your first page (example: http://www.fsc.yorku.ca/fluid/moodle/). Copy the address, then save the page as a complete webpage into a file folder with a descriptive name (such as "Home Page").
  2. Open aChecker.
    • Click the "Browse" button for the Local File box at the top of the page. Choose your saved file. Press the "Check It" button.
    • Review results. Click "sort by accessibility guideline" if it is highlighted. Save as "Webpage, complete" with a descriptive title (such as "Report Summary - Home").
    • Click on each guideline listed and save the resulting page including the Guideline in the title (such as "1.1-Home.html"). At this point you may choose to review each issue and determine its status.
    • Write down the results.
    • Repeat for the pages you want to test.