Minnesota Department of Human Services
http://mn.gov/dhs/
Fredrickson Learningfredricksonlearning.com
Accessibility Best Practices for eLearning
Jill StantonLearning Project Manager
December 9, 2015
Lolly LijewskiCommunications Specialist, TTC
Tony TaoSenior eLearning Developer
Code Example
Why Accessible eLearning?
Lolly Lijewski1Communications Specialist, TTCMN Dept of Human Services
Accessibility is important for several reasons:• So content can be seen and understood by all
members of your audience.
• To ensure messages are delivered in a way that everyone can understand them.
• To be in compliance with state and federal laws.
• Web accessibility also benefits different user needs, preferences and situations.
Laws and Standards
• Americans with Disabilities Act http://www.ada.gov/
• Minnesota Statewide Accessibility Standards mn.gov/mnit/programs/policies/accessibility/
These standards are based on Section 508 and WCAG2.0:• Section 508 standards:
http://www.section508.gov/content/learn
• WCAG 2.0 standards: http://www.w3.org/TR/WCAG20/
Principles of Accessibility
Web content, including eLearning, should be:
• Perceivable,
• Understandable,
• Operable, and
• Robust for people with disabilities.
+ + +
Why Make Content Accessible
• These principles put people at the center of the process.
• People with disabilities should be able to contribute to the web.
• Older adults also benefit from web accessibility.
Examples of How People with Disabilities Interact Online
The document How people with disabilities use the web provides examples of stories of the different ways people with disabilities use the web.
Adapting Content for Screen Reader Users
Content includes:
• eLearning modules
• Web pages
• Video (using captions and audio description)
• Forms
Project Approach for Accessible eLearning
Jill Stanton2Project ManagerFredrickson Learning
Getting Started
• Design for accessibility from the beginning
• Get familiar with WCAG and 508 standards:– Review standards– Talk with experts – Google “accessible
eLearning” for tips and advice
Getting Started
Align team on interpretations:
• What level is goal?
• How interpret standard?
• Make checklist
Example from WCAG: All non-text content that is presented to the user has a text alternative that serves the equivalent purpose, except for several situations, including:
• Content for pure decoration, which may be skipped.
• Content to create a sensory experience, which should have identifying description.
Personas
Create, design and develop to personas:
• Effective way to put human face on requirements
• Design to and reference them throughout the project. “Does that work for Ann?”
• Include name and attributes like:– Typical day– How access eLearning– How will use what they learn – Biggest challenges
Key Messages
Important to providing an “equivalent learning experience”
Great communication leads to team success
The Eagles win against the Bears!
Beyond Content
Navigation
Attachments
Login/Launch
Testing
• Test, but do not be your only tester
• Work with experts when you can
• Clearly define who will approve
• Integrate accessibility into Quality Assurance testing
• Complete Quality Assurance testing prior to accessibility testing
This Sounds Difficult/Complicated/Expensive
It’s too difficult
This audience
won’t like it.
This takes too
much time!
Nobody’s gonna use it
anyway!
My design process will be
restricted.
Is this really
necessary?
We don’t have the budget.
2 Key Messages About Creating Accessible Learning
Accessible Learning is Good Learning:• Learner-centered
• Provides clear content/key messages tied to learning objectives
• Integrates all elements to support content/messages
Planning accessibility from the beginning: • Avoids re-design/re-work later, saving time and
money
• Gets your message/content to all learners
• Complies with the law
1
2
Project Approach for Accessible eLearning
Tony Tao3Senior eLearning DeveloperFredrickson Learning
Rapid eLearning Tools Review
ToolsAccessibility Support
Captivate 7 and higher
Full support on WCAG AA
Storyline 2 update 5+
Full support on WCAG AAAdd summary?
Articulate Studio ‘13
Limited support on 508 Transcript, not tabs
Develop Accessible Components
Include:
• Adjust tab order
• Pace objects in correct sequence
• Remove unnecessary objects
• Add visual/audio cues for interaction
Best Practices for Development
• Do not use variables to feed content
• Pause the project audio for screen reader
• Do not blend graphic and text
• Interaction elements that are not accessible:– Rollover– Drag and drop– Widgets– Smart Shape buttons