Forum Discussion
Tab key needs to be hit twice to move to next button
Hi. I have a course with all custom buttons. My buttons have two States, Normal and Hover. When I Preview the course and TAB through the buttons it takes two hits of the TAB key to go from button to button vs one hit. Anyone have a fix for this?
Hi Russ,
I appreciate you reaching out to share what you are experiencing with your custom buttons.
- How were these created?
- Is it multiple shapes to create the button, and the screen reader may be selecting an additional item?
I'd recommend double-checking the alt text of the items:
Storyline 360: Adding Alternative Text for Screen Readers
If you need any help, feel free to attach a slide to your reply here, and we can take a look.
- RussLickteigCommunity Member
Hi Leslie,
The screen shot below shows the State for the Next button. All of my buttons have two states with a single SVG file for each state. Not multiple items.
Another issue I just noticed is that when I publish the course to the Review page to share with people the text is changing from standard weight to a bold weight. I assume this is an SVG bug? Do I have to do anything in post publishing with SVG items like this?
- RussLickteigCommunity Member
Hi Leslie,
This looks to be an issue with SVGs being used for States. I just add a standard button from SL and a button with PNGs for each state. Both of these buttons worked as they should. One TAB. Is this a bug? I truly love how great SVG buttons look.
- RussLickteigCommunity Member
Hi Leslie,
More research here. I just created a new button from SVGs and it works fine. The buttons I am having issues with originally had PNG files as States but I "replaced" the images for each state with SVG files. Apparently, that does not work. I assume this is a bug? Now I have to go in and create all-new buttons. Can you confirm if this is a known issue?
- MariaCSStaff
Hi, Russ.
Thank you for the additional information!
Would it be possible to share the .story file with our support team so we can investigate this further?
- RussLickteigCommunity Member
Maria...I reached out and Cleo Sinues looked at a file of mine. He could not recreate the problem I was having. It seems at its simplest fix is to never create a button with PNG states and then switch them to SVGs.