Somebody at your district finally counted the PDFs. Four thousand of them, going back nine years — student handbooks, registration packets, bell schedules, board minutes, meal applications, athletics physicals, the special-education procedural safeguards notice in English and again in Spanish. The website redesign is handled; the vendor put WCAG 2.1 AA in writing. Nobody has a plan for the four thousand, and the compliance date is no longer comfortably far away.
Before you scope that work, there is a good chance you are about to buy against the wrong standard. If your team went looking for guidance, you almost certainly searched for accessible school documents and Section 508 — that is simply how the phrase is used in K-12 — and landed on a checklist written for federal agencies. Section 508 is not your district’s rule. The checklist it produces is one WCAG version behind the rule you are actually measured against, and it will pass documents that a Title II review fails.
Why “Section 508” Is the Wrong Search
Section 508 (29 U.S.C. §794d) obligates federal agencies when they develop, procure, maintain, or use information and communication technology. A school district is a unit of local government. It is covered by Title II of the ADA, and — because essentially every district accepts federal financial assistance — by Section 504 of the same Rehabilitation Act. Neither of those is Section 508.
The bridge people reach for is the Assistive Technology Act, which requires states accepting AT Act funds to assure Section 508 compliance. The 2004 amendments narrowed that assurance so it applies to the State Assistive Technology Program itself — not to every state agency, and certainly not down to local school districts. Separately, many states have adopted 508-equivalent requirements by statute, executive order, or procurement policy, and some of those do reach districts. That is worth checking, but it is state law borrowing the standard, not Section 508 reaching you on its own.
Here is what the mix-up costs. The Revised 508 Standards incorporate WCAG 2.0 Level A and AA. The DOJ Title II rule requires WCAG 2.1 Level A and AA. WCAG 2.1 added success criteria that bear directly on documents — among them 1.4.10 Reflow, 1.4.11 Non-text Contrast, 1.4.12 Text Spacing, and 1.3.5 Identify Input Purpose, which is exactly the criterion a fillable enrollment form with name and address fields has to answer for. A vendor quoting against a 2.0-era checklist is not necessarily cutting corners. They are answering a different question than the one your compliance date asks.
Your Documents Are “Web Content” Under the Rule
Districts read the Title II rule as a website rule, and it is easy to see why — it is usually described as one. But the regulation defines conventional electronic documents as a specific list of file formats: portable document format (PDF), word processor file formats, presentation file formats, and spreadsheet file formats. If a document in one of those formats is part of your web content or mobile app, it is in scope on exactly the same terms as the page linking to it.
That sweeps up more than the district website. It reaches the learning management system, the parent portal, the board-agenda platform, and the documents your food-service or registration vendor posts on a page you link to. There is an exception for content posted by a third party — but it applies only to a genuinely unaffiliated third party, like a member of the public writing on an open community message board. A vendor publishing under a contract, license, or other arrangement with your district is not that. As the Department of Justice puts it, a public entity cannot contract away its responsibilities under the ADA.
The Five Exceptions — and the Two Districts Read Backwards
The rule provides five exceptions. Two of them are far narrower than the way they get quoted in planning meetings.
| Exception | What it actually covers | Where districts get it wrong |
|---|---|---|
| Archived web content | Content created before the compliance date, kept only for reference, research, or recordkeeping, not changed since it was archived, and clearly identified as archived. | All four conditions have to hold at once. A page of old minutes is not “archived” because it is old — it has to be frozen and labeled. |
| Preexisting conventional electronic documents | Documents already posted before your district’s compliance date — unless they are currently used to apply for, gain access to, or participate in the district’s services, programs, or activities. | That clause swallows the exception. The handbook, the registration packet, the meal application, the athletics forms, and the procedural safeguards notice are all still in use — which is most of what anyone actually opens. |
| Third-party content | Content posted by a truly unaffiliated third party who is not posting on the entity’s behalf. | It does not cover a vendor, contractor, or licensed platform posting under an arrangement with the district. |
| Individualized, password-protected documents | A conventional electronic document about a specific person, property, or account, secured behind a login. | It covers one student’s report card in the portal. It does not cover the blank template, the portal itself, or a district-wide notice pushed into every family’s account. |
| Preexisting social media posts | Posts published before the compliance date. | Everything posted from that date forward is in scope, including the flyer image with the schedule baked into it. |
And then the caveat that should decide how you plan. An exception removes a document from the technical standard in Subpart H. It does not remove your underlying Title II and Section 504 obligation to communicate effectively. If a parent who is blind asks for an excepted document in an accessible format, you still have to provide it — on request, under time pressure, one document at a time, by whoever happens to be available that week. That is the most expensive way in the world to do this work. The exceptions are a way to sequence the project, not a way to avoid it.
A Triage Your Team Can Run This Week
Sort by whether a document is used to apply for, access, or participate in something — not by how old it is or where it sits in the folder tree.
| Document | In scope? | When to do it |
|---|---|---|
| Blank templates staff reuse each year | Yes | First. An untagged template regenerates the problem every August. |
| Registration and enrollment packets (fillable) | Yes — used to apply | First. Fillable forms need labeled fields and a correct tab order, not just tags. |
| Meal benefit applications | Yes — used to apply | First. |
| Student and parent handbook | Yes — used to participate | First. |
| Special education procedural safeguards notice | Yes — and separately owed under the IDEA and Section 504 | First. |
| Current board agendas, minutes, and budgets | Yes | Second — and build it into the publishing workflow. |
| Board minutes from prior years | Likely excepted, if frozen and labeled as archived | Label them, then defer. |
| Calendars, newsletters, event flyers | Yes | Second. |
| Individual report cards and IEPs in the portal | Excepted — but still owed on request | Build a response path, not a bulk remediation project. |
The first row is the leverage. Most districts republish the same forty documents every year out of the same source files. Fix the sources and the backlog stops growing while you work through it.
Want a real number before you build the budget? Run one of your own district PDFs through our free checker. It tests tags, reading order, alt text, and the document language declaration right in your browser — nothing is uploaded — and tells you which of those is failing before you send anything out for quote.
The Part That Doubles the Work: Your Translated Documents
Title VI obligates districts to communicate with limited-English-proficient parents in a language they understand, so most districts already publish the handbook, the registration packet, and the safeguards notice in Spanish and often in two or three more languages. Accessibility and translation are almost always bought from different vendors, in that order — and the remediation does not survive the trip.
- Tags do not come along. A translated document rebuilt in InDesign or re-exported from Word starts untagged. The heading structure, reading order, and table markup you paid for exist only in the English file.
- The language declaration is the failure nobody checks. WCAG 3.1.1 requires a document’s default language to be programmatically determinable, and in PDF that means setting the
/Langentry. A Spanish handbook still declaringen-USgets read aloud by a screen reader in an English voice, applying English pronunciation rules to Spanish words. It is technically tagged and practically unusable. A bilingual side-by-side form needs 3.1.2 handled as well, marking the language of each passage. - Alt text is content. It has to be rewritten in the target language, not carried across. So do the labels on a fillable form, and any text baked into an image.
- Text expansion breaks the layout you just fixed. Spanish routinely runs longer than the English it came from. Cells overflow, frames reflow, columns re-order — and a reflowed layout invalidates the reading order the remediation established.
A district that publishes an accessible English handbook and an untagged Spanish one has not satisfied one obligation and missed the other. It has satisfied accessibility for the families least likely to need translation, and missed it for the families who need both at once.
The fix is a sequencing decision, and either order works so long as you make it deliberately: remediate the source, translate, then re-remediate and re-test the target — or finalize the translated layout first and remediate once, in the target language. What is not defensible is doing the work once in English and assuming it carried.
The Villain: Remediation Priced by the Page
Procurement’s instinct is to put a document backlog out for bid by the page and take the lowest number. What that reliably buys is an automated tagging pass and a checker report showing zero errors — which is not the same thing as an accessible document.
Auto-tagging guesses heading levels from font size, reads multi-column layouts in the wrong order, marks layout tables as data tables, and gives images either an empty alternative or the file name. An automated checker cannot evaluate whether alt text is meaningful, whether reading order matches the visual order a sighted reader follows, or whether a heading outline is logical. Those three judgments are most of the job, they require a person, and they are the first thing cut when the unit of sale is a page. Accessibility overlays, whatever they promise for web pages, do nothing at all for a PDF.
Two questions separate a real vendor from a wizard-and-invoice shop. Who performs the manual reading-order review, and what are their credentials? And: who screen-reader tests the Spanish file, and do they speak Spanish? A remediation house with no linguists cannot answer the second one — and that is the file your LEP families depend on.
A Three-Step Plan
- Inventory and triage, worst-first. Crawl the site, the LMS, and the portal for those four file formats. Rank by the “used to apply for, gain access to, or participate in” test. Freeze and clearly label anything that genuinely qualifies as archived — that is real scope reduction you can take unilaterally, today.
- Fix the templates before the backlog. Every recurring document comes from a source file in Word, InDesign, or your student information system. Remediate the source so next year’s version ships accessible, then work backward through the archive. Our step-by-step PDF remediation guide covers the six failures that account for most of what reviewers find.
- Scope remediation and translation as one workflow. Put both in the same statement of work. Require the language declaration to be set per file, require alt text authored in each published language, and require a screen-reader test in every language you publish — performed by someone who speaks it.
Do this and the compliance date turns into a project plan instead of a threat. A parent using a screen reader can read the handbook. A parent using a screen reader in Spanish can read the same handbook. And when someone asks what your district did, the answer is an inventory, a priority order, and a dated record — not a scramble.
Why Districts Work With Taika
Language Access Hub, powered by Taika Translations, is a veteran-owned (VOSB), SAM-registered language access provider on GSA Schedule and NASPO ValuePoint — so most districts can buy without running a full solicitation. We handle document remediation and certified translation under one roof, which means the Spanish version of your handbook is tagged, declared, and screen-reader tested by people who actually read it. See our ADA and Section 508 compliance services and what we build for school districts.