You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@eboudreau , @alexduryee : I think that we might be able to use the 2018 minor EAC revision to create a PDF/UA file. I don't think that there are any images or graphics in the EAC tag library, so it should just be a matter of a few minor changes to create a PDF/UA tag library. Once we get to the PDF creation step, just let me know and I can take a crack at that.
To-dos, in order to pass the Accessibility Checker:
Add a document title in metadata (may as well add other metadata elements while we're at it)
Add bookmarks within the PDF
Add alt-text to images (I think it's just the SAA logo and the example element?)
Add headers to tables. This one is a little vexing, since the list of attributes for each element is stored in a table. We'll need to add "attribute" and "required?" headings to each of those tables.
Once these are done, I think we should be set for generating PDF/UA as part of the process.
At some point, we'll want to generate accessible PDF documents for the TLs via the XML->FOP workflow.
cc @fordmadox
The text was updated successfully, but these errors were encountered: