Creating an Accessible PDF

The PDF for this project wasn’t just exported and uploaded. It was built the same way the rest of this site was built — with structure, clarity, and accessibility in mind from the start. PDFs can easily become barriers when they’re just images or untagged text, so the goal here was to create a document that works for everyone, including people who rely on screen readers, keyboard navigation, or magnification tools. This page explains the choices made during the process and the tools used to make sure the final PDF is actually usable.

View the Accessible PDF

You can open the completed accessible PDF created for this project using the link below:

View the Anime‑Style Accessible PDF

What Makes a PDF Accessible

An accessible PDF needs more than readable text. It needs a structure that assistive technology can understand. For this project, the PDF includes:

• Tagged content so headings, paragraphs, and lists are recognized correctly
• A logical reading order that matches the visual layout
• Alt text for images so screen readers can describe visuals
• Real, selectable text instead of flattened or scanned pages
• Clear, descriptive link text
• Consistent heading levels to support navigation
• Document metadata like title and language

These elements make the PDF predictable and easier to navigate, especially for users who depend on assistive tools to move through a document.

Tools Used to Check Accessibility

Several tools were used to make sure the PDF met accessibility standards and didn’t hide any issues.

Adobe Acrobat Accessibility Checker

This was the main tool for scanning the PDF. It flagged missing tags, reading‑order problems, unlabeled images, and anything else that could confuse a screen reader. It also provided suggestions that helped refine the structure.

WAVE (for linked content)

While WAVE doesn’t scan PDFs directly, it was used to check any web content linked inside the PDF. This kept the experience consistent for users moving between the document and the site.

Read Aloud and Screen Reader Testing

The PDF was tested with built‑in screen reading tools to make sure headings were announced correctly, alt text appeared where it should, and the reading order matched the intended flow. This step helped confirm that the document wasn’t just technically accessible, but actually usable.

Steps Taken to Ensure Accessibility

The PDF was created with accessibility in mind from the beginning, not added at the end. These steps were followed during the process:

• The document was built using a tool that supports tagging and structure
• Headings were applied using proper styles instead of manual formatting
• Images were given meaningful alt text
• Lists were created using real list formatting
• Tables were tagged with headers and reading order
• The document language was set to English
• The final file was tested and corrected using Acrobat’s accessibility tools

Each step helped make the PDF more predictable and easier for assistive technologies to interpret.

Why Accessible PDFs Matter

PDFs show up everywhere — in classes, workplaces, and public websites — and when they aren’t accessible, they can block entire groups of people from important information. Making PDFs accessible isn’t just a technical requirement; it’s a way to make sure everyone can read, understand, and interact with the content. It also supports legal and ethical standards for digital accessibility, which is becoming more important every year.