What Actually Makes a PDF Accessible (Hint: It’s Not Font Size)

Accessibility isn’t about enforcing a specific font size, it’s about making content readable. Examples include using responsive design to style structural elements like headings and lists, which provide visual hierarchical cues for sections of information, and ensuring content properly resizes for different devices and screen magnifications.

For a digital file (including PDFs, Word documents, PowerPoint and webpages) to be accessible, it must be structured so assistive devices can interpret it correctly. That means:

• Clear, logical headings or slide titles
• Complete file properties (metadata), including a meaningful document title
• Images described with alternative text
• A logical reading order
• Sufficient color contrast
• Fonts that are easy to read (see the UCSF Font Guide for best practices)
• No animations

For PDFs specifically, files must contain real text (not images) and be properly tagged so screen readers can navigate the content. Accessibility checkers can help flag issues, but passing a checker alone doesn’t guarantee accessibility.

Finally, whenever possible, consider publishing content as a webpage instead of a PDF. Webpage’s are often the most accessible and sustainable option! For more information, check out our help documentation on Accessible PDFs or attend one of our Live Help Sessions.