Captivate 2017 HTML5 output acessibility

JAWS reads Captivate 2017 HTML5 course in the following order: When course is loaded via index.html in web browser, first it reads the Slide title followed immediately by the Slide Accessibility Text. I usually put in the accessibility text what the slide contains (2 textboxes, 1 image, etc) so that my blind users know what they are tabbing to on the page. Depending on your tab order, when the user tabs, JAWS will read the accessibility name/description boxes for your objects. To activate any buttons, JAWS users will need to select Shift and Enter keys. The Enter key does work normally when the screen reader is turned off.

I haven't had any issues yet with HTML5 output except for the fact JAWS users cannot search by heading, link, or form field due to way Captivate codes their file (I am unable to editing much in Dreamweaver beyond adding some code to help with focus indicator and some Javascript). I don't think this is a problem as long as you are consistently with the slide accessibility info as users go from slide to slide in your course.

It sounds like you are using variables or something on your slides to have JAWS read strange numbers.