Sakai 2.9 Assignments Tool Firefox Comprehensive WCAG 2 Protocol Results

Test Details

Browser/OS Used:

Firefox 8, Windows 7

Sakai Tool:

Assignments

Page(s) Tested:

Assignment List, test assignment submission, test assignment submission confirmation

Date:

11-29-2011, 12-6-2011, 12-7-2011, 12-8-2011

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-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

  1. On the "Assignments List" page the "Chat" speech bubble image does not have an alt attribute.
  1.  The image should have an empty alt attribute (alt="")
  1. Minor
  1. This is not an assignments issue, but a neoportal issue. SAK-21503

Linearized Content

No issues

 

 

 

Reliance on Sensory Characteristics

No issues

 

 

 

Use of Color

No issues

 

 

 

Sufficient Contrast

  1. As part of the portal The currently selected tool (grey on white) does not meet the minimum color contrast ratio.
  1. The color, font weight and opacity should be changed to make it stand out and meet color contrast requirements. 

    #toolMenu li.selectedTool span, #toolMenu li.selectedTool a
     color: #3355BB;
    opacity: 0.7;
     text-decoration: none;
    font-weight: bold;
  1. Minor

 

Resizable Text

No issues

 

 

 

Semantics

  1. as part of the portal there are multiple navigation landmarks with no additional descriptions to differential the two landmarks. One of the navigation landmarks is on the wrong element. it is on the skip navigation anchor instead of the actual list of navigation links
  2. On the Assignments main page the "Show ___ items" combo box is labeled as "Press Enter, then use alt + up and down arrows to scroll through menu".
  3. The file upload form control in the attachments section on the test assignment submission page is not explicitly labeled.
  1.  The aria-label attribute should be added to both navigation landmarks to provide more context. the top navigation role navigation should be moved from the h1 to the ul element
    <ul id="topnav" class="topnav" role="navigation" aria-label="Worksites Navigation">

    <div id="toolMenu" role="navigation" aria-label="Tools Navigation">
  2. The combo box should have a proper label and the instructions should come before the label element and combo box

    <span class="skip">To operate the combo box, first press Alt+Down Arrow to open it, and then use the up and down arrow keys to scroll through the options.</span>
    <label class="skip" for="selectPageSize"> Number of items per page</label>
    <select id="selectPageSize" name="selectPageSize" onchange="document.pagesizeForm.submit();">
  3. The File upload form control should be labeled
    <tr>
                                                <td>
                                                    <label for="clonableUpload">Select a file from computer</label>
                                                </td>
                                                <td>
                                                    <div id="clonableUpload">
                                                        <input type="file" "="" onchange="javascript:showNotif('submitnotifxxx','post','addSubmissionForm');document.getElementById('addSubmissionForm').action='http://sakaicle1-trunk.uits.indiana.edu:8181/portal/tool/07171c50-3a56-4973-8785-caae686b9b57?panel=Main&sakai_action=doAttachUpload';submitform('addSubmissionForm');" id="clonableUpload" name="upload">
                                                        <span style="visibility:hidden" id="submitnotifxxx">Uploading file</span>
                                                    </div>
                                                </td> ...
                                                </tr>
  1. Minor
  2. Major
  3. Major
  1. none yet
  2. SAK-22727 - Getting issue details... STATUS
  3. SAK-22731 - Getting issue details... STATUS

Keyboard Operatibility

  1. On the test assignment submission page, the keyboard focus gets partially trapped in the rich text editor.  The user cannot shift+tab out of the editor, but they can tab out of it
  1.  The keyboard focus should not be trapped in the rich text editor, even partially.
  1. minor

 

Time Limits

No issues

 

 

 

Control of Updates

No issues

 

 

 

Prevent Seizures

No issues

 

 

 

Bypass Blocks - Headings

No issues

 

 

 

Bypass Blocks - Skip Content Links

  1. Skip navigation links are not keyboard accessible. (portal)
  1.  Modify the CSS so the hidden skip to links appear when they receive focus.
  1. Major
  1. fixed

Bypass Blocks - Group Links

No issues

 

 

 

Bypass Blocks - Frame / Page Titles

No issues

 

 

 

Page Titles

  1. The page titles do not change when viewing the details of an assignment.
  1.  All page titles should be unique.

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

 

Focus

No issues

 

 

 

Links

No issues

 

 

 

Headings

No issues

 

 

 

Labels

See Semantics table row

 

 

 

Language Identification

No issues

 

 

 

Change of Context

No issues

 

 

 

Consistency

No issues

 

 

 

Access keys

No issues

 

 

 

Change of Context Notification

No issues

 

 

 

Error Notices

No issues

 

 

 

Required Field Notification

  1. On the test assignment page, a user must either enter text in the rich text editor or upload a file.  These instructions are not included on the page and only appear when the page errors out after submission.
  1. The requirement of text in the rich text editor or 1 upload should be specified in the instructions.

    <p>This assignment allows submissions using both the text box below and attached documents. Type your comments in the box below and use the Add Attachments button to include other documents. Save frequently while working. You are required at minimum to enter text in the rich text editor or upload 1 file.</p>
  1.  minor

 

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.