Solved

Inheritance and Reading Order

Hi Everyone,

I'm using Lectora Desktop 21.3, and to avoid repeating a Close button for several pop-up windows, I placed the button at the top of the tree and it automatically appears in all pages in this tree (see snapshot below). However, this feature causes a compliance issue with 508 because of the reading order. 

As shown in image2, the Close button receives the focus as the first clickable element in the page, but there are other elements that should be clicked before the user reaches to the Close button. 

Is there a remedy for this? How do I maintain the proper reading order, so that the Close button receives the focus last?

Solution

You can use Set Reading Order to Last after putting the button in a group.

More here

Discussion (4)

Thanks a lot "wheels", easy and simple fix! How come it didn't occur to me:)

I put the Close button in a group and tested it, it worked perfectly well, hopefully, it will pass the compliance too.

Many thanks!

No, not at all, your message and links were very helpful.

Many thanks again!

Glad I could help and sorry for the terse reply was from my phone!

It isn't very obvious as you have found out.

Hopefully you will find some other helpful items in the article

How to Use Lectora to Create Accessible Courses

.

You can use Set Reading Order to Last after putting the button in a group.

More here