tutorial on 508 compliance?

How's everyone going?

I actually do need some help with accessibility standards for a course that I'm working on. I attached a sample page from one of the courses. Here's a description of what happens:

- This course has 2 "paths": One is for the normal learners, and the other is those with visual disabilities.

- VisionDis is a variable that controls which path is shown (Path 1 or 2).

On Path 1, the user can navigate normally (either by clicking or tabbing through with the focus box).

On Path 2, while the audio is playing, the user's focus box tabs through Menu and Closed Captions only, but then they can go to the play/pause/stop/previous/next buttons when the audio is done.

These work the way I want it to inside Storyline, but on the published html file, here's what happens:

- There are instances that I cannot tab my way back to the screen if I'm on Menu/Closed Captions.

- Our QA person who checked this using JAWS couldn't press on the play button.

- The tabs don't seem to get read (or it doesn't read all the time).

I'm not sure if this has anything to do with our JAWS reader being on trial mode, to be honest.

I guess I'm just looking for some additional direction on how to make this function better on Path 2. I know I can probably assign buttons on the keyboard for the course buttons, but any recommendation on how to make this more user-accessible would be great!