Accessibility and screen readers

Hi Angela,

Thanks for reaching out and sharing your questions about screen readers.

Anyone know how to remove the 'back to top' button when tabbing through? 

The skip navigation shortcut is enabled by default, and we recommend keeping it enabled. However, you can turn it off should you need to do so. See this user guide for details.

• Also, in case you're not familiar with this behavior, I wanted to share this information as well:
  • Storyline 360: How to Use the Skip Navigation Shortcut

Arriving on a slide and it sometimes says "blank", but using the arrow keys will prompt it to read the content.

Does your slide have a title when you're hearing this? If you have an example, we'd be happy to take a look. I know this was an issue that JAWS recently addressed in their software and Lauren talks about it here.

The arrow keys are how you navigate the text on the page, so this sounds like expected behavior.

Storyline 360: Slide Content Is More Accessible

"Clickable main landmark slide" before reading content sometimes. Anyone else get this? or know what is behind it saying that? 

This is an ARIA landmark. Screen reader users are able to understand items on the screen and navigate to them using them.

Simon mentions it here:

Recent accessibility improvements in Storyline 360

Hope this helps you get started in understanding how screen readers work. Let us know if you have any additional questions.

Thank you. This is really helpful.

I understand that the arrow keys are used to move through the content, the thing that didn't seem right however was that it would read part of sentences and need an arrow prompt to continue. I thought it would read all of what was in a text box. It's almost like there are line breaks or something in the text. Is there a way to see or change how text is structured to stop this from happening??

Also is there more information about ARIA landmarks? Is it possible to see them / edit them for the slides?

I am new to screenreaders so anything to help me understand how they work will be helpful. Is there any training you know about?

Hi Angela!

Great questions! 

Why does a screen reader stop reading in the middle of a sentence?

By default, NVDA will stop reading after 100 characters, and JAWS stops reading after 150 characters. If you want to change this setting in NVDA, head over to the Browse Mode settings and alter the Maximum number of characters on one line.

Here's what it looks like:

We don't currently offer a way to edit ARIA Labels and Landmarks in Storyline 360. You'll find that our current roadmap is filled with accessibility updates, and semantic structure is one of the upcoming features! 

Lastly, there are many resources out there. One of my favorites is Deque University!

Hi Team, I am finding that NVDA is reading the Storyline slide name as well as the "main landmark" which happens to be the same ie NVDA is reading the same thing twice and is becoming quite repetitive for every slide. Any ideas on how I can work around this?

eg:

NVDA first arrow click: " Slide 'Workbook and activities' "

NVDA second arrow click "Main landmark 'workbook and activities'

PS:I've also had to remove all 'Heading' configuration to text to prevent NVDA also reading these as 'Heading 1:Workbook and activitites' (which would mean reading the same thing 3 times: slide name; landmark and Heading).

I've also removed the Text Box 3 "Workbook and activities" from the focus order.

Hello Susan,

Thank you for reaching out and sharing what you are experiencing when using a screen reader.

With your permission, I'd like to take a look at your project file to investigate what's happening. You can share it publicly here, or send it to me privately by uploading it here. I'll delete it when I'm done troubleshooting.

Hi Leslie, thank you. I clicked on your 'here' link and have privately uploaded the file. Thank you.

Hi Leslie,  Another issue regarding the above Storyline 360 file I just privately uploaded. You can refer to slides 2.4 and 2.5 as a couple of examples.

Accessible Text Boxes: NVDA is announcing text boxes on slides as "clickable".  

The text box is just that a 'text box', and not supposed to be clickable.

It is inconsistent so not happening in every slide. Any ideas on how I can work around this?

Thanks

Thanks, Susan. I just replied to you privately via email.

Hi Leslie, I am also facing the same issue as : "Susan Khamis"  mentioned above.

Accessible Text Boxes: NVDA is announcing text boxes on slides as "clickable".  

Is there any way to remove or disable it? 

I am working on my very 1st course, and I just downloaded NVDA to review it.  None of my slide titles get read.  None of my text boxes are getting read.  I am so frustrated.  Help?