PDF Accessibility for K–12 Districts: The Most Common Mistakes and How to Fix Them
By Kalin Schoephoerster | KShep Creative
Think about how many PDFs your district publishes in a year. Family handbooks. Board meeting minutes. Staff onboarding guides. Emergency procedures. Special education notices. Enrollment forms. Policy documents.
Now consider how many of those are actually accessible to someone using a screen reader, navigating with a keyboard, or relying on assistive technology because of a visual or cognitive disability.
For most districts, the honest answer is: not many.
That's not a criticism — it's a reflection of how PDFs have always been created. Staff open Word, type what they need, hit "Save as PDF," and move on. The result looks fine on screen. But for someone whose technology needs to read that document aloud or navigate it by structure, "looks fine" isn't enough.
With ADA Title II compliance deadlines now in effect for larger districts and approaching in 2027 for smaller ones, PDF accessibility has moved from a best practice to a legal expectation. The good news is that most PDF accessibility problems are fixable — and many are preventable if you know what to look for.
Here's where districts most commonly go wrong, and what to do about it.
Why PDFs are a particular accessibility challenge
PDFs aren't inherently inaccessible. A well-built PDF can work beautifully with assistive technology. The problem is that a PDF can look completely normal visually while being entirely unreadable to a screen reader — because what matters isn't the appearance, it's the underlying structure.
Screen readers don't see a page the way a sighted person does. They follow a reading order, interpret heading tags, read alt text for images, and navigate by landmarks. If that structure isn't there — or if it's wrong — the document becomes a wall of noise or silence, depending on the tool.
This surprises a lot of district staff, because the document looks fine. The text is visible. The layout is clean. But if the structure underneath doesn't match what assistive technology expects, the experience for a user with a disability can range from confusing to completely inaccessible.
WCAG 2.2 applies to PDFs, not just web pages. If your district is working toward ADA Title II compliance, your PDF library is part of that work — not separate from it.
The most common PDF accessibility mistakes in K–12 districts
Mistake 1: Scanned documents saved as image-only PDFs
This is the most common and most damaging mistake. When a physical document is scanned and saved as a PDF, the result is essentially a photograph. It looks like a document, but there's no actual text for a screen reader to find — just pixels.
Scanned board meeting minutes, copied staff handbooks, physical forms converted to digital — these show up regularly in district document libraries and on public-facing websites.
The fix: Use OCR (optical character recognition) software to extract the text from scanned documents and make it selectable. Adobe Acrobat Pro has built-in OCR. For new documents, always start digitally rather than printing and scanning.
Mistake 2: No document title or metadata
When someone opens a PDF using a screen reader, the first thing it announces is the document title. If that field is blank — or if it reads something like "Microsoft Word - Final FINAL v3" — that's an immediate barrier to orientation.
This is a small fix that takes less than a minute and makes a real difference for users who navigate multiple documents at once.
The fix: Before exporting to PDF from Word, go to File > Properties and fill in the Title field. In Adobe Acrobat, go to File > Properties > Description. Make the title descriptive and specific — "2025–2026 Staff Handbook" rather than "Handbook."
Mistake 3: Missing or incorrect heading structure
Headings aren't just a visual formatting choice — they're navigation landmarks. A screen reader user can pull up a list of all headings in a document and jump directly to the section they need, the same way a sighted reader might skim a table of contents.
If your document uses large bold text styled manually instead of actual heading tags, it looks like a heading but functions as plain text. The document becomes flat and unnavigable for anyone using assistive technology.
The fix: Use proper heading styles (Heading 1, Heading 2, Heading 3) in Word or Google Docs before exporting to PDF. Don't manually bold and enlarge text to create the appearance of headings — use the styles panel. The structure transfers to the PDF on export when done correctly.
Mistake 4: Images with no alt text
Photos, charts, logos, infographics, and icons all need text descriptions for people who can't see them. Without alt text, a screen reader either skips the image entirely or announces "image" with no further information — neither of which communicates what the image is meant to convey.
This is especially significant for K–12 districts that include charts in board reports, photos in family newsletters, or diagrams in instructional materials.
The fix: Add alt text to every meaningful image before exporting to PDF. In Word, right-click the image and select "Edit Alt Text." Write a brief, specific description of what the image shows and why it matters in context. For purely decorative images (a divider line, a background texture), mark them as decorative so screen readers skip them intentionally.
Mistake 5: Tables without proper structure
Data tables need to be tagged correctly so a screen reader can communicate the relationship between a cell and its header. Without that structure, a table full of numbers becomes a string of values with no context — a user hears "32, 47, 18, 61" with no way to know what those numbers mean or which column and row they belong to.
The fix: In Word, define header rows before exporting — select the top row, right-click, go to Table Properties > Row, and check "Repeat as header row at the top of each page." This signals to the PDF that the top row contains headers. For complex tables already in PDF format, Adobe Acrobat Pro's table editor allows you to tag headers manually.
Mistake 6: Poor color contrast
Text that's light gray on white, yellow on white, or any low-contrast color combination fails WCAG 2.2 contrast requirements — meaning it's difficult or impossible to read for people with low vision or color blindness. This shows up frequently in district documents that use brand colors without checking whether those colors meet contrast standards.
The fix: Before finalizing any document, run your color combinations through a free contrast checker. WebAIM's Contrast Checker (webaim.org/resources/contrastchecker) lets you input foreground and background colors and tells you immediately whether they pass or fail. WCAG 2.2 requires a contrast ratio of at least 4.5:1 for normal text and 3:1 for large text.
Mistake 7: No logical reading order
In multi-column layouts, newsletters, or documents with text boxes and sidebars, the order a screen reader follows may not match what the eye sees. A reader might hear the first column, then jump to a sidebar, then back to the middle of the page — in an order that makes no sense as a reading experience.
The fix: The cleanest solution is to simplify layouts at the source — avoid floating text boxes and complex multi-column designs where possible. For existing PDFs, Adobe Acrobat Pro's Order panel (under Accessibility Tools) shows the current reading order and allows you to drag and reorder elements until the sequence is logical.
Where to start when you have hundreds of PDFs
If reading that list made your to-do list feel significantly longer, here's the most important thing to know: you don't have to fix everything at once.
Prioritize by impact. Start with the documents that reach the most people, carry the most consequence, or are legally required to be accessible:
Family-facing documents — enrollment forms, handbooks, family letters, special education notices
Board materials — agendas, minutes, and reports that are publicly posted
Staff onboarding and required training materials
Any document linked from your district website — these are the highest-visibility items and most likely to be flagged in a compliance review
Documents buried in archives that haven't been accessed in years can wait. Documents your families receive every fall cannot.
If you're not sure where your biggest barriers are, a broader accessibility audit — one that looks at your website, key documents, and public-facing content together — gives you a complete picture of where the gaps are and a prioritized plan for addressing them, rather than tackling documents in isolation. Learn more about accessibility audits →
Building accessible PDF habits your team can sustain
The fixes above are reactive — they address problems that already exist. The bigger win is preventing those problems from accumulating in the first place.
A few habits that make a meaningful difference:
Start in Word with proper styles. The most important accessibility work happens before the PDF is ever created. A document built with heading styles, proper alt text, and defined table headers will export to an accessible PDF. A document built by manually formatting text will not.
Use accessible templates. If your district uses shared templates for common documents — letterhead, meeting agendas, report formats — building accessibility into those templates means every document created from them starts with the right structure. One-time investment, ongoing return.
Train the people who publish most. Not every staff member needs to be a PDF accessibility expert. But the people who regularly publish documents to your website, send home family communications, or create staff-facing resources benefit enormously from even a short, focused training on the basics. The goal isn't perfection — it's building awareness of the few highest-impact habits.
If your district is looking for accessible document templates or staff training on accessible content creation, that's work that connects directly to your broader ADA Title II compliance effort. Explore accessibility audit and remediation services →
Ready to understand where your district stands?
PDF accessibility is one of the most concrete and fixable parts of a digital accessibility effort — but it's hard to know where to start without a clear picture of what you're working with.
If your district is navigating ADA Title II compliance, preparing for an audit, or simply trying to build better content practices going forward, a broader accessibility review can give you that picture — and a prioritized plan that covers your website, documents, and public-facing content together.
Book a free 30-minute intro call →
Or learn more about what a WCAG accessibility audit includes → before reaching out.
For the broader compliance context — including deadlines and what ADA Title II requires of public school districts — see What K–12 Districts Need to Know About the New Federal Digital Accessibility Rules →
Kalin Schoephoerster is a CPACC-certified instructional designer and accessibility consultant based in St. Paul, MN. KShep Creative partners with K–12 districts, higher education institutions, EdTech organizations, and small businesses to develop accessible eLearning, instructor-led training, curriculum, SOPs, and website accessibility audits aligned with WCAG 2.2 and ADA Title II requirements.