Child pages
  • Sakai 2.8 Chat Firefox Accessibility Toolbars Protocol Results
Skip to end of metadata
Go to start of metadata

Test Details

Browser/OS Used:

Firefox 3.6.12, Windows 7

Sakai Tool:

Chat

Page(s) Tested:

 

Date:

22.November.2010

QA Server:

Qa1-nl

Accessibility Problems and Recommended Solutions

Subject

Results

Recommendations

Priority

JIRAs

Links

When on the "Manage Rooms" page as an instructor, the "Edit", "Delete", "Clear History", "Set as Default" links do not make sense when taken out of context.

Add hidden link text that adds name of the chat room as context to screen reader users. For example:

HTML:

<div id="..." class="itemAction"><a ...>Edit<span class="skip"> Alternate Chat Room Settings.</span></a>
|
<a ...>Delete<span class="skip"> the Main Chat Room.</span></a>
|
<a ...>Clear History<span class="skip">&nbsp; for the Main Chat Room.</span></a>
|
<a ...>Set <span class="skip">Main Chat Room</span> as Default</a>

CSS:

.skip
{    position: absolute;
    left: -999em;
    width: 1em;
    overflow: hidden;
}

Major

SAK-19569

Links

When in a chat room as an instructor, the "Options" and "Change Room" links have the same destination/function. They both allow for changing the room.

Should the "Options" link be removed?

Minor

SAK-19994

Images

OK



 

Page Structure / Markup

"Users in Chat" should be a level three heading.

Change:
<div class="chatListHeadWrapper">Users in Chat</div>
To:<h3 class="chatListHeadWrapper">Users in Chat</h3>

Major

SAK-19639

Consistency



 

 

Access Keys

OK



 

Frame Titles

OK



 

Style sheets / Linearization

OK



 

Text Zoom

OK



 

Tab Order

OK



 

Functionality

Select menus have onChange events that change the page context when exploring the options with arrow keys in IE.

This is a global issue in Sakai. Exploring use of a jQuery event handling routine to create a more accessible user interaction for select menus in IE.

Critical

SAK-11199

Color

OK



 

FAE Results

Nothing new found.



 

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.