Browser(s) / OS Used:
July 31, 2012
QA Server Environment:
Sakai 2.9.0-b05 (Kernel 1.3.0-b04)
Evaluation Complete: (Yes / No):
Accessibility Problems and Recommended Solutions
Reliance on Sensory Characteristics
Use of Color
"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.
OK. Forms labeled correctly.
Control of Updates
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
Bypass Blocks - Frame / Page Titles
Focus is visible and order follows visual flow.
Change of Context
Help page link appropriately states that it will open new browser window.
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
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.
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"/>
AccessKey+h conflicts with browser help hot keys in Firefox and IE. (Test in Safari)
Line 75, Column 13: ID "skipNav" already defined
Line 165, Column 12: end tag for element "a" which is not open
Line 252, Column 8: end tag for "div" omitted, but OMITTAG NO was specified
Correct major syntax errors.
- 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.