Child pages
  • Sakai 2.9 Neoportal Firefox Comprehensive WCAG 2 Protocol Results
Skip to end of metadata
Go to start of metadata

Test Details

Browser/OS Used:

Firefox 8.0.1 on Windows 7, IE 9, Safari 5.1 on OS/X

Sakai Tool:

Default Neoportal

Page(s) Tested:

Gateway, course site

Date:

November 30, 2011

QA Server:

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

QA Server Environment:
(Copy from footer)

Sakai 2.9.0-a02

Evaluator(s):

Brian Richwine

Evaluation Complete: (Yes / No):

No

Accessibility Problems and Recommended Solutions

Subject

Results

Recommendations

Priority

JIRAs

Images

The src URL for the /library/image/silk/comment.png icon used in the portal chat gets read aloud by adaptive technologies because the alt attribute is missing.

Add an alt attribute to the image element for the icon. Since the image is redundant to the text already present, an empty alt attribute is appropriate. This will cause screen-readers to ignore the image.

<img style="vertical-align: middle;" src="/library/image/silk/comment.png" alt="">

Critical

SAK-21503 - Accessibility: The image element for the silk/comment.png icon image used in portal chat needs an alt attribute ( Closed)

Linearized Content

 

 

 

 

Reliance on Sensory Characteristics

OK -  No instructions that depend on sensory characteristics were found.

 

 

 

Use of Color

Currently selected worksite is indicated by color alone. Currently selected site is not revealed semantically (in the neo-portal, the currently selected worksite is revealed by color alone, it is listed in the page title though that page title is difficult for sighted individuals to see in many modern web browsers - it get's severely truncated to fit in the tab for the browser page).

 

 

 

Sufficient Contrast

 

 

 

 

Resizable Text

 

 

 

 

Semantics

 

 

 

 

Keyboard Operatibility

Top worksites navigation menus do not work according to ARIA specifications and do not function the same as other pull down menus in the site.

 

Critical

SAK-22026 - Accessibility: NeoPortal Keyboard Interactions Are Non-standard and Inconsistent/Broken ( Closed)

Keyboard Operatibility

Inconsistent - tabbing through the sites in the main neoportal nav bar is one tab per site while tabbing through the sites in the more sites drawer is two tabs per site. 

 

Major

SAK-22026 - Accessibility: NeoPortal Keyboard Interactions Are Non-standard and Inconsistent/Broken ( Closed)

Keyboard Operatibility

Activating a worksite's pulldown menu in the "More Sites" drawer by keyboard is different than the interaction required to open a worksite's drop down menu in the main neoportal nav bar.

 

Critical

SAK-22026 - Accessibility: NeoPortal Keyboard Interactions Are Non-standard and Inconsistent/Broken ( Closed)

Keyboard Operatibility

Activating the "More Sites" drop down menu by keyboard is different than the interaction required to open a worksite's drop down menu on the main navigation bar.

 

Critical

SAK-22026 - Accessibility: NeoPortal Keyboard Interactions Are Non-standard and Inconsistent/Broken ( Closed)

Keyboard Operatibility

Once a worksite's pulldown menu in the "More Sites" drawer has been opened, it can't be closed by keyboard users. Also, it can only be closed by mouse users if they select another worksite's menu, another worksite, or close the drawer altogether.

 

Critical

SAK-22026 - Accessibility: NeoPortal Keyboard Interactions Are Non-standard and Inconsistent/Broken ( Closed)

Keyboard Operatibility

Keyboard focus can leave the open "More Sites" drawer and travel through the page even though the "More Sites" drawer is still open and masking the page.

 

Critical

SAK-22026 - Accessibility: NeoPortal Keyboard Interactions Are Non-standard and Inconsistent/Broken ( Closed)

Time Limits

No warning or notification of session time out other than getting logged out and returning to the gateway page.

I thought a dialog box used to appear. Is that feature there and just not turned on by default?

 

 

Control of Updates

No ability to control announcements of chat tool updates to adaptive technologies.

 

 

 

Prevent Seizures

OK - No flashing content found.

 

 

 

Bypass Blocks - Headings

Inconsistent - Chat tool is not demarcated in the same way as other page features.

Suggest putting a hidden heading before the chat tool features and bringing the chat tool's heading's levels in line.
<h1 class="skip">Chat</h1>
<h2>My Connections</h2>
<h2>In this site</h2>

Critical

SAK-22027 - Accessibility: The NeoPortal Chat tool use of headings is not correct / consistent with other page features ( Closed)

Bypass Blocks - ARIA Landmarks

The ARIA landmarks work great and are well positioned. It would be helpful to label them so the region's function they are marking is made clear and to distinguish the multiple "navigation" landmark areas.

Place aria-label attributes on the navigation elements with landmarks that describe their purpose.

Critical

SAK-22021 - Accessibility: The ARIA Landmarks presented by the Neoportal are not all unique ( Closed)

Bypass Blocks - Skip Content Links

Skip navigation links are not visible to keyboard only users

Modify CSS so the skip navigation links automatically appear when they receive keyboard focus.

Major

SAK-21502 - Accessibility: Skip Navigation links aren't visible to allow access to sighted keyboard only users ( Closed)

Bypass Blocks - Skip Content Links

Skip navigation links do not work in Webkit Browsers

Webkit won't let an item that is positioned offscreen receive focus. Also, Webkit only scrolls the page

Critical

SAK-21507 - Accessibility: The three skip navigation links do not work in Safari or Chrome ( Closed)

Bypass Blocks - Group Links

 

 

 

 

Bypass Blocks - Frame / Page Titles

OK - All frames have descriptive titles

 

 

 

Page Titles

OK

 

 

 

Focus

It is difficult to tell between the currently selected workspace and a workspace navigation bar entry that has keyboard focus.Visual indication of keyboard focus is often non-standard and changes seemingly randomly depending on which item has focus.

Always use the dotted outline and hover styling to indicate keyboard focus. Consider making the moon-glow highlight a bit brighter.

Critical

SAK-22029 - Accessibility: NeoPortal Visual Indication of Keyboard Focus Difficult to See, Inconsistently Implemented, and Other Issues ( Closed)

Focus

Inconsistent: The focus indicator in the neoportal navigation bar changes depending on what element focus is on and where the element is located. This will confuse users with low vision and cognitive issues:

1) Logout: standard outline (no moon-glow, no blue text)
1) Worksite in top nav bar: Moon-glow highlight + text changes to blue (no outline)
X) Worksite menu: doesn't get/show focus
2) "More Sites" in top nav bar: outline-left+outline+right + text changes to blue (no Moon-glow)
3) Worksite name in "More Sites" drawer: text changes to blue (no outline, no moon-glow)
4) Worksite menu in "More Sites" drawer: standard outline
5) "View All Sites" and "+Add New Site" buttons: text changes to blue (no outline, no hightlight)

