# Accessible board agendas and meeting documents Canonical page: https://districtproof.io/services/board-agenda-accessibility Build navigation, clear headings, meaningful links, and a reliable reading sequence into board agendas. Treat the agenda, supporting packet, and later revisions as related but separately versioned documents. ## What this service covers - Agenda headings and bookmarks - Packet navigation and references - Supporting documents and scans - Version and publication checks ## Start with the task and the source Agendas help the public understand what a board will consider. A clear sequence of agenda items, readable labels, and meaningful links matters both visually and through a screen reader. An agenda that simply points to an unreviewed attachment leaves part of the task unfinished. ## What needs human attention Build the agenda in a structured source template. Use real heading styles for sections and descriptive link text for supporting materials. Check whether PDF assembly has preserved tags and navigation. Identify scanned supporting material early so it can be handled within the review window. ## Make the next update easier Late supplements need a predictable process. Agree on the intake cutoff, how new files will be named, and whether a revised full packet or separate supplement will be posted. Verify the version that is actually available to the public. ## 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 Care](https://districtproof.io/solutions/board-packet-service). [Request a fixed quote](https://districtproof.io/pricing) after a sample review or begin with your public website inventory. For the regulatory context, read the [ADA Title II school district deadline guide](https://districtproof.io/resources/ada-title-ii-deadline-school-districts). Your district and counsel determine the applicable obligations and exceptions. ## An agenda is a route into a public meeting A resident may want to find one agenda item, open its supporting material, and return to the agenda. That sequence should stay understandable when the resident uses a keyboard, a screen reader, a small screen, or text magnification. An agenda review therefore looks beyond whether the first page has tags. It considers the whole path from the meeting listing to the relevant attachment. District teams often assemble agendas under time pressure. Content may arrive as office documents, exported reports, image scans, or a PDF someone received by email. Identify those formats before the final assembly deadline. A component inventory shows what can be corrected in its source and which attachments require separate remediation. Illustrative district scenario ### The agenda item links to a scanned attachment The agenda itself may have clear headings and links while a supporting financial schedule is an image. A resident who reaches the attachment still cannot obtain its information as text. The scope should identify both files and explain whether the attachment is being remediated, replaced with a better source, or referred back for a district decision. ## Review navigation and the assembled result Check that agenda headings have a sensible hierarchy, that attachment labels describe their subject, and that links still work after files are combined. If bookmarks are part of the agreed packet design, they should help readers reach actual sections. Page references, attachment titles, and agenda numbering should agree with the final content. Review the final combined document after assembly. A component that worked on its own can change when merged, inserted, or re-exported. Keep both the component list and the final version identifier in the handoff so the district can trace where a problem was introduced. ## Make late additions a defined part of the process Decide who may authorize a supplement, how it will be named, and whether it will replace the full packet or be posted as a separate file. A small textual change may need a narrower recheck than a newly scanned attachment, but the decision should be visible. Avoid treating a revised file as automatically covered by the previous review. A recurring arrangement can reserve an agreed review window around the board calendar. The intake cutoff, page allowance, complex-content treatment, and revision policy determine whether the workflow is achievable. Those details belong in the written scope, along with the person responsible for final posting. ## Give the board office a usable delivery record The board office needs a concise list of what was returned, what remains open, and which version should be posted. Technical findings should not require staff to interpret a tool report before they can do their next task. A delivery record can separate content questions, review outcomes, and publication actions. Explore the [Board Packet Service](https://districtproof.io/solutions/board-packet-service) for recurring work, or use the [board packet guide](https://districtproof.io/resources/board-packets-accessibility-guide) to organize the next meeting. DistrictProof’s role is to support the document workflow; the district retains responsibility for meeting notices, records, and legal decisions. ## Frequently asked questions ### What do you need to scope the work? A representative sample, the best available source files, the intended use, and your required publishing schedule. Website projects also need an agreed list of pages, templates, and tasks. ### How is this priced? We review complexity and scope before providing a fixed quote. Page counts alone do not describe the effort required for scans, tables, forms, or interactive components. ### Will an automated checker be enough? A checker can identify some issues, but a human review is needed for meaning, order, descriptions, and use. Evidence should identify both the tools and the manual coverage. ### What will we receive? Your agreement defines the returned files or issue log, review coverage, delivery schedule, and evidence record. Publication verification should reference the live version.