Making a scroll bar keyboard accessible

Hi Sandy,

I don't see that this particular issue with scrolling panels and screen readers is resolved, in the sense that if you enabled the scrolling panel for the screen reader or add alt text to it - than it experiences difficulty within the screen reader. If you don't add those items/elements - than it seems to be able to read the text, although the user can't use arrow keys to scroll. I'm not sure what Byron set up to get this working so hopefully he'll be able to share a sample project or additional information with you here. 

Sandy, I know it doesn't mention anywhere that it is, but it is fixed as far as I can see, unless we are talking about a different thing, from what I see it is working

To create a test file

1. Make sure you have the latest update
2. start a new file, insert scroll entry field,
3. insert one or multiple blocks of text
4. Publish - et voila,
5 test by using tab and the arrow keys on the scroll field

- you can now select the scroll entry field with the tab key, which you can then control with the arrow keys, you can give the scroll entry field an alt tag(e.g. use arrow keys or skip this field). the screen reader will read all the text in an element (and?) or the alt tag. Again you can test this, with Jaws screen reader(as an example). 

Inside the scroll entry field you keep the elements visible, if it is an image you can turn of the visibility for assistive tech, else you need to insert text for the alt tags, the screen reader should read out all elements.

I've attached a simple test, just tab through the elements, select the scroll and use, the up and down keys to scroll, you will still have to continue to tab through each elements to read each individual element,

if you really want the screen reader to read the text as one, when the user hits the scroll field (for visually impaired people perhaps?) you will have to place all the text in the scroll entry's alt tag, and disable the alt tags from the elements inside the scroll field, I would probably choose against this, and just ad an instructional alt tag to the scroll field.  

It's up to you, have fun, try it out, if we are talking about the same thing(arrow control on the scroll) it is fixed, maybe because they fixed the sliders, and didn't mention the scroll (similar?) 

thanks, bye

any update on adding accessibility to scroll panels?

Hello Marie,

Sorry that you've run into an issue with this as well.

It looks like the issue with JAWS not reading the object or alt text for scrolling panels is still open with our team.

The contents of the scrolling panel should be read and it looks like Byron has a bit of a workaround above regarding the alt text as well.

If you need our team to take a look at anything, feel free to share here.

Hello Everyone,

I am working on a project and came across a similar type of issue. I am using Articulate Storyline 2.

There is a text entry field where user has to fill in his/her name and a list a country(in a scrolling panel). There are 2 issues which i am facing right now.

1. I want user to write his/her name and then jump to country field after pressing the tab key. Currently I have to press the tab button twice to jump to the country field.
2. I want user to navigate to his/her country from the keyboard up and down arrow button and then the use of Enter key to select his/her country.

I am attaching the file here for your reference for the better understanding. You will find 2 slides where i tried to work with different mindset. In the first slide i tried to work around everything on the base layer and in the second slide i tried to make use of slide layer as well.

Please check the published version before making sure its working.

Thanks

Himanshu Sharma

Hi Himanshu,

Thanks for sharing your file here with us.

I saw the same as you described, and I found that the issues mentioned here with the scrolling panel and accessibility are still open issues for our team to investigate in Storyline 2. 

I did notice that the tab order was correct (in terms of pressing tab twice on your first slide to navigate to the drop down) as there is the additional box of your "white rectangle" that users are technically tabbing to first, even though it's not visible. 

We'll let you know here if there are any updates on this issue, so you're in the right place to stay updated on this bug's progress. 

I've published full HTML5 from 360 and still am not able to keyboard into my scrolling panels to access links within. Has this been resolved yet? My search on this site is not pulling up relevant discussions or articles to the affirmative. Please advise. Thanks.

Hi Tonya!

Thanks for including that link, and I do see the problem you described. Have you tried adding a hotspot on top of the link, with a trigger to open the link when the learner clicks the hotspot? 

Hi,

I just reading this thread that was started 5 years ago. Are scrolling panels with text now keyboard accessible?

From my testing, it looks like it isn't. Can you please clarify.

Thanks,
Mark

I have the same question as Mark.