Highlights for Universal Accessibility
- Making documents universally accessible means ensuring that everyone has access to all information in a document.
- Universal accessibility for PDF documents can be achieved by complying to the PDF/UA standard which has the aim to provide everyone with equal access to all information in a document.
- Some of the most impactful PDF/UA requirements are tagged PDF, alternate descriptions, language identifiers and embedded fonts.
- Universal accessibility offers universal benefits for users with and without disabilities.
- PDF/UA makes it easy to comply with accessibility regulations across the globe such as ADA, EAA, AODA and so on.
- The open-source iText SDK/library lets you create and manipulate Tagged PDF in Java and .NET (C#). Add language specifier, set the title, embed fonts and add alt text.
- Using the Fluent document solution from Apryse, you can create templates to generate PDF/UA compliant documents in a collaborative and user-friendly environment.
Why make PDF documents accessible
Whether you look at your company’s internal or public facing documents, many of them are bound to be PDFs; the PDF format makes up about 90% of published digital documents today. And in a world where digital documents are often the sole source of information available, it is important that everyone has equal access to all the information in those documents. That is exactly what PDF/UA – the PDF standard for Universal Accessibility – aims to do.
Technical requirements of PDF/UA
The requirements particularly focus on including those with disabilities that make use of assistive technology (AT), such as screen readers and braille displays, but also input devices ranging from adaptive keyboards to eye-tracking software. The current PDF/UA-1 standard specified in ISO 14289-1:2014, is based on PDF 1.7 and adds some additional requirements and constraints to ensure accessibility.
One of the most impactful requirements is that all meaningful content should be tagged. Tags identify each element of a PDF, for example a header, a table, or an image. Together, these tags form a hierarchical structure tree and the order of the tags sets the reading order of the document. A full list of requirements can be found in the free PDF/UA ebook we produced, though we have summarized the key points here.
All meaningful content needs to be tagged in a logical and semantically correct way. All other content is identified as an artifact.
The main language of the document and any changes in language throughout the document should be marked.
Fonts must be embedded and Unicode mapped
Images that convey meaning must contain alternative descriptions and must be tagged with a Figure tag.
Universal Benefits of PDF/UA
While the biggest stakeholders for accessibility are the over 1 billion people with disabilities worldwide, PDF/UA can benefit both users with and without disabilities. Just think about how frustrating it can be to read an inaccessible PDF on your mobile phone. The structural requirements of PDF/UA allow for better machine reading capabilities, that can allow for efficient reflow of a document on diverging screen sizes, but can also improve your PDF to HTML conversion, SEO (Search Engine Optimization), and everyday text-to-speech applications. You can read more about the benefits for all users in our blog.
Does anybody still need convincing? Well, providing accessible documents is not just a moral consideration, but one often mandated by law. One such law addressing the accessibility of all publicly available content, is the Americans with Disabilities Act (ADA). In 2020 alone, approximately 11,000 ADA lawsuits related to accessibility of private businesses were filed, of which 3,500 relate to digital accessibility. With settlements for individual plaintiffs often adding up to thousands of dollars, inaccessible documents can become a major liability for your organization, and not just in the USA (ADA and Section 508).
The EU has the EU Web Accessibility Directive and the European Accessibility Act (EAA), The UK has the Disability Discrimination Act and Canada has several such as AODA. And the list goes on, so be sure to check for your local regulations in our free ebook “PDF/UA: the inclusive document format”.
Make PDF/UA compliance scalable with Apryse
Apryse offers you solutions to achieve PDF/UA compliance in a scalable way, both within the open-source iText Core library and the Fluent document solution.
iText Core library
iText Core provides developers with the necessary tools to automate the creation of accessible PDFs in both Java and .NET (C#). With just a few lines of code you can meet the following PDF/UA requirements in your workflows:
- Create and manipulate Tagged PDF
- Add a language specifier
- Set the title of the document to display in the title bar
- Embed fonts
- Set alt text
Code example for creating a PDF/UA compliant document
With Apryse's collaborative and user-friendly Fluent document generation solution you can design great-looking templates in Microsoft Word, PowerPoint, or Excel, and merge them with data using the Fluent designer add-on. The Fluent Manager enables you to simplify the process of creating and maintaining your templates, data sources, and resources.
Fluent supports a wide range of data sources and output document formats including Office, HTML and PDF. In addition to standard PDF output and PDF/A for long term archival purposes, Fluent now also supports PDF/UA output, enabling you to automate the creation universally accessible PDF documents with ease.