If you want to read the contents using normal VO reading keys you need to first interact with the path\filename pane. If anyone else wants to test and see if they get the same behavior, here is a link to a tagged PDF: I tested this using multiple tagged PDFs and the same thing happened in each of them. I just couldn't navigate quickly to any of them and none of them appeared in the rotor. If I simply read through the document VO did announce headings, alt tags, self-descriptive links - all of which would be expected in a tagged PDF. I also checked and the headings do not appear in the rotor. What I found was that VO does now seem to read the tags in the PDF, but that if I tried to navigate using the headings it caused VO to crash/restart. So I just tested reading a tagged PDF on my early-2013 Mac Book Pro running OS X 10.11.1 and the latest version of Acrobat Reader DC. The blog post claims that the update will be out in less then thirty days I now have something to be more excited about then the Apple watch. In my opinion if this update is truly accessible it will be the most important advancement in the state of mac accessibility since Pages became more accessible. For the first time, Mac users will be able to use VoiceOver to create, edit and read accessible PDF documents." "The upcoming release of Adobe Acrobat and Adobe Reader will contain support for reading tagged PDF content with assistive technology on both Windows and Mac OS X. The following is a quote from Adobe's accessibility blog.
This update claims that it will change all of this. As I'm sure everyone knows, there is currently little meaningful support for tagged pdf's on the mac, which makes accessing pdf's annoying at best. Last week, Adobe announced the upcoming release of Adobe Acrobat DC and Adobe Reader DC, These updates claim to have accessibility features that would be a game changer on the mac.
0 kommentar(er)
