The state agency I work for has mandatory requirement to make all pdfs accessible. We are creating static pdf using Adobe livecycle designer 8.2 and Jaws reads fine. In the accessibility panel, we give screen reader preference as "caption" and in the object panel, for caption, we give the field name. We make sure our tab order is set correct in the reading order. Life was good.
As soon as I made the forms expandable (dynamic), for field size to expand and be able to print, screen reader technology started acting funky.
In forms mode (press enter), jaws does not read the fields in set tab order. It jumps all over the form.
The same form worked fine with Screen reader in static mode.
I will really appreciate any help/direction in this topic. If you like to know how I made the forms dynamic, I will be happy to elaborate (learnt it from this forum).
Thanks a bunch
Priya
You'll need to contact Global Graphics for support on this issue. It doesn't have anything to do with Acrobat.
Thom Parker
The source for PDF Scripting Info
[url=http://www.pdfScripting.com]pdfscripting.com[/url]
The Acrobat JavaScript Reference, Use it Early and Often
[url=http://www.adobe.com/devnet/acrobat/javascript.php]http://www.adobe.com/devnet/acrobat/javascript.php[/url]
Thom Parker
The source for PDF Scripting Info
www.pdfscripting.com
Very Important - How to Debug Your Script