A member applies for a home equity loan on your website. They download the disclosure PDF, open it in Adobe Reader, and their screen reader announces: "Graphic. Graphic. Graphic." No rates. No terms. No context. Just a series of unlabeled images where the text should be. They close the file, call your branch, and spend 20 minutes on hold. That friction is not a hypothetical. It happens on credit union websites every day, and most marketing and operations teams have no idea it is occurring.
What makes a PDF inaccessible in the first place
The core problem is that most PDFs are generated as flat image files rather than tagged, structured documents. When your compliance team exports a rate sheet from Word, or your core system generates a loan disclosure as a print-ready PDF, the output often looks fine on screen but contains no underlying text layer that assistive technology can read. A screen reader needs tagged headings, logical reading order, alternative text for any charts or tables, and properly labeled form fields if the document is interactive. Without those tags, the file is functionally invisible to members who rely on screen readers, refreshable Braille displays, or keyboard-only navigation.
The scope of this goes beyond screen reader users. Tagged PDFs also benefit members using mobile devices with pinch-to-zoom, older members who increase their system font size, and anyone reading on a low-resolution display. WCAG 2.1 Level AA is the standard most credit unions reference, and current NCUA guidance on digital accessibility increasingly points in that direction. But even setting aside regulatory considerations, the practical member service case is straightforward: if someone cannot read your Truth in Lending disclosure independently, you have created a barrier between them and a financial decision that affects their household.
The three most common PDF failures on credit union sites
After reviewing dozens of credit union websites, the same problems appear repeatedly. First, scanned documents. If your team scans a signed paper form and uploads it as a PDF, you have uploaded an image. There is no text layer at all. A screen reader will either skip the file entirely or read out the file name. Second, tables without structure. Rate tables are among the most important content in any disclosure, and they are among the most frequently broken. A sighted user sees rows and columns; a screen reader sees a stream of numbers with no headers to anchor them. Without proper table markup, a member cannot tell which rate corresponds to which term or which fee applies to which product. Third, missing document structure. Headings, lists, and reading order all need to be explicitly tagged in a PDF. A document that looks organized visually can be completely scrambled when read linearly by assistive technology.
What you can actually fix, and how to prioritize
Start with an audit of your highest-traffic PDFs. Pull your site analytics and identify which documents members download most often. For most credit unions, that list includes the Truth in Lending disclosure, the fee schedule, the membership agreement, and any rate sheets linked from the homepage or product pages. Those four categories are where inaccessible PDFs cause the most friction and carry the most regulatory exposure.
For each document, run it through Adobe Acrobat's built-in Accessibility Checker (available in Acrobat Pro) or the free PAC 3 tool, which checks against PDF/UA standards. These tools will flag untagged content, missing alt text, and reading order issues. They are not perfect, but they will surface the most significant problems quickly. If your team does not have Acrobat Pro, this is worth the subscription cost given how many disclosures you likely publish annually.
Remediation has two paths. The better long-term path is fixing the source documents. If your disclosures originate in Word or InDesign, those applications can export tagged PDFs when configured correctly. Word's built-in accessibility checker will catch most heading and alt text issues before you export. The shorter-term path is remediation of existing PDFs in Acrobat Pro, where you can add tags, correct reading order, and label table headers manually. For a small library of documents, this is manageable in-house. For a large library, several vendors specialize in PDF remediation at scale, typically charging per page.
One thing worth flagging to your vendor or web team: how PDFs are linked on your site matters too. Every PDF link should include the file format and approximate size in the link text, for example, "Home Equity Disclosure (PDF, 180 KB)." That is a WCAG requirement, and it is a quick fix that respects the member's time and bandwidth.
How to move this from a to-do to a done
Accessibility improvements stall when they live on a vague list rather than a specific plan. Here is a concrete sequence to get started. This week, identify your five most-downloaded PDFs using Google Analytics or your CMS reports. Next week, run each one through PAC 3 or Acrobat's checker and document the failure types. Then bring those results to a 30-minute meeting with whoever manages your compliance documents and your web vendor. The question to ask your vendor directly: "Can our CMS flag PDFs that fail basic accessibility checks before they are published?" Some platforms support this; many do not, but asking the question starts the conversation. If you are working with a managed website provider, ask whether PDF accessibility remediation is in scope for your current agreement or available as an add-on. From there, set a remediation deadline for your top five documents before moving to the broader library. Small credit unions with limited staff can realistically remediate five to ten documents per quarter. That pace, sustained, clears a meaningful backlog within a year.