Quick Actions

  • Use plain language and avoid technical jargon when possible.
  • Include infographics, diagrams, and visual explanations to break down complex concepts. Ensure that all visual items include textual descriptions and alt text where appropriate.
  • Use real-world examples to ground abstract ideas.
  • Maintain a living glossary of technical terms and acronyms
  • Include a summary page at the beginning of each document outlining its purpose, key content, and its relevance to other work
  • Ensure all documents including drafts, meeting notes and final publications are accessible from the start, and throughout the collaboration process not just at the end of the process
  • Publish standards in accessible formats like properly structured Word documents and tagged PDF documents

Long-term Actions

  • Train chairpersons and committee members in accessible document creation practices

More Information

Examples

  • UK – British Standards Institution (BSI) uses accessible PDFs with proper headings, tags, and alternative text, and provides plain language summaries. They also offer multilingual versions of key documents for non-native speakers.
  • Australia – Standards Australia creates structured documents with proper headings for screen readers and plain language guides for complex terms. Peer reviews ensure accessibility before publication.
  • Germany – German Institute for Standardization (DIN) provides documents in multiple formats (PDF, Word, HTML) with proper tagging and plain language versions for cognitive accessibility. They also collaborate with experts to simplify technical language.

Barriers these actions address