# PDF remediation for school districts Canonical page: https://districtproof.io/services/pdf-remediation Give PDFs a usable structure, logical reading sequence, and clear meaning for assistive technology. The right starting point is a representative sample and the best available source file. ## What this service covers - Tags and heading hierarchy - Reading order and navigation - Alt text and meaningful links - Tables, language, and title ## Start with the task and the source A PDF can contain selectable text and still be hard to use. The order read by assistive technology may differ from the visual layout. Headings may be styled as bold text without structure. Tables may lack header relationships. A remediation scope checks the underlying information as well as the appearance. ## What needs human attention For a text document, begin with the title, language, headings, lists, and paragraphs. For a layout with columns or callout boxes, verify the reading sequence. Inspect the tags, then use the document as a reader would. A checker result alone cannot establish that descriptions or sequence make sense. ## Make the next update easier Ask for the source file before editing an exported PDF. Fixing a reusable source helps the next edition start in a better state. If no source exists, the exported file can be assessed for repair. Some documents may be better replaced with an accessible HTML page. ## Scope the work before setting the schedule Agree on the inputs, document versions, accepted formats, complexity, review method, and output before work starts. Flag any required publishing dates, confidential material, or dependencies on a website vendor. A representative sample helps avoid assumptions about the rest of the backlog. ## Pricing and next steps This service is part of [DistrictProof Docs](https://districtproof.io/solutions/docs). [Request a fixed quote](https://districtproof.io/pricing) after a sample review or begin with your public website inventory. For the regulatory context, read the [ADA Title II school district deadline guide](https://districtproof.io/resources/ada-title-ii-deadline-school-districts). Your district and counsel determine the applicable obligations and exceptions. ## A district PDF library contains several kinds of work A menu, a policy manual, and a board packet may all end in .pdf, but they should not enter the same production queue without a closer look. Menus can depend on visual grids. Policies need clear section navigation. Packets combine material from many authors, with inconsistent source quality. We separate these patterns when sizing the backlog so the work reflects what is inside the files. Repeated files matter too. A policy posted in several places may be one remediation task with several publication locations. Two documents with similar names may contain different revisions. Establishing that relationship before remediation helps your team avoid paying to repair an obsolete edition or posting the wrong returned file. Illustrative district scenario ### A current enrollment guide and an older policy manual The enrollment guide contains instructions families need now; the manual is longer and has many internal references. A useful plan gives each a separate priority, review method, and delivery milestone. The guide needs a clear sequence of actions. The manual needs navigation that lets readers reach the right policy without stepping through every page. This is an example of scoping, not a customer result. ## Deliverables that make the handoff usable The returned PDF is only part of the handoff. Your team also needs to know its source version, what changed, what was reviewed, and whether anything still needs a decision. The delivery manifest connects each returned file to its original name and intended publishing location. This matters when several departments use different names for the same document. Where the source is included in scope, the handoff should identify which editable version was updated and any export steps staff must preserve. We can also identify recurring authoring issues for template or training work. Those improvements belong in a separate, visible work item rather than disappearing into the page count. - Remediated file identified by a version name. - Source-file changes and export instructions where included. - A review record with methods, date, coverage, and open items. - A posting list that helps the district replace the right public links. ## What the district approves before posting Your content owner confirms that wording, dates, policy references, and substantive information remain correct. Accessibility work should preserve the document’s meaning. A reviewer should not guess what an unclear chart, damaged scan, or ambiguous instruction was intended to say. We bring those questions back to the district for a content decision. Once a file is accepted, publication verification checks the version actually served at its public location. A new export from an older source can undo structural work. Keep the accepted source and returned PDF together, and route later revisions through the same version process. ## Start with a representative sample Send a selection that reflects your actual mix: a current notice, a table-heavy document, a scan, a form, and an assembled packet where relevant. A sample containing only simple letters is unlikely to describe a complex archive. Tell us which files are used most, who owns them, and which meeting or program dates drive the schedule. For a website-wide starting point, request the [free PDF Backlog Report](https://districtproof.io/backlog-report). For files published every month, pair the initial project with [DistrictProof Care](https://districtproof.io/solutions/care). The goal is a defined first project and a practical way to prevent the same backlog from returning. ## Frequently asked questions ### What do you need to scope the work? A representative sample, the best available source files, the intended use, and your required publishing schedule. Website projects also need an agreed list of pages, templates, and tasks. ### How is this priced? We review complexity and scope before providing a fixed quote. Page counts alone do not describe the effort required for scans, tables, forms, or interactive components. ### Will an automated checker be enough? A checker can identify some issues, but a human review is needed for meaning, order, descriptions, and use. Evidence should identify both the tools and the manual coverage. ### What will we receive? Your agreement defines the returned files or issue log, review coverage, delivery schedule, and evidence record. Publication verification should reference the live version.