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 accessibility and, to a limited degree, functionality, using a PC. 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 three steps: 


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.

Results should be entered into a spreadsheet (see Attachments) to facilitate developer repair and subsequent QA.

Set-up Computer for testing

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.

  1. Add Internet Explorer 7.0.
  2. Add the AIS Toolbar Beta 2.0. Note: You must first remove any earlier versions of the AIS toolbar before installing Beta 2.0. Also, if you prefer to use IE 6.0, you can add the prior version of AIS Toolbar.
  3. Add the demo for JAWS.
  4. Bookmark the address for the ATRC Web Accessibility Checker Tool (aka aChecker)(

Step 1: Evaluate Page for Appropriate Markup

This is a manual check for appropriate accessibility elements, and does not involve reviewing html or CSS code (which can be fairly technical). Code based review is presented in Step IV.

  1. Click on your tool and its first page will appear.
  2. Go to the AIS toolbar, click on the "Doc Info" icon and select "List Links."
  3. From within the "Doc Info" tool, select "Metadata Information."
  4. Go back to the AIS tool bar, click on the Structure icon, and select "Headings."
  5. Go back to the Accessibility Extension tool bar, click on the Frames icon, and select "Frame Name/Title"
  6. Go back to the AIS tool bar, click on the Tables icon and select "Linearize." Click on the CSS icon, and select "Disable CSS" and "Disable in-line styles." Click on the Images icon and select "Remove Images."
  7. Go to the lower right hand corner of Internet Explorer and change the page size to 400%.
  8. Press "Zoom Out" four times to restore page to normal size. Press the refresh button to restore page appearance.
  9. Go back to the AIS tool bar, click on the Color icon
  10. Go back to the browser, and tab through the application.
  11. Move through the application using your browser and arrow keys.

Step 2: Evaluate with JAWS

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:

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:
  4. Review page functionality
  5. Quit JAWS

Step 3: Validate Compliance with WCAG 2.0 Level 2 Guidelines

This is a review using the Web Accessibility Checker from the University of Toronto. Like other accessibility checkers, some issues can be identified automatically (as in the case of a missing <alt> description in an image file), in other cases, compliance must be ascertained by a manual check by looking at the page and underlying code (as in the case of whether an <alt> description is meaningful). Issues are identified as "Known," "Likely," and "Potential" problems, with the location and suspect code identified. If you are familiar with html you may want to review each issue as you encounter it. If you are going to hand off the results to someone else, you may want to save the issues as complete web pages for their review.

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

  1. Load your first page (example: 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.