DocAccessible
Education solution

PDF accessibility for schools and higher education

A practical document accessibility workflow for K-12 districts, community colleges, and universities managing syllabi, forms, handbooks, reports, and public records.

Updated July 13, 2026. Reviewed by the DocAccessible team.

Start with documents tied to a student action

A district or university can own tens of thousands of files. Treating every file as equally urgent creates a backlog that never becomes a usable service. Start with documents a student, parent, faculty member, or applicant must read or complete now.

  • Admissions, enrollment, financial aid, and accommodation forms.
  • Syllabi, course packets, assignments, and program requirements.
  • Student handbooks, safety procedures, and campus policies.
  • Board packets, public reports, budgets, and meeting materials.
  • Orientation guides, maps, event information, and notices.

What the Title II rule changes for public education

The Department of Justice identifies public schools, community colleges, and public universities as examples of entities covered by the Title II web and mobile accessibility rule. The technical standard is WCAG 2.1 Level A and AA. The current compliance dates are April 26, 2027 for entities serving 50,000 or more people and April 26, 2028 for smaller entities and special district governments.

The rule includes exceptions, including a narrow one for certain preexisting conventional electronic documents. It generally does not protect an old file that is still being used to apply for, access, or participate in a public program. Read the DOJ Title II fact sheet and involve counsel when deciding whether a specific document is excepted. This page is operational guidance, not legal advice.

A workflow that does not depend on one accessibility specialist

  1. Inventory by owner and user action. Record the URL, department, format, last update, audience, and what someone must do with the document.
  2. Choose the output before remediation. Convert frequently updated reading content to HTML. Rebuild adaptable files as tagged PDFs. Route fixed forms and layout-critical records to a specialist.
  3. Fix the source when possible. Heading styles, table headers, meaningful link text, and image descriptions should live in the authoring file so the next export starts from a better place.
  4. Review the real task. Keyboard-test forms, listen to a representative page with a screen reader, and confirm that tables and multi-column content follow a meaningful sequence.
  5. Keep evidence. Store the source, final output, issue history, reviewer, publication URL, and next-review date.

Where Exchange fits

Many education teams already have a preferred remediation vendor. Exchangegives that vendor restricted access to a specific document case, keeps every returned revision, and lets an internal reviewer approve one version before delivery. It is a $19/month coordination plan; the vendor's remediation labor is not included.

Questions education teams ask

Does the ADA Title II web rule cover public schools and universities?

Yes. The DOJ fact sheet lists public schools, community colleges, and public universities as examples of public entities covered by Title II. The rule uses WCAG 2.1 Level A and AA as its technical standard, subject to its exceptions and limitations.

Do all old PDFs have to be remediated?

Not automatically. The rule has a limited exception for some preexisting conventional electronic documents, but the exception generally does not cover documents currently used to access or participate in a public service, program, or activity. Prioritize by current use and user impact, and obtain legal advice for edge cases.

Should a syllabus become HTML or remain a PDF?

Frequently updated reading content is usually easier to maintain as semantic HTML. Keep a PDF when the fixed page is operationally necessary, and remediate the source structure, reading order, tables, links, and images before publishing.

Useful next steps

Keep reading