Sakai 2.9 Announcements Tool Instructor Persona Firefox Comprehensive WCAG 2 Protocol Results

Test Details

Browser(s) / OS Used:

Firefox 9, Windows 7

Sakai Tool:

Announcements

Page(s) Tested:

Announcements main page, Post Announcement, Edit Announcement, Merge, Option, Permissions

Date:

1-5-2012, 1-6-2012

QA Server:

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

QA Server Environment:
(Copy from footer)

Sakai 2.9 Accessibility Review - TRUNK - Sakai 2.9-SNAPSHOT (Kernel 1.3.0-SNAPSHOT)- 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

No issues

 

 

 

Reliance on Sensory Characteristics

No issues

 

 

 

Use of Color

No issues

 

 

 

Sufficient Contrast

No issues

 

 

 

Resizable Text

No issues

 

 

 

Semantics

  1. The table summary on the announcements main page  needs to be updated.
  2. The remove checkboxes on the announcements main page do not have unique labels.
  3. The Access and Availability radio buttons on the Post and Edit Announcement pages are not in a fieldset. in addition, the Availability specify Dates check boxes are not in a fieldset. This would also apply to the display options on the options page.
  4. Multiple Combo boxes on the Post and Edit Announcements pages are unlabeled.
  1.  Update the table summary to accurately describe the table.

    <table class="listHier" cellspacing="0" border="0" summary="Table contains a list of announcements. It is eight columns wide and each row contains a single announcement. Column one indicates if the announcement has an attachment, column two contains the subject(title) of the announcement, column three (Saved by) has the name of the author, column four shows the date the announcement was last modified, column five describes the availability of the announcement (For) whether public or private, column six contains the date the announcement will become available to view in detail (Beginning Date), column seven contains the date the announcement will no longer be available (Ending Date) and column eight contains a check post to remove the selected announcement.">
  2. All form controls should have unique labels.

    <label class="skip" for="check-1">Select to remove "Assignment title"</label>
    <input id="check-1" type="checkbox" value="/announcement/msg/15f0636e-07b5-4c79-842b-a4dc505ea068/main/0d841982-cc8b-4e04-9a8b-c2df65740ff6" name="selectedMembers" title="Select to remove ' Assignment title'">
  3. All radio button and checkbox groups should be in a fieldset.

    <fieldset>
       <div>
          <legend class="h4">Access</legend>
       </div>
       <p class="checkbox">
         <input id="site" type="radio" onclick="$('#groupTable').fadeOut('slow'); resizeFrame()" checked="checked" value="site" name="announceTo">
         <label for="site">
            Only
            <strong>members of this site</strong>
            can see this announcement
         </label>
       </p>
       <p class="checkbox">
        <input id="pubview" type="radio" onclick="$('#groupTable').fadeOut('slow');resizeFrame()" value="pubview" name="announceTo">
        <label for="pubview">
          This announcement is
          <strong>publicly viewable</strong>
         </label>
      </p>
    </fieldset>
  4. All form controls should be explicitly labeled.

    <label for="release_day" class="skip">Beginning Date Day</label>
    <select onchange="document.getElementById('hidden_specify').checked=true;document.getElementById('use_start_date').checked=true;" id="release_day" name="release_day">
                                  <option value="1">1</option>...
                       </select>
  1. Minor
  2. Major
  3. Major
  4. Major
  1. none yet
  2. SAK-22716 - Getting issue details... STATUS
  3. SAK-22717 - Getting issue details... STATUS
  4. SAK-22718 - Getting issue details... STATUS

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

  1. There are two navigation landmarks with no unique text description (portal)
  1.  Each navigation landmark should have a unique text description or label:

    <h1 class="skip" role="navigation" aria-label="Worksites list">Worksites begin here</h1>
    <div id="toolMenu" role="navigation" aria-label="Site Tools">
  1.  minor

 

Bypass Blocks - Skip Content Links

No issues

 

 

 

Bypass Blocks - Group Links

No issues

 

 

 

Bypass Blocks - Frame / Page Titles

No issues

 

 

 

Page Titles

  1. The Merge, Options, and Permission pages do not have unique page titles.
  1.  All page titles should be unique.

    <title>Sakai 2.9 Accessibility Review : AR Test 101 123 Spring 2011 : Announcements: Announcements Permissions</title>
  1.  Minor

 

Focus

No issues

 

 

 

Links

  1. Multiple "edit" links exist on the Announcements main page
  1. Every link should have unique link text.

    <a title="Edit announcement Assignment: Open Date for 'Assignment B'" href="http://sakaicle1-trunk.uits.indiana.edu:8181/portal/tool/c17adcaa-6961-4d4f-a0f6-e8e91aee95b6?itemReference=/announcement/msg/15f0636e-07b5-4c79-842b-a4dc505ea068/main/0d841982-cc8b-4e04-9a8b-c2df65740ff6&panel=Main&sakai_action=doReviseannouncement">Edit <span class="skip">announcement Assignment: Open Date for "Assignment B"</span></a>
  1. Major
  1. SAK-22719 - Getting issue details... STATUS

Headings

No issues

 

 

 

Labels

No issues

 

 

 

Language Identification

No issues

 

 

 

Change of Context

  1. On the Post and Edit Assignments pages when you select one of the Access and Availability radio buttons the focus changes
  1.  The focus should not change on input
  1.  Major
  1. fixed

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.