write-an-accessible-policy-document

# write-an-accessible-policy-document Accessibility includes meaning, format, process, and available alternatives. ## When to use - Use for employee, public, customer, student, vendor, safety, or operational policies. - Do not simplify away a right, duty, exception, threshold, or appeal path. ## Procedure 1. Confirm policy authority, purpose, audience, jurisdictions, source requirements, effective date, and owner. 2. Organize around scope, definitions, rights, duties, steps, exceptions, evidence, decisions, appeals, contacts, and changes. 3. Use plain language, active voice, short sections, descriptive headings, lists, examples, and consistent terms. 4. State deadlines, amounts, thresholds, responsible roles, and alternate paths precisely. 5. Design heading hierarchy, reading order, links, tables, notes, color-independent meaning, and adaptable layout. 6. Provide accessible HTML and document formats, language and interpretation routes, and contact alternatives as required. 7. Test with keyboard, screen reader, zoom, reflow, contrast, links, document structure, and representative readers. 8. Reconcile accessible versions to the approved source and version future changes together. ## Done - An accessible policy document records authority, scope, rules, rights, exceptions, procedures, contacts, appeals, dates, and version - Source, plain-language, keyboard, screen-reader, zoom, reflow, contrast, format, alternative, and version-parity checks verify use