Blog Post

Discover
1 MIN READ

Rise 360: Implementing WCAG Guidelines for Instructional Designers

CommunityTeam's avatar
CommunityTeam
Staff
3 years ago

Whether you’re required to build accessible e-learning or just trying to do the right thing, applying the WCAG standards results in a better learning experience—for everyone. But with so many guidelines, how do you know where to start? Not to worry! We’ve put together this Rise 360 resource to help guide you on your journey to creating fully accessible e-learning—including tips for implementing WCAG guidelines using Articulate apps. We hope this asset makes it easier for you to apply the guidelines so you can create enjoyable and empowering learning experiences for every learner. 

Feel free to bookmark this resource so you can reference it later, or send yourself a copy to add to your Rise 360 dashboard. If you don’t have access to Rise 360, sign up for a free 30-day trial of Articulate 360.

Published 3 years ago
Version 1.0
accessibility
Articulate 360
Example
  • TomBuckley's avatar
    TomBuckley
    Community Member
    3 years ago
    This is helpful but I feel there has some omissions. I would probably add :

    1. Don't embed from storyline. It invariably can be done natively in Rise and every example I have seen works badly with a keyboard navigation. If you are embedding a lot then I would question your choice of approach.

    2. Use of space. Space can help differentiate content. Too much space can require a lot of mouse work. Even for people without issues in their hands this can add unnecessary strain
  • PatrickShippelt's avatar
    PatrickShippelt
    Community Member
    3 years ago
    What a great resource! Defiantly saving this for later. I love that you used the Articulate lesson to relay the learning to us!
  • GeorgePetrov888's avatar
    GeorgePetrov888
    Community Member
    3 years ago
    Let's just stop filling our courses with useless information - and get to the point straight up. We're killing eLearning.
  • SethMerriam-55b's avatar
    SethMerriam-55b
    Community Member
    3 years ago
    This information is great, thanks for pulling it together.

    I do have a related question though: What is everyone's experience trying to review the material with JAWS or VoiceOver? I don't find it to be impossible, but it's still not working as I had hoped. Perhaps I'm using it wrong, but I still hear "blank" a lot, and also find commands be hit or miss. For example the commands to read continuously in JAWS only read a very little bit and then stop, but the same command in VoiceOver reads pretty much everything. I'd love to hear if folx have tips (i.e. let me know if I'm just not doing it correctly). I used these commands for JAWS: (https://dequeuniversity.com/screenreaders/jaws-keyboard-shortcuts#jaws-getting_started), and these for VoiceOver: (https://dequeuniversity.com/screenreaders/voiceover-keyboard-shortcuts).
  • MarvieYap-Mulde's avatar
    MarvieYap-Mulde
    Former Staff
    3 years ago
    Hi Seth!

    I am not a JAWS expert but I hope I can shed some light!

    Some screen readers like JAWS may announce "blank" when it encounters an empty block element in the HTML. This is quite normal, and I believe most screen reader users have accustomed to ignoring this.

    I'm curious to know what you are trying to read continuously and which shortcut you are using so I can compare it with my experience. What I can imagine is you are reading a paragraph, but then JAWS would stop at one point without completing it. I believe there's a maximum length it reads, and is configurable in its settings. Do tell!

    Regards,
    Marvie