# Event programme PDF accessibility review — editable record

This worksheet helps a named editor inspect a particular file. It does not certify compliance. Replace every bracketed field before use.

## File and source

| Field | Record |
| --- | --- |
| Event, date and venue | [ ] |
| Approved programme source file and owner | [ ] |
| Published PDF URL, filename and version | [ ] |
| Matching current HTML programme URL | [ ] |
| Language(s) in the file | [ ] |
| Reviewer and review date | [ ] |

## Source document before export

| Check | Result / evidence / correction owner |
| --- | --- |
| Document title and language are set | [ ] |
| Event date, time zone, venue and access details match the approved source | [ ] |
| Heading styles form a logical hierarchy; no heading is just enlarged body text | [ ] |
| Session order is logical when read linearly; columns do not scramble times and rooms | [ ] |
| Schedule tables, if used, have meaningful headers and no layout-only merged cells | [ ] |
| Informative images have concise alternative text; decorative art is marked decorative | [ ] |
| Links use meaningful visible names and point to the current destination | [ ] |
| Changes and access information are not communicated by color alone | [ ] |
| Text contrast and legibility are checked in the actual design | [ ] |
| Built-in source-document accessibility checker issues are reviewed | [ ] |

## Exported PDF and published route

| Check | Result / evidence / correction owner |
| --- | --- |
| Export used the authoring application's accessible/tagged-PDF option | [ ] |
| PDF document title and language are correct | [ ] |
| Tags reflect headings, paragraphs, lists, table headers and links | [ ] |
| Tags and reading order follow the visible session sequence | [ ] |
| Every needed image has useful alternative text; decoration is omitted from reading order | [ ] |
| Link text, destinations, bookmarks and keyboard navigation work | [ ] |
| Text is selectable and readable at increased zoom/reflow where supported | [ ] |
| Automated PDF check findings were reviewed and repaired | [ ] |
| Manual reading-order and assistive-technology review is recorded | [ ] |
| Published PDF and current HTML page show the same approved schedule and update time | [ ] |

## Decision

| Item | Record |
| --- | --- |
| Open issue, severity and affected attendee task | [ ] |
| Fix owner and due date | [ ] |
| Retest evidence | [ ] |
| Final reviewer and approval date | [ ] |
| Next review trigger (programme, room, access or contact change) | [ ] |

If a PDF is delayed or cannot be made usable in time, keep the current event details available on an accessible HTML page and provide a staffed contact route. Do not quietly replace a known-broken file with another unreviewed export.