ELB Lectora Accessibility Issues with Jaws

We’re currently developing an online course in Lectora Online with AAA (triple-A) accessibility requirements. After delivering the course to our client as a SCORM package for integration into their LMS, they reported several issues when testing the content with JAWS.

We’d like to share these issues with the community to see if anyone has encountered something similar or can suggest possible solutions.

Issue 1: Redundant reading of navigation buttons by JAWS

When using JAWS, the Previous and Next navigation buttons are read up to three times.

We believe this may be happening for one (or more) of the following reasons:

• JAWS reads the different states of the buttons (initial read, when focus/hover is placed on the button, and again when the button is activated).
• JAWS may be reading the buttons once during the initial page load, and additional times from the side panel / titles explorer.

Our questions are:

• Is there a recommended way in Lectora to prevent screen readers from announcing the same navigation buttons multiple times?
• Are there best practices for managing button states or focus behavior to avoid redundant announcements?
• Has anyone experienced similar behavior with JAWS and found a reliable workaround?

Issue 2: Erratic interaction in multiple-choice questions when using JAWS

In multiple-choice questions, when navigating with JAWS, there does not appear to be a clear or intuitive keyboard command to validate or confirm a selected option.

Currently:

• Users navigate both between questions and between answer options using the Up and Down arrow keys.
• This makes the process of selecting and confirming an answer confusing and unintuitive for users with visual impairments.

Our questions are:

• Is there a recommended interaction pattern in Lectora to improve keyboard-based validation of multiple-choice answers?
• Can this behavior be customized to make answer confirmation clearer for screen reader users?
• Are there known limitations or accessibility settings related to question validation with JAWS?

Issue 3: Help button moves to the bottom at high zoom levels

We have included a Help button that displays a text block when clicked. On screens where the zoom level is between 200% and 400%, this button moves arbitrarily to another position, often toward the bottom of the screen.

This causes:

• Overlapping elements
• Blocked navigation
• Inability to advance to other slides

Our questions are:

• How can we review or adjust the configuration of this button in Lectora to ensure stable positioning at high zoom levels?
• Is it possible to enforce relative positioning via CSS to prevent this behavior?