We go along with which belief as a whole
PDF files would be held so you can WCAG dos.0 standards, however, WCAG 2.0, certainly, isn’t adequate, once the I have found. On some peak, Adobe is apparently aware that WCAG dos.0 doesn’t completely defense PDF, because they continue (emphasis extra):
“…and think that making use of WCAG 2.0 with additional advice utilized in WCAG2ICT brings compatible criteria in order to make sure PDF files is available for those who have handicaps.”
“The newest Board may offer PDF/UA as the a selection for article authors, however, should also require even more conditions off WCAG dos.0 so you can guarantee that all-content designs within PDF files was good enough shielded. Article authors which have fun with PDF/UA discover they an extremely of use source of pointers having PDF files that follow ISO 32000-step 1 brand of PDF, but WCAG dos.0 must be the first importance of conformance intentions.”
PDF/UA isn’t intended by any means, figure otherwise means to possess “authors”. It’s a scientific specs intended for app designers. It’s no appropriate a way to obtain recommendations to have article writers than simply try OOXML, the specification towards .DOCX documents employed by Microsoft’s Term.
Software designers make PDF/UA to their situations for the true purpose of while making or running PDF documents. Authors is simply find PDF/UA once they see it one of the possess supported by the application. File authors becomes the key benefits of PDF/UA from the exact same components whereby it connect with app to ensure WCAG dos.0 conformance.
Exactly how not to play with WCAG2ICT
Problems common to the comments provided by ITI, IBM, SSA and you will Adobe is the invocation from WCAG2ICT as the a source out-of “extra recommendations” in making accessible PDF files. There are lots of issues with having fun with WCAG2ICT like this. Earliest, the brand new document itself, just like the James Light points out in his review, states demonstrably: