The glossary explains terms, which are important if you work with accessible PDF.
Through accessibility no people with disabilities are going to be excluded. This means that electronic documents need to meet technical conditions so that everyone can use them independently.
The most important basics are achieved if
- the document contains semantic PDF tags, which generate the logical document structure and reading order;
- objects that are not relevant are marked as artifact (e.g. decorative elements, repeating header and footer);
- basically all text of the document is available as text and not as an image (OCR scanning);
- alternative texts are used to describe non text elements (images and graphics);
- no low or bad color contrasts are used.
An alt text (short for alternative text) describes a non-text element, like an image / a graphic. The invisible text can be read and displayed by software, especially AT.
The alt text should be as short and concise as possible and describe what is visible on the picture. It should not contain any additional information that would not be visually recognised, e.g. the name of the photographer or names of visible persons and things that would not be clearly recognised by the context. This is the big difference to a visible caption / a picture description, which can transmit additional information.
Not every picture/graphic needs an alt text. WAI (Web Accessibility Initiative) offers a valuable decision support with “An alt Decision Tree” and the Web Accessibility Tutorials. The main difference between HTML and PDF is the handling of decorative images (e.g. background images, lines and other decorative shapes). In PDF those are marked as artifacts, see also “Unimportant and decorative objects as artifact”. While decorative images do not need any alt text, functional images should explain the function / the goal and not its image content. This includes linked images in particular.
see alt text
AT (abbr. for assistive technology) is the main term for tools people with disabilities use to read and understand content.
There are the following software and hardware for example:
- Screen reader
- Refreshable braille display
- Screen magnifier
- Voice recognition
- Special keyboards and mice
- Eye tracking, mouth stick
AT is the abbreviation of assistive Technology
logical reading order
The logical reading order stands for the correct order in which individual parts of the content should be read so that the document is understood correctly. A good practical example is a multi-column layout in which line by line within a column must be read and not over the entire page.
Assistive technology (AT) requires PDF tags not only to recognize the meaning of the contents, but also to derive the logical reading order. Unfortunately, not all AT use the order of the tags but take them from the visual order of the contents, which is displayed in Acrobat in the navigation pane “Order”. Adapting this visual order to the logical reading order can be very time-consuming and is not a requirement of PDF/UA.
In “Check semantics and logical reading order” you can learn how to check the logical reading order.
The Matterhorn Protocol is a document by the PDF Association and helps software developers and testers to check a PDF for PDF/UA compatibility. It describes 136 failure conditions. 87 of them can be tested by software. 47 of them have to be checked manually by a human. 2 failure conditions cannot be categorized.
PAC is one of the most comprehensive and free of charge testing tools. It checks PDF documents for its compatibility with the PDF/UA standard. PAC evaluates the failure conditions which can be tested by software. It includes a screenreader preview tool to check the failure conditions which need to be tested manually. The Swiss organization “Access for all” distributes PAC. The software is only available for Windows.
PDF/UA is the ISO standard 14289-1. The part “UA” stands for universal accessibility. The standard is aimed at production companies of software and assistive technology. To check a document for PDF/UA, you do not need to purchase the ISO documentation. Using the free Matterhorn Protocol, a document can be checked for PDF/UA compatibility.
PDF/UA is based on the WCAG, does not contradict those guidelines, but does not cover all regulations of the WCAG.
If your PDF contains tags – also called Tagged PDF – one big and important step of machine readability and thus accessibility has been done. However, the mere existence is not enough. The PDF tags must also reflect the semantics of the document. This means, for example, that a heading is not only visually recognisable as such by a larger font, but also by machine, by a heading tag.
The possible PDF tags (according to the PDF 1.7 standard) can be found in the “Overview of PDF tags”. Some of the available PDF tags are very similar to the HTML tags.
The WCAG, short for Web Content Accessibility Guidelines, are the recommendations/guidelines of the group WAI (short for Web Accessibility Initiative), which in turn is part of the W3C (short for World Wide Web Consortium). These guidelines have been translated into several languages, including German.
WCAG can be considered the most important, general set of rules when it comes to digital and accessible communication. PDF is also considered a possible technology of web content, which is why WCAG also applies to PDF.
For the technical implementation of accessible PDFs, however, the PDF/UA standard is required, not the WCAG.
WCAG is referred to in many national and international laws on digital accessibility. foot