Prev and Next Buttons Accessibility with jaws reader

Hi Teresa!

Thanks for your question, and I'm happy to help you here!

First, let's tackle the screen reader announcing the project title on every slide. Do you need to project title in the player? If not, you can turn it off in Player properties, and that will prevent JAWS from reading it again with each new slide.

Now, on to the previous/next buttons. As you mentioned, when you press the Tab key after the last object on the slide, the screen reader will instruct you to press the spacebar or Enter key if you want to skip player navigation.

If you don't press the spacebar or Enter key, your next tab should proceed to the player navigation, starting with the previous and next buttons, but it sounds like that isn't happening for you.

Can you tell me a bit more about the project and how you tested the published output? 

• What version of Storyline are you using?
• Did you host it on a web server or on a LMS?
• What web browser did you use for testing?

HI Alyssa,

You are right I do not need the Title on the Player so I will find it and turn it off.

Yes it says press spacebar or enter to skip, and then it just doesn't do anything.

I am using Articulate Storyline 360 the latest version.  It hasn't gone live yet, but I did load it into our LMS Test environment (Peoplefluent is the name of the LMS).  I was using Chrome as my browser.

Cheers

Teresa

Ashley, can I add I don't actually understand the comment when Jaws says to press spacebar or enter to skip navigation...why would someone skip navigation, don't they want to go to Next button etc....it really confused me every time I heard it...not that that is a storyline issue but in case you know...

Ashley, We're currently checking JAWS to see what it reads now however, our trusted tester person checked 2 courses and says the navigation buttons are failing. One of the recent updates made to Storyline seems to have broke how they are identified. I should have the JAWS test back early today.

Thanks Bob, this is good to know, as I couldn't see anything I was doing wrong, Jaws just won't move to the prev or next button...again I am assuming I hit Tab to get to them but couldn't get it to work.

Our testing program is showing this if it helps:

Name:  "IDIQ Task Order Evaluation"
LegacyIAccessible.Name:    "IDIQ Task Order Evaluation"
LegacyIAccessible.Role:     pane (0x10)
LegacyIAccessible.State:    focused,read only,focusable (0x100044)
LegacyIAccessible.Value:    "https://articulateusercontent.com/review/items/k9qSJ7nzSr0whGH6/story_html5.html?wmode=opaque"

Its reading all the navigation buttons with the name of the course. It use to ID the buttons by name, Next, Prev, etc.

It will move there - however,  I'm not sure what it will currently say. I have our JAWS testing person looking at it today. Our other Section 508 test showed that the recent Storyline update(s) broke how the buttons are seen.

Ashley - Can you pass this along?

Hi Teresa,

A user may want to skip player elements like the menu, player tabs, and navigation buttons if they want to cycle back through slide objects. 

Without seeing your file, I'm not sure what would cause the tab order to get "stuck" once it reaches the player elements. Would you mind sharing a sample of your file with me?

You can attach it directly to a new thread comment by clicking the Add Attachment button. 

Sure I don't mind attaching.  Hope you don't mind it is just easier if I attach the full course, nothing secretive here....

Please note, I have a lot of work to do on Tab order...If you look at the current Landscape section the tab order is in better shape.  Except for the Table, that is another issue submitted to Articulate, there is a bug when trying to fix Tab order in a table system crashes, they have reported it.

Bob, for me I guess I expected me to Tab and it would say Prev button, then I would tab gain and it would say Next button and then I would hit enter, but nothing works... :(

Tables are not truly 508. You need to add alt text to put everything in context. Storyline simply ideas the cells as 0/0, 0/1, 0/2, etc.... location based vs what the cell represents. It reads the cells fine but there's no correlation for the info. For the example, you don't know that the money amount listed $17,000 is related to the "Offer" column.

Here's an example of what JAWS does with a Storyline table:

JAWS reads: "Table with four columns and four rows. [Tab]. [Tab] Type Offer. [Tab] Offer. [Tab] Delivery Time. [Tab] A. [Tab] Domestic offer from a large business. [Tab] Dollar 17 thousand. [Tab] 2 weeks. [Tab] B. [Tab] Nonresponsive offer. [Tab] Dollar 15 thousand. [Tab] 1 weeks. [Tab] C. [Tab] Offer of a foreign end product from a small business. [Tab] Dollar 16 thousand 5 hundred. [Tab] 3 weeks.

One more... for some reason, you can't put hyperlinks in the cell text either.

Wow Bob, thanks for the tips, and the example.