--- title: "PDF Accessibility" slug: "pdf-updates" updated: 2024-11-27T16:53:05Z published: 2024-11-27T16:53:05Z canonical: "kb.easysend.io/pdf-updates" --- > ## Documentation Index > Fetch the complete documentation index at: https://kb.easysend.io/llms.txt > Use this file to discover all available pages before exploring further. # PDF Accessibility ## Article Overview The following article describe the PDF accessibility feature. NOTE The PDF accessibility feature is available on environments with version 20.12.0 and above. ## **What is an Accessible PDF?** A PDF document is considered accessible if it can be used/accessed by all users, including users with disabilities. For a PDF to be considered accessible, it should be compliant to different accessibility standards. ### **PDF Characteristics** PDFs are typically created from a source document such as a Microsoft Word and are then exported into the PDF format. However, many PDF files are created by scanning hard copy documents and are simply images of text. Unfortunately, image-based PDFs are completely inaccessible as they are and require conversion into readable text using an Optical Character Recognition (OCR) software before they become accessible. ### **How to Create an Accessible PDF Using EasySend's Platform?** (See **Figure 1** to **Figure 3**) To create PDFs with accessible PDF-fillings, perform the following steps: 1. Create markers for the Accessibly Tree that works with screen readers. ![](https://cdn.document360.io/45e1a1b1-1964-46f1-939e-f40bde9b50fa/Images/Documentation/pdf-accessibilitytemp-image-y0h43t1v.png) **Figure 1: Accessibility Tree** 1. Create input fields (AcroForms) that work together with the accessibility tree you created. ![](https://cdn.document360.io/45e1a1b1-1964-46f1-939e-f40bde9b50fa/Images/Documentation/pdf-accessibilitytemp-image-5gna3pn7.png) **Figure 2: Fields** NOTEEach field must be defined with an appropriate type before the file is uploaded to EasySend's platform so it will be recognized by it correctly. The available types of fields are: - Text input - Checkbox - Figure (for an image) - signature - Radio button 1. Upload the PDF to EasySend's platform. ![](https://cdn.document360.io/45e1a1b1-1964-46f1-939e-f40bde9b50fa/Images/Documentation/pdf-accessibilitytemp-image-aakh8zjx.png) **Figure 3: Uploaded Accessible PDF** NOTEThe platform will recognize the combination of the markers and the input fields (from steps **1** and **2**) and preserve them.NOTEThe EasySend's platform also preserves fields' alternative text. When an alternative text is set for a field, before the file is uploaded to the platform, it will be the text read by a screen reader. This is relevant mostly for figures (images) and signatures field types but not just. For example, if the alterative text of a figure is "customer's ID attachment", this will be the text read by a screen reader. ### **Uploaded Accessible PDF** (See **Figure 4** to **Figure 6**) When an accessible PDF was uploaded to the platform, the following message appears: ![](https://cdn.document360.io/45e1a1b1-1964-46f1-939e-f40bde9b50fa/Images/Documentation/pdf-accessibilitytemp-image-tehywy5w.png) **Figure 4: Uploaded Accessible PDF Example** After clicking Ok, to preserve the original PDF accessibility format, the **Textual PDF** (2) checkbox must be checked in PDF properties: ![](https://cdn.document360.io/45e1a1b1-1964-46f1-939e-f40bde9b50fa/Images/Documentation/pdf-accessibilitytemp-image-nyuahd9p.png) **Figure 5: Textual PDF** The PDF will be displayed with marked fields with a dashed border (3). The **Field Properties** section will be locked for editing (4) except for the **label** (5) which is used internally for organizing the marked fields and the **fieldName** (6) which enables the marked fields to be connected to the Model. ![](https://cdn.document360.io/45e1a1b1-1964-46f1-939e-f40bde9b50fa/Images/Documentation/pdf-accessibilitytemp-image-ncyw3rb7.png) **Figure 6: Uploaded Accessible PDF Example** NOTEAfter connecting a field to the model, it is also possible to set a groupValue property in case of a radio question. For additional information about the groupValue property, see the [Creating and Defining a PDF](/v1/docs/creating-and-defining-a-pdf) article. ### **Combining Accessible and Inaccessible Fields** A document with a combination of accessible and inaccessible fields that will not be read by a screen reader is allowed. When manually adding inaccessible fields, their border will be solid and not dashed. In addition, all the properties of an inaccessible field are editable. ### **Accessible PDF Troubleshooting** (See **Figure 7**) In some cases, an accessible PDF is uploaded to the platform and some of the fields are left unmarked (1): ![](https://cdn.document360.io/45e1a1b1-1964-46f1-939e-f40bde9b50fa/Images/Documentation/pdf-accessibilitytemp-image-vvtnd143.png) **Figure 7: Uploaded Accessible PDF Example** To troubleshoot this issue, On the original PDF, verify that: 1. Each field was defined with a field type supported by EasySend's platform: - - Text input - Checkbox - Figure (for an Image) - Signature - Radio button 1. Each Input field has a unique name - no duplication is allowed. 2. An input field name does not contain the following words: - - undefined - null - none 1. Upload the accessible PDF to the platform again.