Child pages
  • Sakai 2.9 New Account Firefox Comprehensive WCAG 2 Protocol Results
Skip to end of metadata
Go to start of metadata

Test Details

Browser(s) / OS Used:

Firefox 14.0.1

Sakai Tool:

New Account

Page(s) Tested:

 

Date:

July 31, 2012

QA Server:

sakaicle1-trunk.uits.indiana.edu

QA Server Environment:
(Copy from footer)

Sakai 2.9.0-b05 (Kernel 1.3.0-b04)

Evaluator(s):

Scott Williams

Evaluation Complete: (Yes / No):

Yes

Accessibility Problems and Recommended Solutions

Subject

Results

Recommendations

Priority

JIRAs

Images

OK

 

 

 

Linearized Content

OK

 

 

 

Reliance on Sensory Characteristics

OK

 

 

 

Use of Color

OK

 

 

 

Sufficient Contrast

"Type" text-entry box default text "registered" has insufficient contrast background color: 2.17:1.

(Selected Tool text also has insufficient contrast but this is addressed in the Profile 2 evaluation.)

Darken text color to #555562.

Minor

 

Resizable Text

OK.

 

 

 

Semantics

OK. Forms labeled correctly.

 

 

 

Keyboard Operatibility

OK.

 

 

 

Time Limits

OK. None.

 

 

 

Control of Updates

OK. None.

 

 

 

Prevent Seizures

OK. No blinking.

 

 

 

Bypass Blocks - Headings

Headings are sufficient.

 

 

 

Bypass Blocks - ARIA Landmarks

ARIA landmark roles are present.

 

 

 

Bypass Blocks - Skip Content Links

"Jump to content" and "Jump to tools list" links are present and are visible on keyboard focus.

 

 

 

Bypass Blocks - Group Links

OK.

 

 

 

Bypass Blocks - Frame / Page Titles

OK.

 

 

 

Page Titles

OK.

 

 

 

Focus

Focus is visible and order follows visual flow.

 

 

 

Links

OK.

 

 

 

Headings

OK

 

 

 

Labels

OK.

 

 

 

Language Identification

OK.

 

 

 

Change of Context

Help page link appropriately states that it will open new browser window.

 

 

 

Consistency

OK.

 

 

 

Access keys

Access keys for tools list and content bring focus to jump links at top of page, from which the user can navigate to the tools list or main content. Is this the desired behavior? Access+0 does not open up the accessibility page.

 

 

 

Change of Context Notification

OK.

 

 

 

Error Notices

After entering information for a user with a pre-existing account or other erroneous entries, the error message appears above the form, so the user has no idea of what has transpired. The JAWS virtual cursor remains at the bottom of the iframe, on the "Create Account" button. The user will not know that the account has not been created without hunting for the error message.

Use an ARIA live region to put focus directly before the error message.

Major

SAK-22840 - Users of screen reading software are not alerted to error messages when creating a new account Resolved

Required Field Notification

Required fields are denoted by an asterisk "*" without an explanation of meaning of asterisk before the form begins. This is insufficient notification.

Explain meaning of asterisk before the form. Also add aria-required attribute to indicate required field for SR users. Example:

 <input name="ariaexample" id="example" aria-required="true" aria-label="Test"/>

Minor

 

Error Prevention

OK.

 

 

 

Help

AccessKey+h conflicts with browser help hot keys in Firefox and IE. (Test in Safari)

 

 

 

Validation

Error Line 75, Column 13: ID "skipNav" already defined

Error Line 165, Column 12: end tag for element "a" which is not open

Error Line 252, Column 8: end tag for "div" omitted, but OMITTAG NO was specified

Correct major syntax errors.

 

 

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.