I just wanted a clear explanation of how the tabbing works in Storyline. It currently seems to pick up everything on screen - even elements that aren't interactive like line graphics. I have also hand created my buttons, rather than using the Storyline ones as the rounded corners really weren't the look I was going for. This unfortunately seems to mean that when you tab to them and select enter, the functions aren't working.
In order to disable this accessibility feature, you'll have to remove the default option for each object. You can find out more information about disabling the default highlighting in this knowledge base article.
Thanks for your fast response - I've now turned off a lot of the highlighting. I'm still having problems with it actually working how I need it to work however. So tabbing to a button and hitting 'enter' doesn't do anything on any of the buttons I have created. Is this because I have created my own from shapes and have not used Storyline's standard buttons? It also seems to add the highlight to the wrong part of every element - too far up. It does this on all elements.
It's quite simple though, there's a grey square which on click, shows a layer. However this doesn't work with tabbing and entering.
This isn't great news unfortunately. I don't want to be restricted to the Storyline buttons as their designs do not suit my project. Is there no way to convert an object to have the functionality of a button such as being tab-able?
Unfortunately, I think the main issue with this is because that particular key is widely used for different functions. Have you considered using a different key? Maybe even the arrow keys, or even the number pad + number pad enter? I'm not sure if the project you're developing has strict requirements to match a specific reproduction of software, etc.
I've been able to create my own shapes, add states to them and target them with the Tab key, but it would take quite a bit of work to make sure hitting it again wouldn't select that same object or all objects again. This gets even more complicated with using the Enter key in conjunction with it. However, what you could do is hide the original layer, I suppose, so targeting that object with Tab again can't occur. I'll keep this on my "desk" today and see if I can play around with it a bit. If I find anything I think may help with this, I'll be sure to share!
If you discover anything, please do let me know and maybe we can find a way to get this to work for you.
I'm so sorry it took me so long to get back to you, we've been a little busier this week. I sat down this morning and took a look at some options for you. I think that using some of the methods I worked with today may help you with the functionality you'd like to use in your courses.
Triggers and layers seem to work fairly well for this. Also, hiding the menu and other target-able objects eliminate the accessibility interference. Since you're wanting to use the same two keys ("Tab" and "Enter") multiple times on the same slide in order to advance to additional objects, adding an object (I used a button and placed it out of sight on the slide) that changes states and triggers with conditions, you can simply make the advancement to a new layer with the next object.
I put together a very quick example together. While I know this isn't the same thing you're trying to do, I'm hoping that you'll be able to incorporate some of this to what you're trying to accomplish, and hopefully it will make your project easier. Note that the animations won't work the same way when you view it again (I'm afraid I didn't have time to get into that), but the functionality will still work with the Tab and Enter keys. Press Tab to start, enter to move on and so on.
Is there an option to remove accessibility globally? I have created a course and to remove the accessibility, I have to individually select the objects in each slide and then remove the Alttext. Is there any other way to do it quickly?
9 Replies
Hi Sally,
In order to disable this accessibility feature, you'll have to remove the default option for each object. You can find out more information about disabling the default highlighting in this knowledge base article.
Let me know if you have any questions!
Hi Christine
Thanks for your fast response - I've now turned off a lot of the highlighting. I'm still having problems with it actually working how I need it to work however. So tabbing to a button and hitting 'enter' doesn't do anything on any of the buttons I have created. Is this because I have created my own from shapes and have not used Storyline's standard buttons? It also seems to add the highlight to the wrong part of every element - too far up. It does this on all elements.
Hope you can help.
Sally
It will probably take quite some work with triggers and such to get this working properly for you.
Are you able to share your course here, or a mock up? Maybe I can take a look and give some suggestions
Thanks!
Ok, thanks. I'm afraid I can't share the files.
It's quite simple though, there's a grey square which on click, shows a layer. However this doesn't work with tabbing and entering.
This isn't great news unfortunately. I don't want to be restricted to the Storyline buttons as their designs do not suit my project. Is there no way to convert an object to have the functionality of a button such as being tab-able?
Thanks,
Sally
Good morning Sally,
Unfortunately, I think the main issue with this is because that particular key is widely used for different functions. Have you considered using a different key? Maybe even the arrow keys, or even the number pad + number pad enter? I'm not sure if the project you're developing has strict requirements to match a specific reproduction of software, etc.
I've been able to create my own shapes, add states to them and target them with the Tab key, but it would take quite a bit of work to make sure hitting it again wouldn't select that same object or all objects again. This gets even more complicated with using the Enter key in conjunction with it. However, what you could do is hide the original layer, I suppose, so targeting that object with Tab again can't occur. I'll keep this on my "desk" today and see if I can play around with it a bit. If I find anything I think may help with this, I'll be sure to share!
If you discover anything, please do let me know and maybe we can find a way to get this to work for you.
Thanks Sally, I hope you have a great day!
Christine
Good morning Sally,
I'm so sorry it took me so long to get back to you, we've been a little busier this week. I sat down this morning and took a look at some options for you. I think that using some of the methods I worked with today may help you with the functionality you'd like to use in your courses.
Triggers and layers seem to work fairly well for this. Also, hiding the menu and other target-able objects eliminate the accessibility interference. Since you're wanting to use the same two keys ("Tab" and "Enter") multiple times on the same slide in order to advance to additional objects, adding an object (I used a button and placed it out of sight on the slide) that changes states and triggers with conditions, you can simply make the advancement to a new layer with the next object.
I put together a very quick example together. While I know this isn't the same thing you're trying to do, I'm hoping that you'll be able to incorporate some of this to what you're trying to accomplish, and hopefully it will make your project easier. Note that the animations won't work the same way when you view it again (I'm afraid I didn't have time to get into that), but the functionality will still work with the Tab and Enter keys. Press Tab to start, enter to move on and so on.
Here's the published version.
I hope you have a great day Sally!
Christine
Is there an option to remove accessibility globally? I have created a course and to remove the accessibility, I have to individually select the objects in each slide and then remove the Alttext. Is there any other way to do it quickly?
Hello Elearning Designer,
There is not a global option to remove accessibility from your course.
You are welcome to share your idea and use-case with our team here.
Thanks Leslie!
This discussion is closed. You can start a new discussion or contact Articulate Support.