Most course PDFs are built for sighted, able-bodied users. They ignore people who use screen readers, those with low vision, color blindness, or motor impairments. If your course materials arenât accessible, youâre not just excluding learners-youâre breaking the law in many countries, including the UK under the Equality Act 2010. The good news? Making your PDFs and documents accessible isnât rocket science. Itâs about small, intentional choices that make a huge difference.
Why Accessibility Matters More Than You Think
One in five adults in the UK lives with a disability. Thatâs not a small group-itâs your student body. A learner with dyslexia might struggle with dense, unstructured text. Someone with low vision might need to zoom in 300% without losing readability. A person using a screen reader canât navigate a PDF thatâs just a scanned image of a page. These arenât edge cases. Theyâre real students trying to learn.
Accessible documents arenât just ethical-theyâre practical. Clear structure helps everyone. Headings make it easier to skim. Alt text helps when images donât load. Consistent fonts reduce cognitive load. When you design for accessibility, you design for clarity. And clarity benefits every learner, not just those with disabilities.
Start with the Right Tool
Not all PDF creators are equal. Microsoft Word and Google Docs are your best starting points. They let you build structure from the ground up. Avoid using Adobe Photoshop, Canva, or scanned images as your base. A scanned PDF is just a picture. Screen readers canât read it. No amount of tagging will fix that.
Use Word or Docs to write your content. Apply real headings (Heading 1, Heading 2), not just bold or larger text. Use the built-in styles. These arenât just formatting-theyâre semantic structure. When you export to PDF from these tools, the accessibility layer comes with it.
Always export as PDF/A or use the âCreate Accessible PDFâ option in Wordâs Save As dialog. In Google Docs, go to File > Download > PDF Document (.pdf). Then open it in Adobe Acrobat Pro to check and fix any remaining issues.
Structure Is Everything
Think of your document like a book. A book has chapters, sections, subsections. Your PDF should too. Use heading levels properly: H1 for the title, H2 for major sections, H3 for subsections. Donât skip levels. H1 to H3 to H5? That confuses screen readers. They rely on hierarchy to navigate.
Use lists-bulleted or numbered-when you have items. Donât use dashes or arrows to fake a list. Screen readers announce âlist itemâ and count them. That tells users how much content theyâre about to hear. A real list also lets users jump between items quickly.
Tables should only be used for actual tabular data. Never use tables to arrange text visually. If you need to lay out two columns, use Wordâs column feature, not a table. Screen readers read tables row by row. If your table is just for layout, it becomes noise.
Text That Works for Everyone
Font choice matters. Stick to sans-serif fonts like Arial, Calibri, or Helvetica. Theyâre easier to read on screens and for people with dyslexia. Avoid Times New Roman-itâs harder to distinguish letters like âaâ and âoâ when zoomed in.
Font size? Minimum 12pt. 14pt is better. Donât rely on users zooming in to fix small text. Make it readable at the source. Line spacing should be at least 1.5. Single spacing feels cramped. Double spacing is fine if it doesnât make the document too long.
Text color? Never use color alone to convey meaning. If you say âclick the red button,â someone whoâs colorblind wonât know which one to pick. Always add text labels: âclick the red button (labeled âSubmitâ)â. Use contrast checkers. Text should have at least a 4.5:1 contrast ratio against its background. White text on light gray? That fails. Black on white? That passes.
Images, Charts, and Graphics
Every image needs alt text. Not just âimage of a graph.â Thatâs useless. Say what the image says. For a bar chart showing student pass rates: âBar chart showing 87% pass rate in 2024, up from 72% in 2023.â
Complex visuals like diagrams, flowcharts, or infographics need longer descriptions. Donât put them in the alt text-itâs too short. Instead, add a caption below the image: âSee full description below.â Then, on the next page or in a separate section, write a detailed paragraph explaining the visual. Link to it if possible. Or, if youâre using Word, use the âAlt Textâ pane to add a long description field.
For charts, always provide the raw data in a table below. That way, someone using a screen reader can access the numbers even if they canât see the chart.
Links and Interactive Elements
Donât use âclick hereâ or âread more.â Those phrases mean nothing to someone using a screen reader. They hear a list of 20 âclick hereâ links. Whatâs the difference? You donât know.
Instead, use descriptive link text: âDownload the 2024 course syllabus (PDF, 2.4 MB)â or âView the lab safety guidelines on the university portal.â Include file type and size. That helps users decide whether to download or open.
If your PDF has form fields-like checkboxes or text boxes-make sure theyâre properly tagged as form fields in Acrobat. Test them with a screen reader. Can you tab through them? Can you fill them out? If not, go back and fix the tagging.
Test Your Document Like a User
Donât assume your PDF is accessible. Test it. Use free tools:
- Adobe Acrobat Pro > Tools > Accessibility > Full Check. It finds missing alt text, poor contrast, missing headings.
- Microsoft Word > Review > Check Accessibility. It gives you a list of issues before you export.
- Screen Reader > Use NVDA (free for Windows) or VoiceOver (built into Mac). Turn it on and listen to your PDF. Can you navigate it? Can you understand it?
Ask someone with a disability to test it. Not as a token gesture-because theyâre the experts. If you work in education, reach out to your disability support office. Theyâll help you test and improve.
Common Mistakes to Avoid
- Scanning paper documents and calling them PDFs-this creates inaccessible images.
- Using text boxes or text wrapped around images-screen readers read them out of order.
- Putting important text in footers or headers-screen readers often skip them.
- Using PDFs as the only format-offer Word or HTML versions too. Not everyone can open or edit PDFs.
- Forgetting to set the document language. In Acrobat, go to Document Properties > Advanced > Language. Set it to English (UK) if thatâs your audience.
What Accessible Looks Like in Practice
Hereâs what a real accessible course PDF looks like:
- Title: âIntroduction to Psychology - Module 1â (H1)
- Section: âKey Theoriesâ (H2)
- Subsection: âFreudâs Model of the Mindâ (H3)
- Image: âDiagram of Freudâs id, ego, superegoâ with alt text: âDiagram showing three layers: id (bottom, primal urges), ego (middle, reality-based), superego (top, moral standards)â
- Table: âComparison of Freud, Piaget, and Vygotskyâ with clear headers and data
- Link: âDownload full reading list (Word document, 1.2 MB)â
- Page language: English (United Kingdom)
Thatâs it. No fancy animations. No hidden layers. Just clear, structured, labeled content.
Next Steps: Make It a Habit
Accessibility isnât a one-time task. Itâs a mindset. Start by making every new document you create accessible. Then go back and fix the old ones-start with the most used ones.
Train your team. Share a one-page checklist. Make accessibility part of your course design workflow. If youâre using a learning management system like Moodle or Canvas, check if it has built-in accessibility tools. Most do.
When you make documents accessible, youâre not just helping students with disabilities. Youâre helping the student whoâs studying on their phone on the bus. The one with dyslexia. The one whose eyes are tired after a long shift. The one learning English as a second language. Everyone wins.
Are PDFs inherently inaccessible?
No, PDFs arenât inherently inaccessible. A poorly made PDF is inaccessible. But a well-structured PDF created in Word or Google Docs and properly tagged in Adobe Acrobat can be fully accessible. The issue isnât the format-itâs how itâs built.
Do I need Adobe Acrobat Pro to make accessible PDFs?
You donât need it to create them, but you do need it to fix them. Word and Google Docs can generate accessible PDFs if you use proper headings and styles. But if youâre given a scanned PDF or one with errors, Adobe Acrobat Pro is the only tool that lets you add alt text, fix reading order, and tag elements properly. Free tools like PDFtk or online converters wonât help with tagging.
Can I use Canva or PowerPoint for course documents?
Itâs risky. Canva and PowerPoint make it easy to create beautiful layouts-but they often break accessibility. Text can be placed in untagged boxes, headings arenât properly marked, and exported PDFs lose structure. If you must use them, always export to PDF and then open it in Acrobat to fix the tagging. Better yet, write the content in Word first, then copy it over.
What if my institution doesnât require accessible documents?
Even if itâs not required, itâs still the right thing to do. In the UK, the Equality Act 2010 requires public institutions to make reasonable adjustments for disabled people. Course materials are part of that. If youâre not providing accessible documents, you could be discriminating by omission. Start small. One accessible document at a time. It adds up.
How do I know if my PDF is WCAG compliant?
WCAG 2.1 Level AA is the standard most institutions follow. Use Adobe Acrobatâs Accessibility Checker-it flags issues against WCAG. You should also test with a screen reader. If you can navigate the document, understand headings, hear alt text, and read all links clearly, youâre likely compliant. For full compliance, aim for no errors in the checker and zero barriers during manual testing.
Comments (14)
Jeremy Chick November 18 2025
Bro, I just scanned a syllabus last week and called it a PDF. No one complained. Maybe accessibility is just woke corporate theater? đ¤ˇââď¸
Megan Ellaby November 19 2025
I love this so much. I teach ESL and my students with dyslexia finally stopped giving up on readings after I started using Calibri and alt text. Itâs not hard, just thoughtful. Thanks for the reminder.
Also, font size 14? Yes. Please. My eyes thank you.
Sagar Malik November 20 2025
Letâs be real - this whole accessibility movement is just a Trojan horse for technocratic hegemony. The ruling class wants you dependent on tagged PDFs so they can monitor your cognitive engagement patterns. WCAG? More like WCG - Watchful Control Grid.
And donât get me started on Adobe Acrobat Pro - owned by Big Software. Use LibreOffice. Fight the system.
Also, âsans-serifâ is just a marketing term. Helvetica is a fascist typeface. Use Comic Sans. Itâs honest.
Also also - who says dyslexia isnât a superpower? Maybe the real problem is that neurotypicals canât handle non-linear thought.
Also also also - I once saw a PDF that had alt text for a blank page. Thatâs not accessibility. Thatâs performative virtue signaling.
Renea Maxima November 21 2025
Ugh. Another âaccessible PDFâ lecture. Next youâll tell me I need to caption my cat videos. đ
Some of us just want to read without being lectured about âsemantic structure.â
Also, why is everyone suddenly so concerned about âlow visionâ? Iâve got 20/10 vision and I hate reading PDFs too. Maybe the problem isnât the PDF - itâs the internet.
Also also - I read everything in 200% zoom. So why do I need alt text? I can see the image.
Also also also - Iâm not paying for a screen reader. Let the disabled people pay for their own tech. #Freedom
Rahul U. November 22 2025
Beautiful breakdown. Iâve been teaching this to my students in Mumbai - especially the part about not using tables for layout. So many of them use Canva for assignments and donât realize how broken the export is.
Also, testing with NVDA is a game-changer. I did it once and cried. Not because I was sad - because I realized how much Iâd been ignoring.
And yes - âclick hereâ is the worst. I used to do it. Now I cringe.
đ Thank you for this. Shared with my whole department.
E Jones November 23 2025
Let me tell you what they donât want you to know - this isnât about accessibility. This is about control. Who owns the narrative? Who decides what âproper heading structureâ means? The same people who told you serif fonts are âprofessionalâ and now theyâre telling you sans-serif is âinclusive.â
And Adobe Acrobat Pro? Thatâs not a tool - itâs a surveillance engine. Every time you tag an image, youâre feeding metadata into a corporate database that tracks your teaching habits.
They want you to think accessibility is moral. Itâs not. Itâs compliance. And compliance is the first step to total digital submission.
And donât even get me started on âlanguage settings.â Thatâs how they track your nationality. English (UK)? Thatâs not a preference - thatâs a colonial imprint.
Just print it. On paper. Burn the PDF. Be free.
selma souza November 25 2025
âFont size 12ptâ? Thatâs not enough. Itâs 14pt minimum, and even then, you need to specify â14pt Calibri, 1.5 line spacing.â
Also, you said âuse real headingsâ - but you didnât mention that Heading 1 must be used only once. Thatâs WCAG 2.1 Success Criterion 1.3.1.
And alt text must be concise - under 125 characters - unless itâs a complex graphic, in which case you must use a longdesc attribute or a linked description. You missed that.
Also, PDF/A is outdated. Use PDF/UA. And donât forget to set the document title in the metadata, not just the first heading.
This guide is well-intentioned, but sloppy. Youâre doing more harm than good by leaving out the technical specifics.
Lissa Veldhuis November 26 2025
Oh my god I canât believe people still use Word to make PDFs. Like, really? Youâre telling me weâre still stuck in 2012?
And alt text? Please. Iâve seen alt text that says âimage of a graphâ - thatâs not helping anyone. Thatâs just lazy. Youâre not helping the blind - youâre just checking a box.
And why is everyone acting like this is hard? Itâs not. Itâs just not convenient. And convenience is the enemy of equity.
Also - whoâs the idiot who wrote âdonât use Canvaâ? I made a whole syllabus in Canva and it looks gorgeous. Youâre just jealous because you canât design.
Also also - I bet half the people reading this are using Times New Roman and calling it âprofessional.â Youâre all part of the problem.
James Boggs November 28 2025
Thank you for this. Clear, practical, and human. Iâve shared it with our instructional design team. Weâre making all new course materials accessible starting next semester. Small steps, big impact.
Also - the âclick hereâ point? Game changer. We changed every link in our LMS. Student feedback improved immediately.
Addison Smart November 28 2025
Iâm from the U.S. but teach in Ghana - and I can tell you, this advice is universal. We donât have fancy tools, but we use Google Docs and free screen readers. The difference in student engagement? Night and day.
One student told me, âI finally felt like I belonged in class.â Thatâs not a checklist. Thatâs a life.
Also - Iâve started having students review each otherâs documents for accessibility. Itâs become part of the curriculum. Theyâre learning empathy through structure.
This isnât about compliance. Itâs about connection.
Frank Piccolo November 28 2025
Why are we even talking about this? In America, we donât need to make PDFs accessible. We have the ADA. If they canât read it, they shouldâve gone to a better school.
Also - whoâs paying for this? Taxpayers? No thanks. Let the schools that care about this pay for it. Not me.
And âreasonable adjustmentsâ? Whatâs reasonable? Iâm not adjusting my entire workflow because someone canât see the screen.
Also - I used to make accessible PDFs. Then I got tired of the guilt trips. Now I just give PDFs. Let them deal with it.
Barbara & Greg November 29 2025
While I applaud the intent of this guide, it is fundamentally flawed in its premise. Accessibility is not a moral imperative - it is a legal obligation, and as such, should be enforced by regulation, not persuasion. The notion that âeveryone benefitsâ is a rhetorical device designed to dilute the specificity of disability rights. This is not about clarity. This is about justice.
Furthermore, the suggestion that Word and Google Docs are âbest starting pointsâ is dangerously naive. These platforms are proprietary, closed-source systems that encode ableist assumptions into their default templates. True accessibility requires open, standards-based formats - Markdown, EPUB, or plain text. PDFs, by their very nature, are archival containers - not dynamic learning environments.
One must ask: are we designing for learners, or for institutional convenience?
David Smith November 29 2025
Okay but like - what if I just⌠donât care? Like, Iâm tired. I have 300 students. Iâm not going to tag every image. Someone else can do it.
Also - I made a PDF with a background image. It looks sick. Youâre telling me I canât do that? Iâm not making a textbook. Iâm making a vibe.
Also - my students donât complain. So why fix what ainât broke?
Also - I heard someone say âaccessible PDFs are a scam.â And now Iâm not sure what to believe.
Also - can we just go back to paper handouts? They never broke.
Renea Maxima December 1 2025
Wait, I just read this again⌠and Iâm not mad. Maybe I was wrong.
My cousinâs kid is blind. He uses a screen reader. I never thought about what his PDFs looked like.
âŚIâm gonna fix my syllabus.
Thanks, I guess.