Sakai 2.8 Portal Firefox Accessibility Toolbars Protocol Results

Browser/OS Used:

Firefox 3.6.12, Windows 7

Sakai Tool:

Portal

Page(s) Tested:

Date:

22.November.2010

QA Server:

Qa1-nl

Links

The portal includes three "Skip Navigation" links (Jump to Content, Jump to Tools List, and Jump to Worksite list). These links are very useful and should be maintained. However, no worksite list is present until a user has logged in. 

The "Jump to Worksite list" skip navigation link should be suppressed until a user has logged in.

Minor

SAK-19559

Links

The link text available to adaptive technology changes when the tools list navigation is collapsed. This will especially confuse low-vision/blind users who are using first letter navigation or search features to activate a link. This is because the link text is being hidden via CSS using display:none. Many adaptive technologies (like screen-readers) honor display:none and visibility:hidden.

Suggestion, use a similar technique as employed by the "skip" css class to hide the link text when collapsing the navigation so the link text is hidden and yet remains available to adaptive technologies.
 In portal.css change this:

.sakaiMinimizePageNavigation #toolMenu li span {
  display: none;
}

to this:

.sakaiMinimizePageNavigation #toolMenu li span {
  position:absolute;
  left:-10000px;
  top:auto;
  width:1px;
  height:1px;
  overflow:hidden;
}

Critical

SAK-19566

Links

The Help tool link in the left hand tools list navigation does not have a title attribute. When the tools list navigation is contracted, adaptive technologies like screen-readers resort to reading the href attribute's value (the URL) which is confusing and unpleasant to listen to.

Provide a meaningful title attribute to the link for the help link in the tools list that is parallel to the title attributes provided on all the other tool links.

Major

SAK-19567

Page Structure / Markup

The "Users Present" feature used to be contained in an iFrame, which was easily navigable to by screen-reader users. Now that it is no longer in an iFrame, the feature should be marked up by a heading so adaptive technology users can find it easily.
Screen-reading software (and many web browsers) provide features that allow users to navigate a page by heading. The portal uses level one headings to markup the various sections of the page (the Worksites list, the tools list/navigation, the tool content iFrame). Using a level one heading to markup the Users present feature would be analogous.

Either markup the "Users present:" text as a level one heading:

<div id="presenceWrapper">
 <h1 id="presenceTitle">Users present:</h1>
 <div id="presenceIframe">
  <ul class="presenceList">
   <li><span title="Currently in Site">Course Instructor</span></li>
  </ul>
 </div>
</div>

or, add a hidden level one heading before the presenceTitle:

<h1 class="skip">Users Present List</h1>
<div id="presenceWrapper">
 <div id="presenceTitle">Users present:</div>
 <div id="presenceIframe">
  <ul class="presenceList">
   <li><span title="Currently in Site">Course Instructor</span></li>
  </ul>
 </div>
</div>

Major

SAK-19568

Access Keys

OK

Frame Titles

OK

Style sheets / Linearization

OK

Text Zoom

OK

Tab Order

OK

Functionality

Visual indication of focus is not shown when the collapse/expand navigation icon has focus. This will confuse users who must use the keyboard to navigate the page.

The problem appears to be in portal.css with the following CSS ruleset:

#toggleToolMenu, #toggleToolMenu:visited, #toggleToolMenu:active, #toggleToolMenu:focus {
 outline:medium none;
 }

Suggested Fix:
Simply removing this ruleset from portal.css

Major

SAK-19396

Color

OK

FAE Results

OK