When I publish a Storyline file for the web, I get Missing Form Label & Empty Button accessibility errors in WAVE. The powers that be where I am employed will not publish the course until these are addressed. Anyone know how to fix these? I'm a bureaucrat so have pretty strict accessibility standards.
Thank you for sharing the screenshot. An empty button errormeans one of the buttons in your Storyline course has no descriptive text. It would be helpful to take a closer look at your .story file to investigate which slides, in particular, are causing those errors.
If you're comfortable sharing your file, feel free to upload a copy here in the discussion or privately through a support case. We'll delete it from our system as soon as we're finished!
Steven, thanks for the speedy reply. I've attached the Storyline file here. By the way, this is an issue with all the Storyline projects, so not just this one. Thanks!
Thanks for sharing a copy of your project file. Without changing anything, I published and uploaded it to a webserver and then tested it in WAVE and here are the results that I got:
Notice that I did not get any error messages for your course. Here's the link that I used for testing. Would you mind testing the link that I shared in WAVE again to see if you get similar results as mine? Additionally, you can check out this list of Web Accessibility Evaluation Tools from W3.org if you'd like to do some testing using other accessibility testers to improve the accuracy of your tests.
Apologies for the broken link. Here's a link that works so you can check it out. As for the second link that you shared, here's the report that is returned when I run the same link in WAVE:
No errors were detected for this course as well. Can I ask if you've tried using other browsers to run your tests? I'm curious if doing so will result in a different accessibility report for your courses.
I published your course for Web distribution so the settings that I used were the default ones.
Have you tried using other accessibility tools to compare the results? You might be getting errors only in a single accessibility testing tool. I'd recommend using other tools to evaluate your course and checking to see if the errors consistently appear there as well.
Thanks for the reply! I indeed did use another web accessibility tool, Axe DevTools (W3C-approved), and it didn’t throw the Missing Form Label or Empty Button errors. Unfortunately, my agency (Massachusetts Department of Elementary and Secondary Education) uses WAVE, so even though they said I could use another, they don’t seem to be accepting those results quite yet.
The bigger question is why you all aren’t getting the errors in WAVE when I am. I’m perplexed! ☹
You can try testing using other browsers to see if this makes a difference. Other tests that you can do is to test while your browser is in incognito/private mode just in case some add-on is causing the behavior for you.
storyline courses are not normal html pages, storyline is a single page app
i looked at "WAVE" and didn't find any hint that it could test single page apps - there must be tested completely different (a test for a 1 hour course would be > 1 hour)
if this is true, "WAVE" is not at all suitable to judge storyline courses
does anyone know a tool to test Single Page Apps for find Accessibility Errors?
I went ahead and opened a support case on your behalf so we can have our support engineers assist you with your accessibility testing. I've already shared details of your case with them, and someone will be reaching out shortly via email with the next steps for troubleshooting.
14 Replies
Hi Bobby!
Happy to help with this!
Thank you for sharing the screenshot. An empty button error means one of the buttons in your Storyline course has no descriptive text. It would be helpful to take a closer look at your .story file to investigate which slides, in particular, are causing those errors.
If you're comfortable sharing your file, feel free to upload a copy here in the discussion or privately through a support case. We'll delete it from our system as soon as we're finished!
Steven, thanks for the speedy reply. I've attached the Storyline file here. By the way, this is an issue with all the Storyline projects, so not just this one. Thanks!
Hello Bobby,
Thanks for sharing a copy of your project file. Without changing anything, I published and uploaded it to a webserver and then tested it in WAVE and here are the results that I got:
Notice that I did not get any error messages for your course. Here's the link that I used for testing. Would you mind testing the link that I shared in WAVE again to see if you get similar results as mine? Additionally, you can check out this list of Web Accessibility Evaluation Tools from W3.org if you'd like to do some testing using other accessibility testers to improve the accuracy of your tests.
Let me know how it goes!
Thanks Joe. Getting this error when selecting the link:
This XML file does not appear to have any style information associated with it. The document tree is shown below.
AccessDeniedAccess Denied
CGWHTJV5V4EXNSGY
XRyAg5MgpZtgaqVjGh0uiG+xOFTFYt42AMtgizh7LtXZLyfrifvk/aZKPNAgtEe0yUv3KG3VLIw=
Joe,
Might you be able to put the published ZIP file somewhere where I can download it? I can then upload it to my test server.
Also, you can see another course of mine that has the same errors here:
https://www.doe.mass.edu/rlo/worldlanguages/module1/story.html
Maybe you could select that and see if you get the same errors I am.
Thanks!
Bobby Earle
Hello Bobby,
Apologies for the broken link. Here's a link that works so you can check it out. As for the second link that you shared, here's the report that is returned when I run the same link in WAVE:
No errors were detected for this course as well. Can I ask if you've tried using other browsers to run your tests? I'm curious if doing so will result in a different accessibility report for your courses.
Quick question: I wonder if you would send me the Publish settings in Storyline. Maybe there’s something in there that is causing the error.
Thanks,
Bobby Earle
Hello Bobby,
I published your course for Web distribution so the settings that I used were the default ones.
Have you tried using other accessibility tools to compare the results? You might be getting errors only in a single accessibility testing tool. I'd recommend using other tools to evaluate your course and checking to see if the errors consistently appear there as well.
Thanks for the reply! I indeed did use another web accessibility tool, Axe DevTools (W3C-approved), and it didn’t throw the Missing Form Label or Empty Button errors. Unfortunately, my agency (Massachusetts Department of Elementary and Secondary Education) uses WAVE, so even though they said I could use another, they don’t seem to be accepting those results quite yet.
The bigger question is why you all aren’t getting the errors in WAVE when I am. I’m perplexed! ☹
Thanks!
Bobby Earle
Hi Bobby,
You can try testing using other browsers to see if this makes a difference. Other tests that you can do is to test while your browser is in incognito/private mode just in case some add-on is causing the behavior for you.
Unfortunately, I’m getting the errors in all browsers and also in incognito mode. It’s very frustrating.
storyline courses are not normal html pages, storyline is a single page app
i looked at "WAVE" and didn't find any hint that it could test single page apps - there must be tested completely different (a test for a 1 hour course would be > 1 hour)
if this is true, "WAVE" is not at all suitable to judge storyline courses
does anyone know a tool to test Single Page Apps for find Accessibility Errors?
Hi Bobby,
I went ahead and opened a support case on your behalf so we can have our support engineers assist you with your accessibility testing. I've already shared details of your case with them, and someone will be reaching out shortly via email with the next steps for troubleshooting.
Thanks!!!! 😉