Sakai 2.9 Neoportal Chat Walkthrough Script Results

Evaluation Details

Browser/OS Used:

Windows 7 IE9, MacOS 10.7/Chrome

Adaptive Technology Used:

JAWS 12, Mac VoiceOver

Sakai Tool:

Neoportal Chat

Page(s) Tested /
Walkthrough Script:

Sakai home page

Date:

12/22/11

QA Server:

http://sakaicle1-trunk.uits.indiana.edu/

QA Server Environment:
(Copy from footer)

Kernel 1.3.0-SNAPSHOT

Evaluation Participants:

Scott Williams

Evaluation Complete: (Yes / No):

No

Accessibility Issues and Recommended Solutions

Task / Subject

Results / Issue

Recommendations

Priority

JIRAs

Finding chat

The Neoportal Chat link is dead last in the reading order. I resorted to finding it in the list of links.

Make a heading at the same level as the other hidden headings that precede blocks of page structure.

Critical

SAK-22027 - Getting issue details... STATUS

Any

The number of connections is repeated every few seconds ad infinitum in JAWS. VoiceOver doesn't do this.

 

 

 

Posting message

VoiceOver correctly announces message text on send. JAWS does not.

 

 

 

Receiving message

Neither JAWS nor VoiceOver announces message text when received.

 

 

 

Message history

OK

 

 

 

Opening chat

After clicking on the chat link, nothing is announced when the chat box was opened.

 

 

 

Duplicate links

<name> message link is identical to <name> "my connections" link. No way of differentiating between the two.

 

 

 

Text entry

Text entry field in chat is not labeled.

 

Critical

SAK-22061 - Getting issue details... STATUS

Plug-in requirement?

I never could determine what Plug-in I needed to avoid the error message when sending messages in Firefox, therefore was unable to proceed with the Firefox testing. Tried all the usual suspects (Quicktime, Flash, etc.) to no avail. Why should I need ANY plug-in for Sakai?

 

Major

SAK-22133 - Getting issue details... STATUS

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.