Child pages
  • Accessibility Reviews and Recommendations
Skip to end of metadata
Go to start of metadata

This section contains accessibility reviews for the 2.01 (508 and WCAG 1.0) and 2.1 (JAWS) releases. Please see the attachment for a summary of work to date.

  • No labels

11 Comments

  1. Things to add to Sakai Accessibility Page:

    1) High level tool commands (such as "Options" and "Permissions") require javascript to be turned on to work.

    1. 2) Directions to change frames setting to "no indication."

    2. 3) The relationship between headings and table cells is defined by the scope tag to accommodate accessibility hooks in Java Server Faces. Pre JAWS 5.1 screen readers do not recognize the scope tag, and will not read the heading for a cell when prompted.

    3. 4) Adaptive Technology products used with Sakai and found compatible: JAWS 6.1, Window-Eyes x. Evaluation tools used to assess Sakai compliance: A-Prompt, WebXACT, W3C Validator.

    4. 5) Text size can be enlarged or reduced by pressing control plus the "+" or "-" sign in Firefox, and by pressing control plus the middle button of a mouse in Internet Explorer.

  2. Common issues encountered in our reviews:

    1) Javascript is required for some operations. This becomes a moot point in WCAG 2.0 according to Chris Ridlap (ATRC), so long as we make it clear that activation of javascript is required for using Sakai. We should make this clear in the Accessibility Page, but elsewhere as well? For example, put an item in the Help Index for "Javascript"?

    2) Redundant tool headings. The problem here is that there are separate frames for page titles and content. Those two iFrames need to be merged, at which point the redundancy will go away.

    3) Enhance navigation by headings. We could further improve navigation for AT users by extending heading tags further into the tools. For example, include heading tags into table rows and forms. See individual tools for specifics. This will require a review and revision of the style guide to ensure we are consistent between tools.

    4) Others. Please add other common issues that need attention.

    1. 4) Make titles more descriptive This has been done in much of Sakai, but there are instances where we've overlooked it. For example, whenever a worksite name is shown in a form or table, we should append the term "worksite" to it. "Accessibility Test" has "Accessibility Test Worksite" as its title. This can, and should, be done dynamically.

      5) Add table captions Something that has been consistently overlooked. Will require revision to style guide. One way to make this less of an issue is to use current text preceding tables into the caption, and left justify using CSS. Most, if not all tables, already have lead-in text or a title that can be made into a suitable caption. Of course, we'll have to review and revise table headings for consistence formatting at some point...

    2. 6) Use Column and Row Headers in Tables. This will improve the context for blind persons using screen readers.

      7) Improve Title tags in table links. Make sure that title tags in tables include the subject item, i.e., do not put "view message," but "accessibility testing email; view message." Otherwise persons who have set their screen readers to read title tags won't hear the subject heading. Note: It would be even better to make the message: "accessibility testing email; click to read message."

    3. 8) Improve Title tags in Content-related iFrames. Frame titles should have the consistent format of "<name of tool> options" for the top iFrame and "<functional description>" for the second frame, without duplicating the tool name. For example: "Discussion Tool Options" and "Add New Topic".

      When the two iframes are combined, frame title should follow the format of "<name of tool>: <functional description>", again without duplication. For example: "Dicussion Tool: Add New Topic"

    4. 9) Make tool headings consistent. Tool headings should be consistent, and follow the following sequence: Heading: "<name of tool>", subheading: "<action verb><noun>" for actions, "<name of tool><type>" for rendered displays. For example: "Announcements", "Add Announcement" and "View Announcements", "Announcement List."

    5. 10) Add title tags to action buttons. Descriptive title tags should be provided for action buttons. For example, when "<" is used to indicate prior page, a title tag should be provided that reads "Previous page."