axesPDF Guide EN User Guide
axesPDF Guide EN User Guide
User Guide
V07.2021
Content
Introducing axesPDF® .................................................................................................................. 4
PDF/UA, the global standard for PDF accessibility ............................................................... 4
A comprehensive set of tools ................................................................................................. 5
A basic workflow for checking and remediating PDF documents ...................................... 6
Working with accessible PDF documents ................................................................................... 7
What if the PDF document doesn’t have good basic tagging structure? ........................... 7
Installing axesPDF® ...................................................................................................................... 8
System requirements .............................................................................................................. 8
Downloading and installing axesPDF® ................................................................................. 8
Activating axesPDF® .................................................................................................................... 9
Setting up a personal license ................................................................................................. 9
Setting up licenses for several people in an organization .................................................. 9
Getting familiar with the axesPDF® user interface................................................................. 10
Quick access toolbar .............................................................................................................. 10
Toolbar ribbon tabs ............................................................................................................... 11
Main menu ........................................................................................................................ 11
Logical Structure ribbon tab ............................................................................................ 11
Content ribbon tab........................................................................................................... 12
Font ribbon tab................................................................................................................. 12
Extras ribbon tab .............................................................................................................. 12
Viewer ribbon tab ............................................................................................................ 13
Document view ................................................................................................................. 13
Logical Structure Tree pane ............................................................................................. 13
Task panes ......................................................................................................................... 14
Preview panel ................................................................................................................... 18
Checking your PDF document ................................................................................................... 19
Visually inspect your PDF document ................................................................................... 20
Fixing PDF/UA problems ............................................................................................................ 21
Basic requirements problems ............................................................................................... 21
Content ............................................................................................................................. 21
Natural language.............................................................................................................. 22
Introducing axesPDF®
You can use axesPDF® to check and remediate PDF documents for compliance
with the PDF/UA (ISO 14289), WCAG 2.1, and Section 508 standards.
The checking and remediation tools in axesPDF® help you produce fully PDF/UA
compliant documents with ease. You can use these tools to check your Microsoft
Word, Adobe Acrobat, or Adobe InDesign documents.
Accessibility issues are found quickly, and you can easily fix most of them.
Important: To use AXESPDF ®, your PDF document must contain a tag structure.
If it doesn’t, you can create a tagged PDF by converting the source document or
adding tags using a PDF editor.
"The primary purpose of ISO 14289 (known as PDF/UA) is to define a specific use
of the structure and tagged PDF features in PDF 1.7, which provide a mechanism
for reuse of PDF page content, especially in the accessibility context."1
For more information about the PDF/UA and the PDF/A standards, check out the
list of resources in the PDF Association website2.
1
PDF association. (2014, October 7). ISO 14289 (PDF/UA). Retrieved from
https://www.pdfa.org/resource/iso-14289-pdfua/
2
https://www.pdfa.org/resource/
■ One top-level container tag. All other tags are nested within the container tag.
■ All relevant content elements are tagged.
■ The tag order is the same as the preferred reading order.
■ Tags are nested correctly.
■ All elements or content that belongs together are kept together. For example,
paragraphs, tables, or lists that are span page breaks or column breaks are not
divided into several tags.
■ All links to external destinations, like websites or other documents, are
correctly tagged and are clickable.
What if the PDF document doesn’t have good basic tagging structure?
If your document doesn’t have tags or a good basic tagging structure, you can
create a tagged PDF by converting the source document or adding tags using a
PDF editor.
Once the conversion is finished, you can use axesPDF® to evaluate the PDF, check
the PDF/UA compliancy, and fix any outstanding issues.
Installing axesPDF®
System requirements
axesPDF® works with the following operating systems:
Note: If you have a previous version installed, you must uninstall it first.
Start the setup program by navigating to the where you saved the downloaded
file and double-click axesPDF.Setup.exe.
The installation wizard guides you through the rest of the process.
3
https://www.abledocs.com/en/products-services/axespdf/download
Activating axesPDF®
You can use axesPDF® in Trial Mode or activate a license to use all the available
features. You set up licenses for a individuals or organizations.
If you choose to run the add-in in Trial Mode, when you create a PDF, each page
will have a watermark, and some characters will be randomly colored.
4
https://support.axes4.com/hc/en-us/articles/360013781220
5
https://support.axes4.com/hc/en-us/articles/360013781020
6
https://support.axes4.com/hc/en-us/articles/360013849319
Main menu
Use the main menu to open, close or save files, to read the product information,
or to quit axesPDF®.
■ Metadata
■ Annotations
■ Navigation
■ Accessibility Support Properties
Document view
The Document view is the default view of the PDF document that you are
working on.
If you select a structure element in the Logical Structure Tree pane, or select an
error in the Checker task pane, the corresponding element is highlighted in the
Document view.
When you click a tag in the structure tree, the corresponding area is highlighted in
the Document view.
You can also edit tag names by double-clicking the tags and use the Search Tag
field to search for specific tags in the structure tree.
Task panes
There are several task panes that you can use to view the results of a PDF/UA
check, and to edit the properties, settings, and tags in your PDF document.
The Properties task pane shows all the properties and attributes for the tag that
you select in the Logical Structure Tree pane. You can change all properties of the
selected tag, including the structure type.
Use the Settings task pane to specify several general settings for your PDF
document that are relevant to the starting view or the assistive technology used to
access the document.
You can click Default to set standard values for layout, window options and user
interface, which are preferable for accessibility. The default settings include:
Layout
Use the Checker task pane to check your document for PDF/UA issues. When you
first open the document, click Refresh to perform the analysis and view the list of
issues.
The error messages are organized in categories. You can expand each category to
see the specific issues.
Double click on an error message to see the corresponding issue highlighted in the
Document view and in the Logical Structure Tree pane.
Use the Role map task pane to review role mappings in your PDF document.
You can also sort and filter the items in the Structure Type and Role lists.
Use the Destination task pane to review the targets of the internal links and the
associated structure elements in your PDF document.
Preview panel
Use the Preview panel to see the content of your PDF document as it is presented
to a screen reader or assistive technology. You can use the Preview panel to
visually check the logical order and the presentation of the content.
In the Preview panel, the different structure elements are represented by symbols.
For more information, go to this article in the Help Center7.
Usually you start with the PDF/UA check. Then you examine the errors, choose the
corresponding commands, and make the corrections.
7
https://support.axes4.com/hc/en-us/articles/360008791960-Overview-of-the-symbols-in-the-
screenreader-preview
Content
Problem: “Artifact present inside tagged content”
A marked content element that is referenced by the logical structure contains a
nested artifact.
1. Remove all the artifacts by opening the Content ribbon tab and clicking
Remove Artifacts.
2. Mark the content elements again by clicking Artifact non-tagged content.
Problem: “Tagged content present inside an Artifact”
There is a marked content container with a MCID that is nested inside an Artifact.
There is no standard method for fixing this error; you must examine the affected
content.
If the related element is marked content that is not referenced by the logical
structure:
■ Image objects
■ Path objects
■ Text objects
To fix these issues:
Natural language
Language assignments can be set on three different levels in a PDF document:
■ Document level
■ Structure level
■ Content level
If the natural language for a document cannot be identified during a PDF/UA
check, the then it cannot be determined for the following type of content in the
document:
■ Outline items
■ Text objects
■ Actual text
■ Alternative text
■ Alternate name of a form field
■ Contents entries
To fix this issue:
1. In the Settings task pane, in the Language field, enter the required language
code. For example, use "en-GB" for British English, "en-US" for US English or
"de-DE" for German.
Alternative Descriptions
Problem: “Alternative description missing for an annotation”
An alternative description about the destination of a link is missing.
1. Add an alternative description by opening the Extras ribbon tab and clicking
Set Contents key of Link annotations.
An alternative description is added to every link tag.
Notes
Problem: “ID missing in Note structure element”
There are Note-Tags without ID.
Role Mapping
Problem: “Non-standard structure type “Story” is neither mapped to a standard structure type
nor to another non-standard structure type”
Every non-standard structure type must be mapped to a standard structure type.
This mapping is missing from the document.
There is a Standard structure type that is remapped to the same structure type.
According to the PDF/UA standard, this is not allowed.
Structure Elements
Problem: “First heading is not on the first level”
In every document, the first heading must be an H1. Heading levels must not be
skipped; for example, an H3 must not follow an H1.
1. In the Logical Structure Tree pane, double-click the first tag heading and
change it to “H1”.
Problem: “Table header cell has no associated subcells”
In a table, there are header cells (<TH>) that do not have associated data cells
(<TD>).
Programs like screen readers cannot recognize the relationship between the
header and the data cells.
1. In the Checker task pane, double click the error message to move to the
corresponding header cell. The header cell is also highlighted in the Logical
Structure Tree pane.
2. For a simple table, in the Properties task pane, set the correct scope of the
selected header cell.
3. If table header cells do not apply for a whole column or row, you have a
complex table. In that case, you must set the reference between header cells
and data cells by using header IDs. In the Viewer ribbon tab, click Table.
1. In the Checker task pane, double-click on error so that the related figure and
figure tag is highlighted.
2. In the Properties task pane, add a bounding box by clicking the "+" for one
of the empty attribute fields; for example, the attribute "Left". The correct
bounding box is automatically created.
To fix this issue, add the required tag using a PDF tag editor.
1. In the Checker task pane, double-click on the error so that the related
heading and heading tag are highlighted.
2. To change the name of the heading tag, on the Logical Structure ribbon tab,
click Rename Tags, and in the Rename Tags dialog box, type a new name for
the selected tag.
You can also manually edit the tag name in the Logical Structure Tree pane.
Structure Tree
Problem: “Art structure element used as root element”
The document contains an Article structure element that, semantically, is not used
correctly.
1. In the Checker task pane, double-click the error. The corresponding tag is
highlighted in the Logical Structure Tree pane.
2. Click the tag and enter a semantically correct root tag name; for example,
"Document".
You can also create a new root tag "Document" in a PDF tag editor and then nest
all other tags under it.
1. In the Checker task pane, double-click the error. The corresponding tag is
highlighted in the Logical Structure Tree pane.
2. Click the tag and enter a semantically correct root tag name; for example,
"Document".
You can also create a new root tag "Document" in a PDF tag editor and then nest
all other tags under it.
1. In the Checker task pane, double-click the error. The corresponding tag is
highlighted in the Logical Structure Tree pane.
2. Click the tag and enter a semantically correct root tag name; for example,
"Part".
1. In the Checker task pane, double-click the error. The corresponding tag is
highlighted in the Logical Structure Tree pane.
2. Click the tag and enter a semantically correct root tag name; for example,
"Document".
You can also create a new root tag "Document" in a PDF tag editor and then nest
all other tags under it.
The figure tag is an inline level element. If it is used as a block level element, the
attribute “Placement: Block” is required. Otherwise, some assistive technologies
are not able to present it correctly.
1. In the Checker task pane, double-click the error. The corresponding tag is
highlighted in the Logical Structure Tree pane.
2. On the Logical Structure ribbon tab, click Fix Placement.
Problem: “Possibly inappropriate use of a Form structure element”
Some form tags in the document are not used correctly. In most cases, it is due to
the placement attribute.
The form tag is an inline level element. If it is used as a block level element, the
attribute “Placement: Block” is required. Otherwise, some assistive technologies
are not able to present it correctly.
1. In the Checker task pane, double-click the error. The corresponding tag is
highlighted in the Logical Structure Tree pane.
2. On the Logical Structure ribbon tab, click Fix Placement.
The formula tag is an inline level element. If it is used as a block level element, the
attribute “Placement: Block” is required. Otherwise, some assistive technologies
are not able to present it correctly.
1. In the Checker task pane, double-click the error. The corresponding tag is
highlighted in the Logical Structure Tree pane.
2. On the Logical Structure ribbon tab, click Fix Placement.
Problem: “Possibly inappropriate use of a Note structure element”
Some note tags in the document are not used correctly. In most cases, it is due to
the placement attribute.
The note tag is an inline level element. If it is used as a block level element, the
attribute “Placement: Block” is required. Otherwise, some assistive technologies
are not able to present it correctly.
1. In the Checker task pane, double-click the error. The corresponding tag is
highlighted in the Logical Structure Tree pane.
2. On the Logical Structure ribbon tab, click Fix Placement.
Problem: “Sect structure element used as root element”
There are Section structure elements in the document that are not used correctly.
1. In the Checker task pane, double-click the error. The corresponding tag is
highlighted in the Logical Structure Tree pane.
2. Click the tag and enter a semantically correct root tag name; for example,
"Document".
You can also create a new root tag "Document" in a PDF tag editor and then nest
all other tags under it.
Document Settings
Problem: “DisplayDocTitle entry is not set”
The file name is set as the window title; it should be the title of the document.
Metadata
Problem: “Title missing in document’s XMP metadata”
The document is missing a title.
1. In the Settings task pane, in the Title field, enter the title of the document.
You can also add a document title using a PDF editor.
Glossary
Here is a list of terms used in the tools that you use to create and test PDF
documents.