# WCAG best practices - print templates (low-code) ## Free tools for verifying print accessibility ## PAC PAC - (Windows) - a tool used to check whether PDF files comply with accessibility requirements. It can be used to verify whether our PDF meets PDF/UA and WCAG standards and generate a report based on that. It also allows you to preview the document structure for a screen reader. {% hint style="info" %} It should be noted that PAC is not an official tool created by the ISO committee, but by a third-party company; therefore, the results of its reports and analyses are not the only ones to rely on completely, because they are not the only available tool of this type, and other solutions may offer information and analyses that may differ to some extent. {% endhint %}

Figure 1. PAC main panel

Figure 2. Document HTML structure tree

Figure 3. Document HTML structure preview

## Axes4 Axes4 - - an online tool that generates an accessibility report. It is more limited than the PAC tool in terms of more detailed analysis with error indication, and it does not allow previewing the PDF structure.

Figure 4. Accessibility report

## Screen readers Information is available [here](#dobrepraktykiwcagszablonywydrukow-lowcode-czytnikiekranowe) ## Print metadata declarations In the context of accessibility **\** we can declare metadata or other additional information that do not directly affect the visual formatting. {% hint style="danger" %} **\** for proper operation in the document structure, it must be placed between the tag **\**, and the first **\** {% endhint %} Screen readers can interpret these values. According to UA and WCAG assumptions, the metadata should include **the document title, language, and the DisplayDocTitle setting**. Example declaration: ``` pl <- language declaration true <- DisplayDocTitle setting AwZ document <- title Document author <- author AwZ document <- description ``` ## Assigning the correct tag to email addresses and links Email addresses and links to external addresses should be contained within the context of the tag **\** Example: ```xml ... ``` ## Modifying the role of elements By default, elements are automatically assigned their corresponding types in the generated PDF structure. (H1 to H6 for headings, L for lists, etc.). However, it is possible to override the default roles if we want to improve the default structure using the "role" attribute. **The default \ is assigned the role \

**`.` ``` ... Header with H1 tag Paragraph in the section ... ``` To omit some elements in the PDF structure so that they are not visible to the screen reader, we can use **role="artifact"**. This is useful for skipping elements such as **\** such as page headers and footers, which are unhelpful for blind users when read by a screen reader. Example of use for a header: ``` ``` It is also possible to "wrap" content that we would like to omit in the PDF structure using the <**fo:wrapper>** element with the role "artifact" assigned. Example for presenting the date format dd-mm-yyyy under the field: ``` dd - mm - yyyy ``` ## Presentation of empty cells When creating elements that do not need to present a value and may be empty, you should not use a non-breaking space or characters in the same color as the print background. Example of a template for an unchecked checkbox causing an accessibility report error due to the use of color="white", which results in a white character displayed on a white background: ```xml xsl:template name="checkbox_template"> ✕ ✕ ``` Instead, it is better to create an empty cell with an assigned style **padding-top** and **padding-bottom**, which will visually give us the same appearance of the cell without the need for any unnecessary character inside it. ``` X ``` ## Spacing between elements - avoiding empty rows It is bad practice to use elements such as fo:block with non-breaking spaces to increase the spacing between elements in the printout. The same effect can be achieved by using styles such as **margin-top** and **margin-bottom.** This way we avoid unnecessary empty elements in the document structure. If you want to increase the spacing between rows **\** you can use the table property **border-collapse="separate"** and **border-spacing="...".** For example: ``` Row 1 Row 2 ``` {% hint style="info" %} Accessibility in PDF (Consdata blog article) [Accessibility in PDF - barrier-free documents](https://blog.consdata.tech/2025/04/28/dostepnosc-w-pdf-dokumenty-bez-barier.html) {% endhint %} --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.eximee.com/documentation/documentation-en/budowanie-aplikacji/interfejs-uzytkownika/wcag/dobre-praktyki-wcag-szablony-wydrukow-low-code.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.