Sakai 2.9 Login Page Site Browser Tool JAWS Walkthrough Script Results
Test Details
Browser/OS Used: | IE 8 / JAWS 12 on XP |
Sakai Tool: | Login Page Features Tool |
Page(s) Tested: |
|
Date: | 2011.10.13 |
QA Server: | sakacle1-trunk.uits.indiana.edu |
QA Server Environment: | TRUNK - Sakai 2.9-SNAPSHOT (Kernel 1.3.0-SNAPSHOT) |
Test Participants: | Mary Stores: JAWS, Brian Richwine: Observer |
Accessibility Problems and Recommended Solutions
Subject | Results | Recommendations | Priority | JIRAs |
|---|---|---|---|---|
Type of site radio buttons on search form | Radio buttons do not have any legend. What does "Any" radio button not selected mean? | Convert "Type of Site" from a heading into a fieldset legend | Critical | SAK-21797 - Getting issue details... STATUS |
After submitting search results | JAWS announces it was in forms mode (because of the login fields). | Set focus inside of the Site Browser tool on the "Results" heading so the screen-reader user knows the search results are present. |
|
|
Page title after submitting page results | Page title does not inform the user that they are on the search results page | Append "Search Results" on the end of the page title. |
|
|
List object navigation buttons | Buttons are only punctuation. | Need to be "next" and "Previous" instead of < and > | Critical | SAK-21677 - Getting issue details... STATUS |
Search results table summary | Table summary doesn't describe what is found in the table. | Mary and Brian will devise a new table summary. |
|
|
Search link in action bar | Meaning isn't intuitive | Consider making it "Back to search form" link. Or put such a link under the search results. |
|
|
List navigator | List navigator controls aren't repeated at the end of the results table. | Repeat controls at end of table. |
|
|
No Sites meet the search criteria text | Doesn't include the search criteria for error detection. Can't tell if the search info was entered incorrectly or that there really aren't any matching results. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
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.