Sakai 2.9 Schedule Firefox Comprehensive WCAG 2 Protocol Results (2012)

Test Details

Browser(s) / OS Used:

Firefox 14.0.1 / Windows 7

Sakai Tool:

Schedule

Page(s) Tested:

Main, random events

Date:

8-6-2012

QA Server:

http://sakaicle1-trunk.uits.indiana.edu:8181/portal

QA Server Environment:
(Copy from footer)

Sakai 2.9 Accessibility Review - TRUNK - Sakai 2.9.0-b05 (Kernel 1.3.0-b04)- Server localhost

Evaluator(s):

Joe Humbert

Evaluation Complete: (Yes / No):

Yes

Accessibility Problems and Recommended Solutions

Subject

Results

Recommendations

Priority

JIRAs

Images

No issues

 

 

 

Linearized Content

When dates have 3 or more events, the events appear to be on multiple dates instead of a single date 

Configure the CSS to allow the table cells to encompass their containing information without overlap

Minor

 

Reliance on Sensory Characteristics

No issues

 

 

 

Use of Color

The Dates which have events are designated with a yellow color, but no text.

Provide an invisible heading or text that designates which days have events

Minor

 

Sufficient Contrast

No issues

 

 

 

Resizable Text

No issues

 

 

 

Semantics - Tables

The table summary for the calendar table does not provide enough information

The table summary could be, "This table contains all the events for the current course or workspace. The table is currently organized in a month overview format. Columns represent each day of the week, Sunday through Saturday."

Minor

 

Keyboard Operatibility

No issues

 

 

 

Time Limits

No issues

 

 

 

Control of Updates

No issues

 

 

 

Prevent Seizures

No issues

 

 

 

Bypass Blocks - Headings

No issues

 

 

 

Bypass Blocks - ARIA Landmarks

No issues

 

 

 

Bypass Blocks - Skip Content Links

No issues

 

 

 

Bypass Blocks - Group Links

No issues

 

 

 

Bypass Blocks - Frame / Page Titles

No issues

 

 

 

Page Titles

The individual event pages do not have a unique page title, it is the same as the main schedule page

The individual event pages should have unique page titles.

Major

 

Focus

No issues

 

 

 

Links

The date links (e.g., 1, 2, 31, etc.) are not unique or descriptive of their purpose. 

In "Calendar by Month" view Most link text is truncated to the point that the link text does not make sense with or without context

Extra context should be added to the link to make it unique and descriptive.

E.g.: <a style="padding:3px;margin:0;display:block;width:50%" href="http://sakaicle1-trunk.uits.indiana.edu:8181/portal/tool/cb570de4-4c0d-4fa5-a475-223f0d0dc184?day=31&month=7&year=2012&panel=Main&sakai_action=doDay"><span class="skip">Events for July</span> 31</a>

Add extra context to the truncated links so that they make sense out of context.

E.g.: <a style=" text-decoration: none !important" title="Class field trip - AR Test 101 123 Spring 2012" href="http://sakaicle1-trunk.uits.indiana.edu:8181/portal/tool/cb570de4-4c0d-4fa5-a475-223f0d0dc184?eventReference=/calendar/event/7aa94e8c-8f28-4d31-a54b-166f3cd17d64/main/2b0fb5e8-61b7-4e6a-93d5-c26585742ab7&panel=Main&sakai_action=doDescription">
<img border="0" alt="Activity" src="/library/image/sakai/activity.gif?panel=Main">

Class fi <span class="skip">eld trip</span>...
</a>

Major

 

Headings

No issues

 

 

 

Labels

No issues

 

 

 

Language Identification

No issues

 

 

 

Change of Context

When selecting an item from the view form control, the calendar view automatically changes.  There is hidden instructions on how to prevent automatic submission for users of screen reading software, but not keyboard-only users.

Possible inclusion of the information in the help documentation would be beneficial.

Minor

 

Consistency

No issues

 

 

 

Access keys

No issues

 

 

 

Change of Context Notification

No issues

 

 

 

Error Notices

No issues

 

 

 

Required Field Notification

No issues

 

 

 

Error Prevention

No issues

 

 

 

Help

No issues

 

 

 

Validation

No issues

 

 

 

Priority Definitions

  • Critical: Issue will keep some/all users from being able to use this tool.
  • Major: Issue will cause significant difficulty to some/all users and should be revised.
  • Minor: Tool can be used successfully, but functionality will be significantly improved by fixing issue.
  • Trivial: Indicates that this issue has a relatively minor impact.