I attended a presentation by an advisor on accessibility for the NZ Government (and previously with the Canadian Government) which was very informative.
“If properly tagged and otherwise “accessible”, [PDF] semantic structures have never been available to screen reader users on Mac OS, iOS, or linux. I gather Adobe is currently taking steps to rectify the situation for OS/iOS, but that’s not complete yet, and it still leaves blind/screen reader users on linux out in the cold. They can still get to the text, but it’s just one big blob of linear, unstructured text.
The other issue with PDFs is that they don’t allow reflow, or changing fonts, font size, colour, etc. This makes them especially painful to use for everyone on mobile devices.
Epub3, on the other hand, is just HTML and CSS in a wrapper, so Epub3 readers can allow all those features, reflowing pages to the desired screen size, font/font size, etc. And since it’s all just HTML, the semantic structures in the markup are easily exposed to assistive technologies.”
Now my challenge is how to take this information and build it into a workflow for our design team.
By the way I really enjoy your InDesign podcast David. Thanks for sharing your wealth of information! (We are on CC2014… just haven’t updated our reading material, or gone to CC2015 as is incompatible with our server — long story but apparently there is a light at the end of the tunnel)