Guide
Should meeting agendas be a web page or a PDF?
Both, written once. Post the agenda as a web page where your website allows it, and link a tagged PDF from that page for printing and the record. Where your system only takes files, post the tagged PDF.
- Published
- Last reviewed
Why the page comes first
In 2018 the head of GOV.UK set out the case on the Government Digital Service blog: “The default should be to create all content in HTML.” His reasons fit an agenda too:
- “Compared with HTML content, information published in a PDF is harder to find, use and maintain.”
- “PDFs are not designed to be flexible in their layout”, so they don’t adapt to a phone screen the way a page does.
- “…unless created with sufficient care PDFs can often be bad for accessibility”.
It didn’t ban PDFs: “If you can’t avoid publishing a PDF, ideally it should be in addition to an HTML version and the PDF must meet accessibility standards and archiving standards.” For an agenda, the PDF is the printable copy with fixed pages, and often the file of record. A tagged one can be accessible too: our guide to what “ADA compliant PDF” can and can’t mean explains what that takes. The ADA’s Title II rule covers both formats once they’re posted, and names neither as better: our guide to Title II for meeting documents has the dates.
The HTML copies agenda systems sell
Two large agenda vendors, CivicPlus and Diligent, now offer the same add-on: a web view generated beside the PDF, which stays unchanged. Our research on agenda platforms quotes what each says. Other systems build their own web views of the agenda, and in our spot checks some had no headings, or an empty title and no language. Our reading: a generated copy is only as good as the document it’s made from, and we found no independent audit of DocAccess’s web views. If your system offers one, open it and check that it has a title, real headings and the right language.
Doing both from one draft
- Write it with real headings and lists, in Word, your website’s page editor or Ada Editor. Our agenda template starts you off.
- Publish the page. If your website has a page editor, paste or rebuild the agenda there with its headings. Ada Editor can also export a standalone web page; our reading is that many website systems only accept content entered in their own editor, so ask whoever runs your site whether it can host one.
- Make the tagged PDF from the same draft, following our guide to turning a Word document into a tagged PDF.
- Link the PDF from the page, with its format and size in the link, for example “Agenda (PDF, 120 KB)”.
- If you also post through an agenda system, follow our steps for posting a PDF to an agenda system.
Ada Editor’s web page export works for every language; its PDF export covers Latin scripts only, as our accessibility statement says.
Corrections and limits
This guide is our recommendation, not legal advice: neither format is required by the ADA over the other.
Found something wrong or out of date? Report a correction to this guide (public, on GitHub).
None yet.
Sources
Read on October 12, 2026.
- Neil Williams, Government Digital Service, Why GOV.UK content should be published in HTML and not PDF (July 16, 2018).
- Vendor statements on HTML views: the sources listed on our agenda platform research.