Jaws and Cp 7.01.237 - not BFFs?

Question

Building for a 508 requirement that uses IE and JAWS 14 on a Windows 7 machine using the Captivate 7.01.237 version. I'll state out front that we made 508 accessible pdfs that were given extremely high marks by our mobility and sight impaired user groups, but are not considered other than "ancillary" accessibility by the government tester (not sure why)
Currently running into this laundry list when testing to the SCORM Cloud and applying JAWS:
JAWS reads the variable script in a text box instead of the output (example reads: "$$cpInfoCurrentSlide$$ of $$rdinfoSlideCount$$" instead of "1 of 2" and reads "$$cpInfoProjectName$$$$cpInfoDescription$$" rather than "Lesson1 - JAWS is Evil")
If a button has three states (selected, rollover, and not selected) JAWS reads this as three buttons, and two don't have name, role, and state information.
JAWS won't read the feedback boxes on any question slide, period.
If you set up an action to reveal information after the user makes a choice by selecting a button or menu item, any resulting change on the page is not necessarily read immediately following the selection.
Opening a TOC from the playbar is easy, closing it is nearly impossible in JAWS
An overlay TOC creates an expand/collapse button as a tab on the upper corner of the TOC that cannot be given an accessibility tag.
Accessing a TOC immediately reduces JAWS effectiveness. The focus and flow of the course is lost and cannot be reset - all slides begin at the of the TOC and JAWS reads "end flash" - the only way back to the beginning is to press the up arrow key repeatedly until you reach the beginning of the slide.
Opening a linked swf or document is a high wire act - if you close it and JAWS isn't focused over the open project, it's difficult to get back to the project, let alone get back to where you left off.
Using a glossary widget works, but it's difficult at best to get out of it and close it without running through every active letter and the title and content bars, which gets old fast.
Smart shape buttons can't be accessed without using shortcut keys.
Yes, sent all of this in as a bug report today. Just looking for any ideas/workarounds as I continue to be "that silly old ant, trying to move that rubber tree plant..."
Justenuf

Answer 1

PLEASE NOTE: If you are lucky enough to have a 508 testing service that reads the law in a manner that allows you to create JAWS (or other screen reader) accessible .pdf documents to meet the requirements of the law, none of the information below should be an issue, since visually impaired users will have access to your content through the document. However, my experience has been that there is no agreement on whether the pdf document meets the requirements of Section 508 (for example, one department I worked for did not allow pdfs to be used at all, another department saw them as a "nice supplement" - after initially being exceptionally enthusiastic about their use as the primary alternative.)
FYI - heard back from Adobe and wanted to share with other 508-challenged designers - "[Sankaram]" = Adobe
1. JAWS reads the variable script in a text box instead of the output (example reads: "$$cpInfoCurrentSlide$$ of $$rdinfoSlideCount$$" instead of "1 of 2" and reads "$$cpInfoProjectName$$$$cpInfoDescription$$" rather than "Lesson1 - JAWS is Evil")
[Sankaram]: This is a bug. (not 508 compliant - so lose your slide counter, could be a deal breaker)
2. JAWS won't read the feedback boxes on any question slide, period.
[Sankaram]: It is suggested to have audio attached to feedback captions, so when it is appeared corresponding audio is read. (So, it's a bug unless you record audio for each feedback box on each question slide - no TTS option available)
3. If you set up an action to reveal information after the user makes a choice by selecting a button or menu item, any resulting change on the page is not necessarily read immediately following the selection.
[Sankaram]:Objects are read by JAWS based on the Z-index in timeline. Say for example you want a text caption to be shown on click of a button make sure you place text caption up in the Z-index next to button. (So, set up your reading order from the bottom of the timeline to the top... or maybe not - I'm still working with this)
4. Opening a TOC from the playbar is easy, closing it is nearly impossible in JAWS An overlay TOC creates an expand/collapse button as a tab on the upper corner of the TOC that cannot be given an accessibility tag.
[Sankaram]:This is bug. (As stated by numerous folks here, the TOC is tricky - as stated by Adobe - it just isn't 508 compliant)
5. Accessing a TOC immediately reduces JAWS effectiveness. The focus and flow of the course is lost and cannot be reset - all slides begin at the of the TOC and JAWS reads "end flash" - the only way back to the beginning is to press the up arrow key repeatedly until you reach the beginning of the slide.
[Sankaram]: I could see the issue here. (Since its already not compliant from #4, this is just another nail in the TOC coffin)
Justenuf