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 Association’s PDF 2.0 interop workshop on May 16, 2018 will have the opportunity to test their own files and implementations against files and software others have developed for PDF 2.0.
As with the previous two interop workshops, participation is free, and developers have the option of participating anonymously and/or remotely. Although registration is required, an email address will suffice.
New in 2018… workshop attendees can maximize utility and value by participating prior to the workshop day, by adding their own test-files or commenting on others, but by requesting test-files from other developers.
To maximize both the opportunities and the benefits of testing, the third PDF 2.0 interop workshop makes it possible for developers of PDF consumer products to ask for and discuss test cases addressing specific PDF features before the formal event begins. According to Martin Bailey, CTO of Global Graphics:
“Leveraging the workshop to request test-files that exercise PDF 2.0 features is a major opportunity to validate developers’ assumptions and ensure a valid basis for development.”
First, sign up for the 3rd Interop Workshop. The event itself will be held May 16, 2018. This workshop directly follows (and is co-located with) PDF Days Europe on May 14 and 15, keeping things convenient for PDF Days attendees.
Those signing-up for the workshop will receive instructions for creating an account on the PDF Association’s Jira for the PDF 2.0 interop project.
Once you have a login you can begin uploading files and test-requests in preparation for the event.
On May 16, 2018, developers participating in-person should arrive at the workshop room by 0900. A GoToMeeting session will be provided for those participating remotely. We will begin with introductions and a short briefing on the process; then get down to testing!
We understand that some companies restrict their developers’ open participation in such events due to a variety of concerns. To accommodate this restriction, there’s no problem with participating via a generic email account, and thus remaining completely anonymous to other participants. Anonymous users will not have the ability, however, to change the status of test-files.
Remote participation is encouraged for developers who cannot be physically present in Berlin for the 3rd interop workshop. Instructions for joining the event will be included in your welcome email.
We chose this platform for tracking test files and test-requests because it’s likely to be familiar to developers. Leveraging that assumption, we are not providing instructions on the use of Jira itself, but simply highlighting the differences as compared to a conventional software project.
We encourage users to make full use of the commenting, voting and watching functionality in Jira in order to stay current on comments or status-changes for specific test-cases.
Once logged-in, visit the PDF 2.0 interop project.
Review the previously-posted issues for a sense of the test-files and test-file requests already posted to this or previous interop workshops. Alternatively go straight to creating a new “issue”.
In this Jira, “Issues” are actually test-cases or test-case requests. To start a new test-case or request a specific test-file, start a new issue of either type and click “Next”.
Provide a brief summary of your test or request. In the Components field, type in the ISO 32000-2 clause number and clause title to identify the feature(s) you are testing or wish to test. If that clause has been previously posted, it will appear in the dropdown. If not, please provide the complete clause number and title.
In the Description field, provide whatever information would help other developers understand what you are trying to achieve.
Optionally, use the Label field to identify the source (for Workshop purposes) and context (Creator, Consumer, Editor) of the test file or request. The drop-down provides a list of previously-used identities.
Attach your test-file, if applicable.
If the issue relates to an existing issue you may indicate that connection by identifying the type of relationship and indicating the issue in question.
Add an assignee, if applicable (for example, if you want to request a specific attendee review your test-file), then finish by clicking “Create”.
As you review files posted by others, please leave some sort of comment (or screen-shot, or other output if appropriate) on their issue to indicate your findings.
In this instance, Jira issue status was repurposed for use in the interop workshops.
Only the test-case requester should retire existing test-case requests.
Typically, test-case status is changed by an issues administrator, however, any member of the Workshop may set the status of a given test-file if they believe consensus has been achieved. Any given status conformance is subject to review by the PDF Association’s PDF Validation TWG.