acrobat 2017: what are the bugs with accessibility?

[murrjames]

does anyone have issues with accessible forms and acrobat 2017?

[title changed for clarity by moderator]

[jane-e]

Hi murrjames ,

I moved this from PDF Forms to Standards & Accessibility (tagged PDF)

If you are not looking for a yes or no answer, though, please clarify the issues you are having. Thanks!

[murrjames]

I want to know what issues or bugs people have in acrobat 2017. that is the question. not sure why you moved me, but eiter way I want to know about the bugs ppl have found.

[jane-e]

If it's "bugs" with accessible forms, it should be here in the Accessibility forum. Did I misunderstand? I can pop it back if I did.

[murrjames]

I only do accessible pdfs and I have only sent it here. When did this other group start?

ok leave it then, thank you.

[jane-e]

I'm not sure as to when — this is only my third year volunteering on the forums, and I think it's been here since I've started. Any moderator can move it. If you don't like where it is, just let us know!

[Chad Chelius · Accepted solution]

I don't keep track of the bugs in Acrobat 2017. I use Acrobat DC which is the subscription edition of roughly the same product. Additionally, there are limitations of Acrobat 2017 from an accessibility standpoint but mostly these are things we'd like to have vs. bugs per se. I can tell you that Acrobat 2017/Acrobat DC offers many more features and a lot more functionality when remediating PDF files than previous versions. Your question pertains to Accessible forms in Acrobat 2017. I can tell you that forms created in Acrobat 2017/DC are not tagged by default and require that you manually tag the form fields after the fields are created which is an extra step. I wouldn't categorize this as a bug but more of a limitation or omission in the functionality. Programs like Adobe InDesign do actually tag the form fields when exported to the PDF format. If you do a lot of form creation, I'd take a look at Adobe LiveCycle Designer/AEM Forms Designer.