Turn frequently used documents into web pages

What this service covers

• Content and format assessment
• Semantic headings, lists, and tables
• Mobile reading and navigation
• Link replacement and ownership

Start with the task and the source

Not every document needs to remain a PDF. Frequently updated information such as meal details, service instructions, or office guidance may work better as a web page. A page can be easier to read on a phone and simpler for staff to update in a CMS.

What needs human attention

Conversion requires more than copying text. Preserve heading hierarchy, list relationships, table headers, link purpose, and meaningful images. Check that information originally conveyed through layout or color still has a clear equivalent in the new format.

Make the next update easier

Plan the publishing change. Identify inbound links, decide whether an older PDF should remain available, and assign an owner to the new page. Review the live version after publishing. Archive and retention decisions remain with the district and its counsel.

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. Request a fixed quote after a sample review or begin with your public website inventory.

For the regulatory context, read the ADA Title II school district deadline guide. Your district and counsel determine the applicable obligations and exceptions.

Choose content that benefits from being a web page

Start with information families revisit or staff update frequently: program instructions, office guidance, meal information, contact lists, and service explanations. A page can make it easier to navigate by headings, follow links, and read without downloading a document. The choice still depends on records needs and how the content will be maintained.

A signed record, a fixed publication, or a complex reference document may need to remain available in its original format. Some information can have an HTML reading version alongside an appropriate record copy. The district decides what must be retained, how versions relate, and which copy is authoritative.

Preserve information while changing the format

Map the original sections before moving text into a CMS. Identify headings, lists, tables, footnotes, charts, and references. Content conveyed through layout may need an explicit explanation in the new page. Preserve the relationships that help a reader understand which instruction or note belongs to which item.

A conversion also provides an opportunity to simplify the reading path. Break dense instructions into meaningful sections, use descriptive link text, and keep the main action close to the information needed to take it. Content changes that affect policy or meaning go back to the district owner for approval.

Work within your CMS and vendor responsibilities

The page template, editor, and publishing permissions affect what can be implemented directly. Agree on who creates the page, who fixes shared template issues, and who checks the published result. If an embedded tool is part of the task, include its owner and accessibility follow-up in the plan.

Avoid moving inaccessible formatting into a page builder unchanged. Headings should be real headings, tables should reflect data relationships, and controls should use appropriate elements and labels. The surrounding site navigation and page template may need review beyond the converted content area.

Manage links, records, and future ownership

List the places that link to the original PDF. Decide whether each should point to the web page, the retained record copy, or both. Where redirects are possible and appropriate, define them with the website team. Do not remove records or change retention arrangements as an incidental part of accessibility work.

The handoff identifies the new page URL, approved content version, page owner, and review outcome. For the next update, staff should know which source to change. Explore DistrictProof Web for the surrounding website experience and Care for a recurring publishing routine.

Frequently asked questions