Finalsite + AudioEye: Fix PDF flags

A practical guide for content editors: how AudioEye flags PDF accessibility issues, how to decide which PDFs to prioritize, and how to address the most common problems. Part of the AudioEye how-to series.

💡Quick answers

  • What does AudioEye mean when it flags a PDF? A linked document does not meet WCAG 2.1 standards. Common issues include missing "tags," no logical reading order, or missing alt text.
  • Can AudioEye fix this automatically? No. Remediation happens inside the PDF file itself (using a tool like Adobe Acrobat Pro) before you re-upload it to Finalsite.
  • Do I have to fix every PDF? Not necessarily. Use this as an opportunity to "clean house." If a document is old or rarely used, unpublish it. If it is high-traffic, consider converting it to a web page.
  • How do I find the flagged file? Add /?oss=1 to the page URL to highlight the link, or use the AudioEye dashboard to see a full list of documents.

In this article


Why PDF accessibility matters

PDFs are one of the most common sources of accessibility failures. Unlike web pages, PDFs carry their accessibility data "baked" into the file. A document created by scanning a paper page or using "Print to PDF" results in a flat image that a screen reader cannot read.

This affects users who are blind, those with low vision who use zoom tools, and users who depend on a logical reading order to understand complex documents.

Step 1: Find and prioritize your flagged PDFs

Open the flagged page and add /?oss=1 to the end of the URL. The scanner will highlight the link to the PDF. Note the file name so you can locate it in your Resources module.

Pro tip: Where used in Resources

Check the "Where Used" status in Resources. If a document isn't linked anywhere else and is outdated, deleting it is the fastest way to resolve the flag. Learn more in the article, "Find where resources are used on your site."

Step 2: Decide the best path forward

Before spending time fixing a PDF, ask these three questions:

Is this document still needed?

If the document is an old newsletter or an expired flyer, simply remove it. An inaccessible document that no longer exists is no longer a compliance issue.

Can this be a Composer page instead?

HTML is inherently more accessible and easier to maintain. High-traffic items like student handbooks or enrollment steps are much better suited as native web pages than PDFs.

Must this remain a PDF?

Official signed forms, legal board minutes, and high-density reference materials are valid candidates for PDF remediation. If it must stay a PDF, proceed to Step 3.

Step 3: Address the most common issues

PDF remediation requires a professional tool such as Adobe Acrobat Pro, PAC 2024, or PAVE. The specific steps vary by tool, but the underlying concepts are the same. Consult your tool's documentation for the exact menu paths and features. Most have built-in accessibility checkers to guide you through these issues.

Missing document tags

Tags provide the structure (headings, paragraphs, lists) that screen readers use to navigate. Most remediation tools offer auto-tagging as a starting point, but you'll need to verify the tags are correct and in logical order.

Pro tip: Never use "Print to PDF." This creates a flat image and strips all tags. Always use "Save as PDF" or "Export to PDF" from Word, InDesign, or similar applications.

No logical reading order

Screen readers follow the reading order embedded in the PDF. Verify the content flows correctly (typically top-to-bottom, left-to-right) so screen readers don't skip around or misinterpret the layout. Most tools have a "Reading Order" or "Content" panel where you can reorder elements.

Missing alt text or language

Images and figures need alternative text descriptions so screen readers can convey them to users. Additionally, set the document's language in the file properties so screen readers use the correct pronunciation and grammar rules.

Step 4: Re-upload and verify

  1. Save your remediated PDF.
  2. In Finalsite Resources, upload the new version, replacing the old file. If the file name is the same, all existing links will update automatically.
  3. Reload the page with /?oss=1.
  4. Confirm the scanner no longer flags the link.

Recommended tools

Still stuck?

PDF remediation can be complex. If a document is too large or technical to fix manually, email accessibility@finalsite.com with the page URL and the name of the flagged document.

Related articles

Was this article helpful?
2 out of 2 found this helpful

Comments

0 comments

Please Sign in to leave a comment if you don't see the comment box below.