Is there an accessibility checker made specifically to test Storyline/eLearning courses? I've tried Accessibility Insights and WAVE but it seems those were made to test a normal website. A Storyline output is an HTML5 file but it is a self-contained product, not a website.
Hello. Is an Accessibility Checker for e-learning content, especially Storyline, in the pipeline? Even if it were very basic, it just needs to show the content developer if what they are doing is going to be accessible to people with varying disabilities. The list of tools in a previous post is mostly for web pages. This has become a real need for many educational institutions that are presenting more courses on line. Thanks.
Thank you for checking in. That's a great conversation to have!
We don't have an Accessibility Checker that we support at this time, but I recommend starting with the resources below. They cover important design considerations and discuss key Storyline 360 features for creating accessible courses:
I have read some of the Articulate resources and others.
Using a screen reader is excruciating to hear even if all the tabs are in the proper order. After one week, we are going with Plan B: Typing slide information into a Word document then cutting and pasting each slide's description into the associated slide.
The Tab Order procedures does help with people unable to use a mouse because they can "tab" to navigate and "enter or space bar" to activate the button (if there is a button).
This approach is acceptable to our disability resource group for a mandatory training that has to go live next week.
Maybe Articulate can work with Java and other screen readers to improve the experience for non-sighted people.
I appreciate the suggestions. They have helped.
EHS Office in COSE
San Francisco State University
1600 Holloway Avenue
San Francisco, CA 94132
415.338.6892 (office)
415.338.7507 (office alternate)
It's really important to have an accessibility checker built into Storyline and Rise because we need something definitive to promise our clients. We can't tell them we are able to meet 508 or Level AA or any specific requirement because we'd basically have to consult with an agency that specializes in auditing web content for accessibility to guarantee our clients that. What I would like to be able to say is "We are knowledgable about accessibility, we will make a good faith effort to make your site conform within the constraints of the platform, and we will ensure it passes Articulate's accessibility checker."
Thanks for your response. Designing for accessibility is not the same as checking it though. Hopefully, Articulate will realise the importance of this and put it into progress.
Thank you for sharing your perspective on such an important topic. I'll be sure to share your feedback with my team and update this discussion on our progress. Should you need anything in the meantime, please let me know!
It would really be great to incorporate an accessibility checker for Storyline and Rise. I hope this very important function will be added to future updates.
Ironically, I came to this forum because I just started checking out the options for Storyline or Rise as platforms to develop microtrainings for faculty at my institution. The subject? Designing accessible courses to support students with disabilities. I'm so suprised that there are no Accessibility Checkers in products I'd hoped to use to create my training.
I appreciate you taking the time to share what you’d like to see in Storyline 360 and Rise 360. We currently have to add an accessibility checker logged as a feature request, so I’ll go ahead and include your voice in that request. We’ll update this discussion if this feature makes it on our feature roadmap.
Thank you so much for your response! I'm sure it's challenging to build an
accessibility checker into such a complex and comprehensive platform, but
it will pay off down the road.
And compliments to the accessible design tutorials that are available for
Articulate users. They're a good way to bring accessibility to the
foreground for designers so they can think about accessibility from the
start.
As above, please keep us posted with progress on an accessibility checker, as I fear we will not be compliant with our digital learning for those with additional needs.
Should we form some sort of committee or have a check in established to get updates on the development of this feature? I'd love to be involved in the conversations that are occurring about this checker.
I'm keeping a pulse on this and wanted to know if there are any updates to dev or beta testing for this feature? We're getting deep into development of some eLearnings at Amazon Pharmacy and QA and accessibility review is built into our workflow. This feature would save so much time for us. Any updates would be greatly appreciated.
Thanks for checking in on this! There currently hasn't been any movement on this as we prioritize other feature requests. I'm going to include your voice in the request. We’ll update this discussion when there is any news to share about this.
Thanks for including this feature in the future development roadmap; it may be a complex feature to build but I am sure it has moved to the must-have from the would-have category by now. Look forward to using it soon.
Hi there, I'd like to request an accessibility checker also. I'm really surprised this hasn't been priortised as yet, considering the legal implications of failing to provide accessible content for so many educational providers. I understand that it's complex but with similar features available in LMSs and across Office products, and the developments in AI that can be utilised here, I would imagine that it is achievable. Are there any developments as yet?
Welcome to E-Learning Heroes! I understand you would like to see an accessibility checker added to Storyline 360. There are any new developments to report on this feature but I'll add your voice to the existing feature request. We’ll update this discussion if there’s any news regarding this feature.
If you’re wondering what happens when you submit a feature request, here’s our process:
Feature requests start with our customer support team. First, we check if there’s already a way to do what you’re asking. If there is, we’ll let you know. If not, we go to step 2.
We consider the value this potential new feature would offer to our customers. We ask ourselves:
Will this feature meaningfully improve the experience of working with our software?
Will it benefit a majority of users?
If we feel like the answer is “yes!”, we bring the request to our product development team.
Our development team evaluates feature requests alongside their queue of bug fixes, new features already on the roadmap, and other projects. If a new feature makes it onto the roadmap, our team designs, develops, and tests it. And when it’s ready, we share the good news!
These are great criteria for new features! I think an accessibility checker fits the bill perfectly. The meaningful improvement to our experience as developers, not to mention how this helps us make better content for our clients/constituents. *chef's kiss*
Please add me to the voices requesting an accessibility checker.
48 Replies
Hi Crissy!
We don't currently have an Accessibility Checker that we support, but I did find this list of Web Accessibility Evaluation Tools from W3.org!
Let me know if there are any tools that stand out to you as you check your course!
Hello. Is an Accessibility Checker for e-learning content, especially Storyline, in the pipeline? Even if it were very basic, it just needs to show the content developer if what they are doing is going to be accessible to people with varying disabilities. The list of tools in a previous post is mostly for web pages. This has become a real need for many educational institutions that are presenting more courses on line. Thanks.
Hi Linda!
Thank you for checking in. That's a great conversation to have!
We don't have an Accessibility Checker that we support at this time, but I recommend starting with the resources below. They cover important design considerations and discuss key Storyline 360 features for creating accessible courses:
Also, Storyline 360 courses work with JAWS 16 and later, NVDA, VoiceOver, and TalkBack.
Let me know if that helps. I'm happy to discuss further!
Hello
I have read some of the Articulate resources and others.
Using a screen reader is excruciating to hear even if all the tabs are in the proper order. After one week, we are going with Plan B: Typing slide information into a Word document then cutting and pasting each slide's description into the associated slide.
The Tab Order procedures does help with people unable to use a mouse because they can "tab" to navigate and "enter or space bar" to activate the button (if there is a button).
This approach is acceptable to our disability resource group for a mandatory training that has to go live next week.
Maybe Articulate can work with Java and other screen readers to improve the experience for non-sighted people.
I appreciate the suggestions. They have helped.
EHS Office in COSE
San Francisco State University
1600 Holloway Avenue
San Francisco, CA 94132
415.338.6892 (office)
415.338.7507 (office alternate)
An Accessibility Checker for Storyline would be the best thing ever! Articulate, has there been any progress on this?
Hi, Jeanne!
Thanks for checking in on this subject!
Currently, we don't have an accessibility checker we support. I'll be happy to pass your thoughts on to our product team about this.
In the meantime, I would refer to the previous posts in this discussion for a bounty of resources on accessibility.
It's really important to have an accessibility checker built into Storyline and Rise because we need something definitive to promise our clients. We can't tell them we are able to meet 508 or Level AA or any specific requirement because we'd basically have to consult with an agency that specializes in auditing web content for accessibility to guarantee our clients that. What I would like to be able to say is "We are knowledgable about accessibility, we will make a good faith effort to make your site conform within the constraints of the platform, and we will ensure it passes Articulate's accessibility checker."
Yes. Totally agree Anne.
Hi John
Thanks for your response. Designing for accessibility is not the same as checking it though. Hopefully, Articulate will realise the importance of this and put it into progress.
Hi Anne and Jeanne,
Thank you for sharing your perspective on such an important topic. I'll be sure to share your feedback with my team and update this discussion on our progress. Should you need anything in the meantime, please let me know!
It would really be great to incorporate an accessibility checker for Storyline and Rise. I hope this very important function will be added to future updates.
Hi Tamiya,
Thank you for your feedback! I'll add your comments to this request for an accessibility checker.
Any updates on an Accessibility Checker? All industry - standard tools should have this. Is it on an upcoming roadmap?
Ironically, I came to this forum because I just started checking out the options for Storyline or Rise as platforms to develop microtrainings for faculty at my institution. The subject? Designing accessible courses to support students with disabilities. I'm so suprised that there are no Accessibility Checkers in products I'd hoped to use to create my training.
Hi Mary-Colleen,
I appreciate you taking the time to share what you’d like to see in Storyline 360 and Rise 360. We currently have to add an accessibility checker logged as a feature request, so I’ll go ahead and include your voice in that request. We’ll update this discussion if this feature makes it on our feature roadmap.
Thanks for reaching out!
Hi, John.
Thank you so much for your response! I'm sure it's challenging to build an
accessibility checker into such a complex and comprehensive platform, but
it will pay off down the road.
And compliments to the accessible design tutorials that are available for
Articulate users. They're a good way to bring accessibility to the
foreground for designers so they can think about accessibility from the
start.
Mary-Colleen
Hi,
As above, please keep us posted with progress on an accessibility checker, as I fear we will not be compliant with our digital learning for those with additional needs.
Many thanks in advance
Should we form some sort of committee or have a check in established to get updates on the development of this feature? I'd love to be involved in the conversations that are occurring about this checker.
Hi Everyone,
I'm keeping a pulse on this and wanted to know if there are any updates to dev or beta testing for this feature? We're getting deep into development of some eLearnings at Amazon Pharmacy and QA and accessibility review is built into our workflow. This feature would save so much time for us. Any updates would be greatly appreciated.
Hi Holly,
Thanks for checking in on this! There currently hasn't been any movement on this as we prioritize other feature requests. I'm going to include your voice in the request. We’ll update this discussion when there is any news to share about this.
Thanks for including this feature in the future development roadmap; it may be a complex feature to build but I am sure it has moved to the must-have from the would-have category by now. Look forward to using it soon.
Hi there, I'd like to request an accessibility checker also. I'm really surprised this hasn't been priortised as yet, considering the legal implications of failing to provide accessible content for so many educational providers. I understand that it's complex but with similar features available in LMSs and across Office products, and the developments in AI that can be utilised here, I would imagine that it is achievable. Are there any developments as yet?
Hi Sue,
Welcome to E-Learning Heroes! I understand you would like to see an accessibility checker added to Storyline 360. There are any new developments to report on this feature but I'll add your voice to the existing feature request. We’ll update this discussion if there’s any news regarding this feature.
In the meantime, here is some information on how we manage feature requests.
Thanks for reaching out!
If you’re wondering what happens when you submit a feature request, here’s our process:
Feature requests start with our customer support team. First, we check if there’s already a way to do what you’re asking. If there is, we’ll let you know. If not, we go to step 2.
We consider the value this potential new feature would offer to our customers. We ask ourselves:
If we feel like the answer is “yes!”, we bring the request to our product development team.
Our development team evaluates feature requests alongside their queue of bug fixes, new features already on the roadmap, and other projects. If a new feature makes it onto the roadmap, our team designs, develops, and tests it. And when it’s ready, we share the good news!
These are great criteria for new features! I think an accessibility checker fits the bill perfectly. The meaningful improvement to our experience as developers, not to mention how this helps us make better content for our clients/constituents. *chef's kiss*
Please add me to the voices requesting an accessibility checker.
Please add me to this list! A accessibility checker would be an incredible tool!