Ca5pian
-
Posts
6 -
Joined
-
Last visited
Reputation Activity
-
Ca5pian got a reaction from HawaiiAna in Tagged PDF support for accessibility
I totally agree. I don't know many designers who even know it's possible to create an accessible PDF, or what it actually means. But everyone gets it for web work. I can't see a single disadvantage of PDFs were created to be accessible by default.
-
Ca5pian got a reaction from MarkWahlstenDI in Tagged PDF support for accessibility
I totally agree. I don't know many designers who even know it's possible to create an accessible PDF, or what it actually means. But everyone gets it for web work. I can't see a single disadvantage of PDFs were created to be accessible by default.
-
Ca5pian got a reaction from JohannaH in Tagged PDF support for accessibility
I totally agree. I don't know many designers who even know it's possible to create an accessible PDF, or what it actually means. But everyone gets it for web work. I can't see a single disadvantage of PDFs were created to be accessible by default.
-
Ca5pian got a reaction from robskinn in Accessible PDF
I'd be very interested in understanding how Publisher will address accessibility in their exported PDFs. Currently there is no way to tailor a document to export a PDF with any acknowledgement of A11y. I appreciate that it's early days. I just hope it hasn't been left too late. InDesign has been trying to address it, but it too was appalling in its early versions. I expected that a progressive new app might be thinking about this and build it in from the very beginning — after all we are building documents for screen so often, we can't just ignore the requirements of so many.
-
Ca5pian got a reaction from kai2 in Tagged PDF support for accessibility
I totally agree. I don't know many designers who even know it's possible to create an accessible PDF, or what it actually means. But everyone gets it for web work. I can't see a single disadvantage of PDFs were created to be accessible by default.
-
Ca5pian got a reaction from JGD in Tables inside text frames - mandatory
While text wrapping is useful, it's not a substitute for anchoring. I'm sure they have a plan for it, I just hope it's sooner rather than later. I'm dreaming for a pro-level tool that is better/more intuitive than InDesign particularly for modern output. Without anchoring ePub isn't possible, and accessible PDFs become harder to achieve.
-
Ca5pian got a reaction from JGD in Tables inside text frames - mandatory
+1 here. Anchoring a table (or any element inside a text frame) is a must.
In addition being able to specify table head rows (and columns) is important not only for long tables that flow over multiple pages/columns but also with respects for exposing an accessible PDF. Without specifying them any A11y checker will fail the PDF.