Building an Accessibility-First Documentation Workflow
- Presentation
- Multimodality and Accessibility in TD
- 04. April
- 13:00 - 13:40 PM (CEST)
- 11:00 - 11:40 AM (UTC) | 07:00 - 07:40 AM (EDT)
- Find your local time here: Time Converter
- finished
-
Angel Petrov
- Access Drum
Contents
This presentation explores how to seamlessly integrate accessibility into different stages of the documentation creation process, ensuring that content is usable by all audiences, including those with disabilities. The talk will begin with the importance of considering accessibility in content planning, including how to prioritize inclusive language and structure from the outset. Then we will cover practical steps for incorporating accessibility during the authoring, editing, and publishing phases, with a focus on ensuring compatibility with screen readers, providing alt text for images, and creating accessible links and navigation. Attendees will learn how to identify common accessibility barriers and implement best practices to create content that meets accessibility legislation, such as the European Accessibility Act (EAA) requirements. This session is ideal for technical writers, editors, and content managers looking to build a more inclusive documentation workflow.
Takeaways
Learn how to integrate accessibility into the documentation process, identify common barriers in content creation, and implement best practices for creating inclusive, WCAG-compliant content.
Prior knowledge
01. Basic Understanding of Documentation:
Audience should have some familiarity with technical documentation processes, but this will be explained at a high level.
02. Introduction to Accessibility:
Accessibility concepts will be introduced from scratch, explaining them in non-technical language. The importance of inclusive content will be highlighted, but the audience doesn’t need prior experience with accessibility.
03. WCAG Basics Explained:
No prior knowledge of WCAG is required. The principles of WCAG will be briefly covered in a simple and relatable way (e.g., using “making documents easy to read and navigate” instead of complex technical jargon).
04. No Tool-Specific Experience Needed:
While tools like CMS or publishing platforms will be mentioned, no hands-on experience is required. Any necessary explanations about tools will be included in the talk.