Jaws doesn't read the feedback layer

Mar 24, 2023

Hello all, 

My team and I are working on developing a course and we have a bit of trouble with getting Jaws to read the feedback layer for knowledge checks. For some reason, once the answer is submitted, Jaws jumps to the title of the course, it reads it twice, then it reads the AR link and only after a long while it lands on the actual feedback layer. However, this doesn't happen when testing with NVDA.
I am attaching an AR link, as well as a published version. I have done my research here and I got to a couple of posts where the resolution was  "make sure you have the latest Articulate update installed". We did that, but nothing changed. We would really appreciate some help with this, as this happens only in this particular course.  Thank you.

3 Replies
Jose Tansengco

Hello Andreea,

Thanks for reaching out!

I viewed your published course using JAWS Version 2021 and here are my observations: 

  • Immediately after submitting a question using keyboard navigation, I was redirected to the 'main region' which JAWS read back to me
  • I then pressed tab and was immediately taken to the 'Continue' button of the feedback layer
  • I pressed up once to read the feedback text, and. another up to read the layer title (Correct/Incorrect)

It looks like the behavior is a little different when you test your course on my end. Since the issue is only happening to one of your courses, I'd like to ask a few questions to help clarify your experience: 

  • What version of JAWS do you have installed? 
  • Are you able to replicate the behavior on other browsers? 

You also mentioned that it doesn't happen when you use NVDA, which means you have your focus order properly setup. Have you tried installing the latest version of JAWS to see if this makes a difference? 

Jose Tansengco

Hi Andreea,

Thanks for sharing your project file! 

Here's a quick recording of what happens when I test your project file using JAWS 2021. You'll notice in the video that I did not encounter the behavior that you initially described. 

Since the issue appears to be isolated, try the following to see if they help address the behavior:

If the issue persists, open a case with our support team here so we can take a closer look at what's happening.