ReadSpeaker app not available on welcome page
ESYD.C.1573
Posts: 2 🔍
Hi there,
Our ReadSpeaker app is not linking to the first slide on each course. Is this because it's html? This has been noted by our user testers and is a huge accessibility issue. Not to mention the additional money that we paid for this add-on. Can this be fixed?
Answers
-
Hi @ESYD.C.1573
It sounds like ReadSpeaker might not be recognizing the first slide of each course due to how the content is structured in HTML. Here are some things to check:
- Content Loading Issue – If the first slide is dynamically loaded using JavaScript or if it's within an iframe, ReadSpeaker might not detect it properly.
- HTML Markup – Ensure that the first slide has properly structured text elements (like
<p>
or<div>
) rather than text embedded inside images or complex layouts. - ARIA & Accessibility Tags – Sometimes, ReadSpeaker relies on ARIA roles or other accessibility attributes. Ensure the first slide has proper
aria-label
orrole="main"
if applicable. - ReadSpeaker Settings – Check if there's an option to specify where the reader should start. Some tools allow you to define which content gets read first.
- JavaScript Conflicts – If other scripts are running on the first slide, they might be interfering with ReadSpeaker’s ability to detect and process the text.
To confirm whether this is an HTML issue, try:
- Copying the first slide’s HTML and pasting it into a blank HTML file to see if ReadSpeaker works on it.
- Checking if ReadSpeaker functions on other slides normally formatted the same way.
- Inspecting the browser console for errors when loading the first slide.
Since this is a critical accessibility issue, I recommend reaching out to ReadSpeaker’s support team directly.
If needed, you can raise a support ticket to review D2L’s implementation to see if any configurations need adjusting.
Regards,