> For the complete documentation index, see [llms.txt](https://docs.eximee.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eximee.com/documentation/documentation-en/budowanie-aplikacji/interfejs-uzytkownika/wcag/dobre-praktyki-wcag-szablony-wydrukow-low-code.md). # 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 previewing 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 an external company, so the results of its reports and analyses are not the only ones to rely on completely, because it is not the only available tool of this kind, and other solutions may offer information and analyses that may differ to some extent. {% endhint %}

**Figure 2.** HTML document structure tree

**Figure 3.** HTML document structure preview

## Axes4 Axes4 - - an online tool generating an accessibility report. It is limited compared with PAC in terms of more detailed analysis with error indications and there is no possibility to preview the PDF structure.

## Screen readers The information is located [here](#dobrepraktykiwcagszablonywydrukow-lowcode-czytnikiekranowe) ## Print metadata declarations In the context of accessibility **\** we can declare metadata or other additional information that does not directly affect visual formatting. {% hint style="danger" %} **\** for correct operation in the document structure it must be located between the tag **\**, and the first **\** {% endhint %} Screen readers can interpret these values. According to UA and WCAG assumptions, the metadata should include **the application 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 included in the context of the tag **\** Example: ```xml ...

``` ## Modifying element roles By default, elements automatically have corresponding types set 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 by using the "role" attribute. **The default \ has the \

role assigned**`.` ``` ... Header with H1 tag Paragraph in a section ... ``` In order to omit some elements in the PDF structure, so they are not visible to a screen reader, we can use **role="artifact"**. This is useful to skip, for example, elements such as **\** such as page headers and footers, which are not useful for blind users when read by a screen reader. Example use for a header: ``` ``` There is also the possibility to "wrap" content that we want to omit in the PDF structure using the <**fo:wrapper>** element with the role set to "artifact". Example for displaying the date format dd-mm-yyyy under a field: ``` dd - mm - yyyy ``` ## Displaying empty cells For creating elements that do not need to present a value and may be empty, a non-breaking space or characters in the same color as the print background should not be used. Example of a template for an unchecked checkbox causing an accessibility report error due to the use of color="white", which causes a white character to be 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. ``` X ``` ## Spacing between elements - avoiding empty rows A bad practice is to use elements such as fo:block with non-breaking space characters to increase the spacing between elements in the printout. The same effect can be achieved using styles such as **margin-top** and **margin-bottom.** This avoids unnecessary empty elements in the document structure. When 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 (article on the Consdata blog) [Accessibility in PDF - barrier-free documents](https://blog.consdata.tech/2025/04/28/dostepnosc-w-pdf-dokumenty-bez-barier.html) {% endhint %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## 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, and the optional `goal` query parameter: ``` GET https://docs.eximee.com/documentation/documentation-en/budowanie-aplikacji/interfejs-uzytkownika/wcag/dobre-praktyki-wcag-szablony-wydrukow-low-code.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.