The PDF Techniques Accessibility Summit’s objective is to establish a broad-based understanding of how PDF files should be tagged for accessibilty. It’s an opportunity to focus on establishing a common set of examples of accessible PDF content, and identify best-practice when tagging difficult cases.Modernizing PDF Techniques for Accessibility
The PDF Techniques Accessibility Summit will identify best-practices in tagging various cases in PDF documents. Questions to be addressed will likely include: the legal ways to tag a nested list, the correct way to caption multiple images, the appropriate way to organize content within headings.Refried PDF
My hospital emailed me a medical records release form as a PDF. They told me to print it, fill it, sign it, scan it and return it to the medical records department, in that order. In 2018? To get the form via email (i.e., electronically), yet be asked to print it? Did the last 20 years just… not mean anything! So I thought I’d be clever. I’d fill it first, THEN print it. Or better yet, never print it, but sign it anyhow, and return it along with a note making the case for improving their workflow. The story continues…Slides and video recordings of PDF Days Europe 2018
You missed the PDF Days Europe 2018? Never mind! Here you can find the slides and video recordings of all 32 stunning sessions!Using PDF/UA in accessibility checklists
PDF/UA, like PDF itself, is internally complex, but used correctly, actually makes things easier.
Developers participating in the PDF 2.0 interop workshops in the UK (Cambridge) in May, and in the USA (Boston) in June will have the opportunity to test their own files and implementations – even PDF 1.7 implementations – against files and software others have developed for PDF 2.0.
There’s no cost for these workshops, and developers have the option of participating anonymously, or even remotely.
Those participating will be asked to fill an Excel spreadsheet listing their test objectives, and specifying the nature of the information they’ll provide based on their own tests. The PDF Association will use this information to create a matrix of possible pair-wise tests while protecting some participants’ need for anonymity.
The Excel file collects company and product information, and for anonymous participants, we will assign code-words to any product name provided. The form then asks for the basic type of software (creator, consumer, both) being tested.
Once the basic software type is established, choose the means by which you prefer to share test-results with the test-file’s contributor.
For each file (or feature in your software) that you wish to test, please identify areas of testing focus with one row / area of focus. Note that the drop-down is populated by the table-of-contents as provided in the FDIS of ISO 32000-2. PDF Association members can access the FDIS from the PDF Association intranet.
Provide a clearly-identifiable test-case or file-name for each test-file, and indicate whether you’ll be providing some test-cases, or are seeking test-cases.
Once you have identified each test-focus and corresponding file, email your Excel file to email@example.com.
Sign up for the PDF 2.0 interop workshop UK today – May 2-3 in Cambridge.
Sign up for the PDF 2.0 interop workshop USA today! It’s on June 12-13 in Boston.