Choose the format around the reader’s job.

A short service instruction, changing deadline or eligibility explanation usually works well as a web page. A spreadsheet intended for analysis has a different purpose. An approved meeting record may need to remain available as an issued document. Start by naming the job, not by exporting everything from the office application used to draft it.

The GOV.UK accessible-document guidance (opens in a new tab) favors HTML where possible and describes document structure and checks. This is UK publishing guidance. It informs the design decision here without establishing the obligations of a U.S. municipality.

HTML is not accessible merely because it is HTML, and a PDF is not inaccessible merely because it is a PDF. Both need appropriate structure, meaningful content and testing. The decision should account for the complete resident journey, including any required download.

Use this format decision table.

Reader needUseful starting choiceWhat to verify
Read current service instructions on a phoneHTML service pageHeadings, eligibility, start route and a responsible fact owner.
Read a long narrative reportStructured HTML, with a document if an issued edition is neededNavigation, tables, figures and equivalent version context.
Use data in calculationsAccessible spreadsheet or suitable machine-readable data plus HTML explanationHeaders, units, field definitions and download instructions.
Access a signed or approved recordRetain the authorized record and provide an accessible routeRecord status, publication authority and applicable requirements.
Fill in a transactionAccessible online form when feasible, with an approved assisted routeLabels, instructions, errors and successful receipt.
Consult a historic scanned itemEvaluate remediation and access under agency policyReadable text, provenance, permitted changes and assistance route.

On a small screen, scroll the table sideways to see every column.

If a record must remain in its issued form, ask the records owner what can be changed and how an accessible version is identified. Do not silently replace an official document with a summary or assume an archive label settles an accessibility question.

Worked example: a program instruction sheet.

Fictional planning example. Cedar Bay has a two-page PDF explaining how to register for a community workshop. The public task is to understand eligibility, dates, required information and how to register. Those instructions become a service page with the approved registration link and support route.

The PDF is retained only if there is a defined print or issued-edition need. Its link identifies the title, format, relevant edition and size where known. A visible note explains whether it is the official issued document or a print copy of current instructions. The owner records which page and document share facts.

When registration closes, the web page changes its available action and explains the next step. The document is handled according to agency decisions about records and continued access. Staff do not leave an old active-registration link as the only route from a downloadable file.

Use the service-page pattern for the HTML content and the audit workbook to record the file, owner and destination.

Check the document as a document.

  • Create meaningful headings in the source file and verify the exported structure and reading order.
  • Give tables appropriate headers and review complex tables rather than relying on visual layout.
  • Provide alternatives for meaningful images and explanations for information carried only by color.
  • Check document language, title, link purpose and keyboard operation where interactive controls exist.
  • For a scan, inspect text recognition for accuracy. Searchable text alone does not establish accessibility.
  • Test the final published file, including forms, figures and navigation, using an agreed evaluation method.

An automated checker helps locate some issues; it does not verify that every instruction, figure or reading sequence is usable. Assign remediation and retesting to a person with the appropriate skills. A vendor’s statement about a template does not verify all documents created from it.

A reviewer uses a keyboard and ordinary headset to check a digital document, with a neatly printed source page nearby.
Reviewing document structure and access.

Prevent the HTML and document from disagreeing.

Store a relationship between the page, document edition and source revision. Decide which owner authorizes a factual change and whether publication of both versions must be coordinated. A date printed in a footer should not be updated unless it describes an actual publication or review event.

When a document is superseded, preserve the approved record history and make the current route clear. Check links from search results, meeting records and related services. Use the migration checklist when URLs change and the correction workflow when the information was wrong.

For U.S. state and local entities, consult the current DOJ Title II implementation guidance (opens in a new tab) with the responsible accessibility and legal reviewers. Scope and exceptions need agency-specific assessment. This format guide is a planning aid, not an accessibility certification or a determination that a document qualifies for an exception.

A tablet page and a printed edition beside one source folder, an editor checks a matching detail with a pencil.
Keeping web and document versions aligned.