Consider always showing the default thin dotted outline (in white) as a keyboard focus indicator along with whatever other visual flare is desired

Critical

SAK-22029 - Accessibility: NeoPortal Visual Indication of Keyboard Focus Difficult to See, Inconsistently Implemented, and Other Issues ( Closed)

Links

Not sure why the "More Sites" has an additional piece of hidden text that says "Worksites" so the link text for screen reader becomes: "More Sites Worksites".

<a title="More Sites" onclick="return dhtml_view_sites();" href="#"><span>More Sites <em class="skip">Worksites</em></span></a>

???

Major

SAK-21197 - "More" sites dropdown link needs to be clearer for screen reader users ( Closed)

Links

"Expand / Contract Navigation" link does not describe the specific function that will occur when activated (that it will expand or that it will contract the navigation). The current state of the navigation is obvious visually, and the function of the link is also only indicated visually by the direction the triangle graphic points. If a non-visual user is demonstrating Sakai to others (in a class, for instance), they would have to ask if the tools list navigation is visible or not before they can know it is set they way they want it to be.

Also, there are several "navigation" features in a typical Sakai view. Which navigation feature is it referring to?

Change the text from "Expand/Contract Navigation" to one of the following (as appropriate):

  - When tools list is visible: "Contract Tools List Navigation"

  - When tools list is not visible: "Expand Tools List Navigation"

Major

SAK-22030 - Accessibility: Expand/Contract Tools List Navigation Link Text is Not Sufficiently Descriptive ( Closed)

Links

"X" link that closes the neo portal chat feature is not descriptive of its function.

Suggested fix:

Follow the pattern that the help icons use in the tool title bars. Change the 'x' to an image and supply a meaningful alt attribute. Use css to set the icon in the background (so it can be skinned). For example:

<a id="pc_chat_close" href="#">
   <img border="0" alt="Close Chat widget" src="/library/image/transparent.gif">
</a>

Critical

SAK-21504 - Accessibility: Portal chat close link text of 'x' is not meaningful or descriptive of its function ( Verified)

Headings

Neo portal chat feature has two level five headings that are not in the correct hierarchical order. Screen-reader users may think the headings belong under other page content.

Suggest putting a hidden heading before the chat tool features and bringing the chat tool's heading's levels in line.
<h1>Chat</h1>
<h2>My Connections</h2>
<h2>In this site</h2>

Critical

SAK-22027 - Accessibility: The NeoPortal Chat tool use of headings is not correct / consistent with other page features ( Closed)

Labels

 

 

 

 

Language Identification

OK - Default human language is indicated

 

 

 

Change of Context

Help links do not announce that they are opening in a new window

 

 

 

Consistency

Top worksites navigation menus do not work according to ARIA specifications.

 

 

 

Consistency

Refers to "Worksites" (as in "worksites begin here") and to "Sites" (as in "View all sites")

Should "worksites begin here" be changed to "Sites List begins here"? (And "Tools begin here" changed to "Tools list begins here")

Major

SAK-22028 - Accessibility: NeoPortal Inconsistent using "Sites" and "Worksites" terminology. ( Closed)

Access keys

 

 

 

 

Change of Context Notification

Help links do not announce that they are opening in a new window

 

 

 

Error Notices

 

 

 

 

Required Field Notification

OK - None found / None seem to be required

 

 

 

Error Prevention

 

 

 

 

Help

Help links do not announce that they are opening in a new window.

 

 

 

Other Functionality

When used with IE+JAWS, the top navigation bar crashes IE whenever one of the top links gets focus.

 

Critical

SAK-20916 - Accessibility: Accessing a Site from NeoPortal Worksite Navigation Causes Internet Explorer 8 and 9 to Crash when Used with the JAWS Screen-Reading Software ( Verified)

Validation

 

 

 

 

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.