Kerry J's List: Storyline and WCAGAA

Forum post outlining Articulate documentation against Section 508 standards.

"Speaking of 508.  Just had an accessibility professional do a 508 audit of an SL course this week.  
 
Some strange behaviors he noted:
 
JAWS didn't read the Notes pane title (bug?)
The tab navigation only activates the menu and glossary as global items.  This is unfortunate as you have to let JAWS read through the entire menu and or glossary instead of quickly tabbing through individual items.  
JAWS also ignored the alt-tag that I had applied to the photo characters and instead read the timeline description (Brian, Neutral Expression, Looking at the Camera).  
He also mentioned something about the virtual cursor struggling to work effectively in SL (not sure what that meant!).
 
On the positive side, the overall navigation seemed to work well, and it handled launching layers, etc. in fine fashion.  He was generally happy with the steps that SL has taken. His overall assessment:  SL probably meets the legal definition of accessibility, but could still use a fair amount of work on the usability front."

Comparison of Section 508 web standards to WCAG




This comparison simply combines the comparison of Section 508 web standards to WCAG 1.0 found in Note 1 to §1194.22 and the comparison of WCAG 1.0 to WCAG 2.0 published by the W3C, without interpretation.

Storyline and Section 508 accessibility compliance