# PDF accessibility checklist

### Before you export (from Word, PowerPoint, Excel) 

Use the [Microsoft Office accessibility checklist](/digital-accessibility-for-sf.gov-editors/document-accessibility-for-sf.gov-editors/resources/microsoft-office-accessibility-checklist.md) to make your document fully accessible.

### In the PDF 

Fix small issues in Acrobat if needed — but for big fixes, go back to your Office file and re-export.  

Remember that if you make changes in the PDF instead of the Office file, you’ll need to make them again the next time you export the Office file to a PDF. 

* Run the Accessibility Checker (All tools → Prepare for accessibility) 
* Make sure the PDF is tagged 
* Confirm headings are properly tagged (H1, H2, H3) 
* Add alt text for meaningful images; mark decorative ones as decorative 
* Ensure lists and tables are tagged correctly 
* Verify form fields have labels, tooltips, and correct tab order 
* Confirm there’s a document title in Properties 
* Make sure the language is set 
* Check reading order is logical 
* Ensure links are descriptive (no raw URLs) 
* Do not use scanned images of text—run optical character recognition (OCR) in Adobe Acrobat if needed 

{% hint style="info" %}
Do as much accessibility work as possible in the original file (Word, PowerPoint, Excel) before exporting to PDF. Acrobat Pro is best for final checking and fixes. 
{% endhint %}

### Quick testing in Acrobat Pro 

* Use the down arrow key on the tag tree to test reading order 
* Zoom in: text should stay crisp (not blurry or pixelated)  

{% file src="/files/en1sk7HuZRSe6VvNT4Q3" %}
Print a one-page version of this checklist
{% endfile %}


---

# 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://sfdigitalservices.gitbook.io/digital-accessibility-for-sf.gov-editors/document-accessibility-for-sf.gov-editors/resources/pdf-accessibility-checklist.md?ask=<question>
```

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.