Posts in Category "Acrobat"
Adobe is offering a free webinar on document accessibility in conjunction with SSB BART Group and FedInsider News. The webinar will take place Wednesday January 23, from 1:30-2:30 (US eastern time zone).
Jon Avila from SSB BART Group will lead the session which will target managers and content authors in addressing the following topics:
- Overview of accessibility requirements relevant to document creation.
- Guidance on how to analyze known problems in existing documentation.
- Proper use of native document creation software.
- Techniques for finding and fixing accessibility violations.
- Best practices to maintain and update document creation processes to ensure ongoing accessibility.
You can read a more information about the webinar and register at http://solutions.adobe.com/?elqPURLPage=114. Please join us for this event!
Update: I neglected to mention it, but the webinar will have live captioning.
Update: The webinar recording is available.
On behalf of the Adobe Accessibility team, I’d like to welcome you all to 2013. We’ve got a big year ahead of us, and we’re starting with some new documentation for Acrobat XI.
We’ve updated our Acrobat accessibility training resources page with four new PDFs:
- PDF Accessibility Overview
- Covers the accessibility features of PDF as a document format, as well as Adobe Acrobat and Adobe Reader.
- Using the Acrobat XI Pro Accessibility Checker
- A complete walkthrough of Acrobat XI’s Accessibility Checker, as well as the Make Accessible action wizard.
- Acrobat XI Pro PDF Accessibility Repair Workflow
- Walk step-by-step through the PDF accessibility process in Acrobat XI.
- Acrobat XI Pro Accessible Forms and Interactive Documents
- Create interactive forms that can be used by anyone, ensuring privacy and independence for all.
We’ve also created a Acrobat XI accessibility best practices document which contains all four of the above guides in a single file. Documentation for Acrobat versions 8 and up can be found on the training resources page as well.
The new features of Acrobat XI are intended to make creating PDF documents both easier and more automatic. The Make Accessible action wizard walks users through a number of steps, like running optical character recognition and prompting for alternate text on images, and then tests the final product. This makes the process for editing and testing for PDF accessibility a fast, uniform process for authors of all skill levels. The built-in accessibility checker has also been improved, including testing support for the Web Content Accessibility Guidelines (WCAG) 2.0. We think this is the most substantial improvement in Acrobat accessibility since we added support for assistive technology back in 2002.
The team is looking forward to giving a detailed Adobe Acrobat XI walkthrough at the 28th Annual International Technology and Persons with Disabilities Conference on February 28th, and at other conferences throughout the year. We hope you’ll find these tutorials useful.
Acrobat XI (pronounced “Acrobat Eleven”) is coming soon, and with it a host of new accessibility features that will help authors produce more accessible PDF documents, with less effort.
Key improvements in Acrobat include the addition of the Make Accessible Action, enhancements to the Touch Up Read Order Tool, and improvements to the accessibility checking tool to guide authors testing against WCAG 2.0 and PDF/UA.
The Acrobat team has more information about accessibility in Acrobat XI posted, and more information is coming soon.
Adobe continues our support for NVAccess development of the NVDA screen reader in 2012, and with that funding we are supporting a number of priorities designed to help NVAccess developers continue to offer an up-to-date tool for end users as well as developers seeking to provide accessible applications and web sites. Included in the list of priorities is support for ongoing improvements to NVDA’s ability to interact with PDF documents, AIR applications, and ebooks read in Adobe Digital Editions, and for general HTML and ARIA improvements.
For PDF specifically, we recognize the value of NVDA supporting the upcoming PDF/UA standard (ISO 14289) and have agreed with NVAccess that the PDF-focused portion of the work should be focused on enabling NVDA to become a PDF/UA compliant assistive technology.
Past improvements to NVDA’s support for PDF have brought significant benefits for NVDA users reading PDF documents. These past improvements were not designed to focus on PDF/UA compliance, but most of the improvements serve to accomplish compliance and dovetail nicely with current efforts focused on the new standard. The work to make NVDA compliant with PDF/UA will not be able to be completed in the current year, as the scope of work is beyond what can be completed within the current year’s funding, but we expect to be able to provide details about progress in the coming months. As support for PDF/UA is an important goal, we will seek ways to offer support to NVAccess in future years also.
We are almost halfway through the year for this funding and NVAccess developers have made continual improvements – we encourage screen reader users and accessibility-interested developers to download the latest release of NVDA to read ebooks, test web pages, read PDF documents, and more. NVDA is a great tool and Adobe is pleased to help support its development.
Update: We should also clarify that our support for NVDA does not come at the expense of support for other assistive technologies. Tools such as Claro Read, JAWS, Supernova, Window-Eyes, ZoomText, and many more are important tools that users depend on and we will continue to work with the vendors of these great tools.
Harmonization of accessibility standards is a primary goal for Adobe which is why for many years Adobe has worked on the W3C Web Content Accessibility Guidelines (WCAG) working group – our participation was driven by a desire to help define a WCAG 2.0 standard which would be useful for web content that Adobe tools are involved with the authoring or display of, including PDF, Flash, HTML, and more. There is great benefit for developers, authors, and end users when there is an agreed on standard for what constitutes an accessible experience, and it is encouraging to see that WCAG 2.0 is regarded as the primary standard for web accessibility and is referenced by national governments around the world. However, there is more to achieving accessibility than the normative text of WCAG 2.0.
In 2004, Adobe and AIIM started the PDF/UA (Universal Accessibility) activity with the intent of producing standards specific to PDF authoring and presentation which ensure that conforming PDF (ISO 32000-1) files are accessible and usable to all, including users who rely on assistive technology. Today, PDF/UA is ISO 14289-1, a “Final Draft International Standard (FDIS)”, expected to be published later in 2012.
We’ve received many questions about the relationship between PDF/UA and WCAG 2.0. WCAG 2.0 was developed as a technology-independent standard and provides individual (normative) success criteria for accessibility which are general enough to apply across technologies. The W3C’s WCAG working group also provides a growing collection of advisory (non-normative) techniques to offer technology-specific guidance, including a growing set of techniques for HTML, CSS, Scripting, PDF, Flash, and more. Beyond these techniques, developers need to conduct additional research to ensure that the content or applications they create meet the WCAG 2.0 success criteria – for example, a Java developer looking to offer a compliant applet will not find techniques on the W3C site at this time, but may be able to meet WCAG 2.0 if they correctly follow guidance provided elsewhere and evaluate the resulting applet against the WCAG success criteria.
PDF developers need this type of clarity on how to meet WCAG 2.0, and the PDF techniques, while useful, do not presently represent a complete set which encompass all technical requirements for accessibility in all PDF documents. This is where PDF/UA provides help. PDF/UA provides normative technical specifications for the use of the PDF format, defining proper structure and syntax to enable reliable access. This includes identification of necessary tagging structures, how to specify alternative text for images, how to ensure correct Unicode mappings for character glyphs, and many other file, page and object-level specifications, as well as how Reader applications and assistive technologies can fully process PDF/UA conforming files to maximize accessibility.
PDF/UA defines the technical specifications to enable PDF documents to meet WCAG 2.0, but WCAG 2.0 has additional requirements which require an author’s attention. The areas where WCAG 2.0 has additional requirements include time-based media (guideline 1.2), scripting and actions (e.g. success criteria 3.2.1 and 3.2.2), and certain types of content (e.g. success criteria 2.4.4). For these and other additional requirements, the W3C’s technique documents (both general and PDF-specific techniques) provide guidance for authors interested in complying with WCAG 2.0.
PDF/UA clarifies and simplifies the PDF-specific technical requirements to meet WCAG 2.0. Adobe fully supports PDF/UA and intends to use and promote it in our PDF authoring tools. Adobe also plans to support the conforming Reader requirements, which are part of PDF/UA. Authors using Adobe tools such as Adobe Acrobat will be enabled to support PDF/UA as a first and major step toward compliance with WCAG 2.0.
Authors looking for additional guidance on how to meet the W3C WCAG 2.0 for PDF documents can now look to the W3C techniques repository for additional guidance. Techniques for PDF authored over the past two years since the release of the last update to the WCAG techniques (which included techniques for Flash) are now part of the larger collection of techniques. View the full set of WCAG 2.0 techniques or view PDF techniques on their own.
These techniques provide a clear path for demonstrating that a PDF document can meet the most current accessibility standard from the W3C.
As with the Flash techniques for WCAG 2.0 and techniques for all other technologies, the PDF techniques are presented as examples which the WCAG Working Group viewed as sufficient to meet WCAG 2.0 success criteria, not as the only way to meet any given success criteria. Authors may discover a new way to address a success criteria, in a way not yet covered in the existing techniques, and be able to demonstrate why it is sufficient. The techniques offer a collection of strategies that have been reviewed by the working group, but the techniques collections for all technologies are works in progress as there are always additional ways to address success criteria.
The table below provides a listing of the WCAG level A and AA success criteria and the PDF-specific and General techniques that authors can employ to meet success criteria. It is worth noting that not all success criteria for WCAG 2.0 have technology-specific techniques. For example 1.3.3 (Sensory characteristics) has only general techniques, and in this case and similar ones I reference the relevant general techniques section. In some cases there are relevant general techniques as well as PDF-specific techniques and for these both are linked.
Update: I neglected to acknowledge the hard work of Mary Utt from The Paciello Group on the PDF techniques initially, but Mary was a tremendous help in moving this work forward and I offer many thanks. Many people on the WCAG working group also worked very hard to help make these techniques reach this final stage. Thanks to all!
Please send general comments, comments or questions on the techniques, or suggestions for new techniques.
|1.1.1 Non-text Content||A|
|1.2.1 Audio-only and Video-only (Prerecorded)||A||
|1.2.2 Captions (Prerecorded)||A||
|1.2.3 Audio Description or Media Alternative (Prerecorded)||A||
|1.2.4 Captions (Live)||AA||
|1.2.5 Audio Description (Prerecorded)||AA||
|1.3.1 Info and Relationships||A|
|1.3.2 Meaningful Sequence||A|
|1.3.3 Sensory Characteristics||A|
|1.4.1 Use of Color||A||
|1.4.2 Audio Control||A||
|1.4.3 Contrast (Minimum)||AA||
|1.4.4 Resize text||AA|
|1.4.5 Images of text||AA|
|2.1.2 No Keyboard Trap||A|
|2.2.1 Timing Adjustable||A|
|2.2.2 Pause, Stop, Hide||A||
|2.3.1 Three Flashes or Below Threshold||A||
|2.4.1 Bypass Blocks||A||
|2.4.2 Page Titled||A|
|2.4.3 Focus Order||A|
|2.4.4 Link Purpose (In Context)||A|
|2.4.5 Multiple ways||AA||
|2.4.6 Headings and Labels||AA||
|2.4.7 Focus Visible||AA|
|3.1.1 Language of page||A|
|3.1.2 Language of parts||AA|
|3.2.1 On Focus||A||
|3.2.2 On Input||A|
|3.2.3 Consistent Navigation||AA|
|3.2.4 Consistent Identification||AA|
|3.3.1 Error Identification||A|
|3.3.2 Labels or Instructions||A|
|3.3.3 Error Suggestion||AA|
|3.3.4 Error Prevention (Legal, Financial, Data)||AA||
|4.1.2 Name, Role, Value||A|
I spoke on Adobe’s efforts to support the captioning aspects of the 21st Century Communications and Video Accessibility Act at the TDI Conference a couple of weeks ago in Austin, TX. In this talk I highlight a number of efforts to support captioning that Adobe has worked on – most people interested in captioning are familiar with some but not all of these. Take a look and let me know if you have any comments.
Adobe is running a series of training in Australia the first week of March to help Australian Government employees understand how to create accessible PDF documents. The trainings are being held in Canberra at the National Museum of Australia, but will be recorded and made available online after the sessions (probably with a 1-2 week delay in order to have the recordings captioned and posted). We are running these sessions in conjunction with the Australian Government Information Management Office (AGIMO).
I’m delivering two different presentations (twice each):
- PDF Accessibility for Everyone – suitable for a wide range of user knowledge of accessibility, focusing on common authoring pathways
- PDF Accessibility for Techo’s – an advanced session for people with good knowledge of accessibility
More information about the sessions, and registration for attendance, is now available.
I’m looking forward to these sessions and helping people understand how to create PDF documents that meet WCAG 2.0 and are easily used by people with disabilities.