Avoid PDFs

The best long-term practice is to convert all content into native UAMS CMS pages. This provides:

• Superior mobile experience (PDFs are notoriously difficult on phones)
• Easier updates and version control
• Natural accessibility (headings, lists, alt text, etc. work automatically)
• Better SEO and search engine indexing
• Full compliance with WCAG 2.1 Level AA (required by DOJ Title II ADA rule by April 24, 2026)

Blackboard Ally for Websites gives PDFs the lowest accessibility scores when they are untagged or complex — avoid them unless absolutely necessary.

When a PDF Is Truly Required

Only use PDFs for:

• Official fillable forms
• Documents that must be printed exactly as designed (e.g., certificates, certain reports)
• Complex layouts that cannot be replicated in the CMS

Even then, the PDF must be fully tagged and meet WCAG 2.1 Level AA / PDF/UA standards by April 24, 2026. See the full guide: Create and Verify PDF Accessibility in Acrobat Pro

Questions to Ask Before Posting a PDF

1. Why am I sharing this information? If it’s informational content (event details, policies, guides), put it on a UAMS CMS page instead.
2. Will this information need to be updated in the future? PDFs create maintenance nightmares — updates require replacing the file and fixing every link.
3. Can the submitter provide the content in simple text format? Always request a Word document or plain text so you can build a proper web page.
4. Is the same content already available in webpage format? If yes, remove the PDF or make it secondary. If offering both, use descriptive link text (e.g., “2025 Benefits Guide (Accessible PDF, 2 MB)”).

Never Do This

• Post screenshots of flyers or print materials as PDFs
• Use PDFs of text that could easily be web content
• Untagged or unscannable PDFs (Ally will flag them immediately)