- Accessibility Remediation
- October 27, 2026
PDF Remediation: 8 Proven Steps to Make Every Document Accessible
PDF remediation is the work of taking an existing PDF and making it usable for everyone, including people who rely on screen readers, keyboards, magnifiers or voice control. Most PDFs were never built with those users in mind. They look fine on screen, but underneath there is no structure telling assistive technology what is a heading, what belongs in a table, or which order the content should be read in.
The good news is that the process is predictable once you know the steps. At D2i Technology, our accessibility team remediates reports, forms, policies and course materials for organizations in the USA and India, and we follow the same core workflow on almost every file. This guide walks through those eight steps, the tools involved, and the mistakes that cause “fixed” documents to fail later.
What PDF Remediation Means in Practice
A PDF has two layers. The visual layer is what you see. The structural layer, built from tags, is what a screen reader uses. PDF remediation is mostly about that second layer: adding or correcting tags, setting a logical reading order, describing images, and making tables, forms and links understandable without sight or a mouse.
The usual goal is to meet WCAG 2.1 or 2.2 Level AA, and often PDF/UA (ISO 14289), the dedicated standard for accessible PDFs. The W3C keeps a useful list of PDF techniques for WCAG that maps common fixes to specific success criteria.
Why does this matter beyond compliance? Think of a job applicant who uses a screen reader opening your application form, or a patient trying to read their discharge instructions. If the PDF is just an untagged picture of text, they hear nothing useful. Remediation is what turns that document back into information.
PDF Remediation in 8 Steps
Step 1: Take Inventory and Decide What Needs Fixing
Before opening a single file, list the PDFs you publish and decide what to do with each one. Some are outdated and can be removed. Some would work better as a normal web page. Others are still in active use and need remediation.
Prioritize your PDF remediation work by impact. Forms people must complete, documents tied to legal or regulatory obligations, and the most-downloaded files should go first. A small business with 50 PDFs might finish in a few weeks. A university or government agency with thousands usually needs a phased plan.
Step 2: Go Back to the Source File if You Can
This step saves more PDF remediation time than any other. If the original Word, PowerPoint or InDesign file still exists, fix it there first. Use real heading styles instead of bold text, built-in lists, proper table header rows and alt text on images. Then export a fresh, tagged PDF.
A well-prepared Word document can produce a PDF that needs only light touch-up work. Starting from an untagged PDF with no source file is far slower, because every structure has to be rebuilt by hand.
Step 3: Run an Automated Check for a Baseline
Next, run the file through an automated checker. Adobe Acrobat Pro has a built-in accessibility checker, and the free PDF Accessibility Checker (PAC) tests against PDF/UA in more depth.
These reports give you a starting list: missing tags, missing title, missing language, images without alt text, untagged annotations. Treat the report as a map for your PDF remediation, not a verdict. Automated checks can confirm that alt text exists, but not whether it makes sense. They can confirm a table is tagged, but not whether the headers are linked correctly.
Step 4: Set the Document Properties
This is the quickest part of PDF remediation, and it is often missed. In the document properties, add a meaningful title and set the PDF to display that title rather than the file name. Set the primary language so screen readers use the right pronunciation. If parts of the document are in another language, tag those passages with their own language.
A screen reader user who opens “Final_v3_REVISED.pdf” learns nothing. One who hears “2026 Employee Benefits Guide” knows immediately where they are.
Step 5: Fix the Tag Structure and Reading Order
This is the heart of PDF remediation. Open the tags tree and make sure every piece of content has the right tag: headings (H1 to H6 in a logical order), paragraphs, lists and list items, figures, tables and links.
Then check the reading order. Multi-column layouts, sidebars, pull quotes and footnotes regularly end up in the wrong sequence. A common example is a newsletter where the screen reader jumps from the first column into a sidebar halfway through a sentence. Rearrange the tags so content is read in the same order a sighted reader would follow.
Finally, mark decorative items such as background shapes, page borders, repeated headers and footers as artifacts so they are skipped. Removing that noise makes a big difference to the listening experience.
Step 6: Write Useful Alternative Text
Every meaningful image needs alt text that explains its purpose in context. A photo of a team at a conference might need only a short description. A chart needs much more care: describe the main trend or conclusion, not just “bar chart”. If the data is important, include it in nearby text or a table.
For example, instead of “Revenue chart”, write something like “Revenue grew each quarter in 2026, from 2.1 million in Q1 to 3.4 million in Q4.” That gives a screen reader user the same takeaway as someone looking at the chart.
Step 7: Remediate Tables, Forms and Links
Tables need header cells marked as headers, with scope set for rows or columns. Complex tables with merged cells or multiple header rows may need explicit header IDs. Without this, a screen reader user hears a stream of numbers with no idea what they refer to.
Forms need every field labeled with a clear tooltip, a logical tab order, grouped radio buttons and checkboxes, and instructions that can be reached by keyboard. Test the form end to end: can someone fill it in and submit or save it without a mouse?
Links should make sense out of context. “Click here” repeated ten times is useless when someone pulls up a list of links. “Download the enrollment form” tells them exactly where it goes.
Also check color contrast for text and important graphics. Our free Color Contrast Analyzer makes that quick.
Step 8: Test Manually and Document the Results
Testing is the step that separates real PDF remediation from cosmetic fixes. Once the fixes are in, rerun the automated checks, then test like a real user. Open the file with a screen reader such as NVDA or JAWS. Navigate by headings. Move through tables cell by cell. Tab through every form field. Zoom to 200% and check that nothing important is lost.
Then record what you tested and the result. A short conformance note for each file, or each batch, is invaluable when a customer, auditor or procurement team asks for proof. These records also feed directly into VPAT and ACR preparation.
Common PDF Remediation Mistakes to Avoid
We see the same problems again and again when reviewing documents that were “already fixed”:
- Relying on auto-tagging alone. Acrobat’s autotag feature is a starting point, not a finish line. It often guesses headings and tables wrong.
- Passing the checker but failing users. A clean automated report does not mean the reading order, alt text or form flow actually work.
- Using file names as alt text. “IMG_4021.jpg” helps nobody.
- Ignoring scanned pages. Scans need OCR and careful proofreading before any tagging can begin.
- Fixing the PDF but not the template. If the source template stays inaccessible, every new document repeats the same problems.
Our article on manual vs automated accessibility audits explains why human testing remains essential.
Which Laws and Standards Apply to PDF Remediation?
PDFs are covered by the same accessibility rules as websites. In the USA, that includes Section 508 for federal agencies and their vendors, and the ADA, including the Department of Justice’s 2024 Title II rule for state and local governments, which points to WCAG 2.1 AA. In Europe, the European Accessibility Act covers many digital products and services. In India, regulators such as SEBI have set accessibility expectations for regulated entities.
The common thread is WCAG compliance. If your documents meet WCAG 2.1 or 2.2 AA, you are in a strong position under most frameworks.
Should You Handle PDF Remediation In-House?
For a small number of simple, text-based documents, an in-house approach can work well. You will need Acrobat Pro, a screen reader for testing, and time for someone to learn the process properly. The first few files will be slow; that is normal.
Professional PDF remediation makes more sense when you have a large backlog, complex tables or forms, scanned documents, a compliance deadline, or a complaint already on the table. Many organizations choose a mix: specialists clear the backlog while internal teams learn to create accessible documents from the start.
Make Your PDFs Accessible With D2i Technology
Good PDF remediation is careful, methodical work, and it pays off every time someone opens your documents and can actually use them. If you would rather not take it on alone, D2i Technology can help at any stage, from a quick audit of your most important files to full remediation of a document library.
Our accessibility remediation services cover PDFs, websites, apps and eLearning content, and every file is tested manually by our accessibility testing team before it is returned. Send us a few sample documents and we will show you exactly what needs fixing.
Frequently Asked Questions
Need Help Making Your PDFs Accessible?
D2i Technology remediates PDFs to WCAG 2.2 AA and PDF/UA, with manual screen reader testing on every file. Share a few sample documents and we will show you exactly what needs fixing.