Sakai 2.9 Admin Sites Tool Walkthrough Scripts Results
Evaluation Details
Browser/OS Used: | IE 9, Windows 7 32 bit |
Adaptive Technology Used: | JAWS 12 |
Sakai Tool: | Â |
Page(s) Tested / | Â |
Date: | 11/07/2011 |
QA Server: | Â |
QA Server Environment: | Â |
Evaluation Participants: | Â |
Evaluation Complete: (Yes / No): | No |
Accessibility Issues and Recommended Solutions
Task / Subject | Results / Issue | Recommendations | Priority | JIRAs |
---|---|---|---|---|
Explore Tool / Describe Page | Create site, see ones that exist and maybe edit them. | Â | Â | Â |
Explore Tool / Describe Page | Table summary has misspellings in it. | Fix summary. | Minor | Â |
Determine if particular site is published and joinable | Table results for Published / Joinable should have a Yes / No, not just blank. | Spell out Yes or No as appropriate for the results | Major | |
Search for a site by site title | Worked OK, found requested site. | Â | Â | Â |
Edit the searched for site | Focus landed by an edit field on the text that says "Skin" | Move focus to top of the form | Major | fixed |
Edit site description | Used table reading keys to navigate the form, and selected next row when trying to get to the CKEditor to edit the description, however the CKEditor is not in the table so |  |  |  |
Edit site description | Moving to the CKEditor did not announce any help info, only "Description Edit". | Include a link before the editor that says "CKEditor Help" | Minor | ??? |
Edit site | Published, Joinable, Public View, Custom View radio buttons do not have a legend. For instance, tabbing to the Joinable No radio button simply says "No Radio button checked 2 of 2" and does not say what you are saying no to. | Use legends for the radio buttons. | Major | |
Edit Sites | Button text does not make sense out of context. For example when tabbing to the "Add/Edit properties" button, it simply says "Properties" | Use full description of button function for text label. | Major | |
Verify Change | Searched for site and saw the updated descriptions - Success | Â | Â | Â |
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.