Session 1: Foundations and Document Practice
Introduced core accessibility expectations and included a quiz and applied Word or PowerPoint activity.
Case Study
I designed this pathway to help faculty build practical accessibility knowledge through staged instruction, applied practice, assessment, coaching, and ongoing support.
Faculty needed practical, manageable preparation for creating and reviewing accessible course materials without being overwhelmed by legal, technical, or remediation requirements.
Accessibility expectations affected documents, presentations, multimedia, LMS content, instructional activities, and publisher-provided resources. A single awareness session would not provide enough instruction, practice, or follow-up to support meaningful change.
The challenge was to translate broad accessibility requirements into a learning pathway faculty could understand, practice, and apply within their own course responsibilities.
The pathway was developed within a higher education environment preparing for ADA Title II digital-accessibility requirements and WCAG 2.1 AA expectations.
Faculty participants brought different levels of technical skill, course-design experience, accessibility knowledge, available time, and familiarity with document and multimedia tools.
The training also needed to distinguish among faculty-created content, institutionally supported content, and publisher-provided materials that faculty or instructional designers might not be authorized to revise.
The result needed to be scalable enough for self-paced participation while still providing opportunities for applied work, clarification, consultation, and follow-up.
The pathway had to support faculty learning within real institutional limits rather than assume unlimited staffing, time, authority, or remediation capacity.
I approached the project as a faculty-learning design problem rather than a one-time compliance communication. Faculty needed more than a list of requirements. They needed a staged pathway that introduced concepts, provided examples, required practice, checked understanding, and connected participants with support.
I organized the experience so that knowledge, application, and follow-up worked together. The pathway was designed to help faculty understand what accessibility requires, practice with common content types, identify when they could make corrections themselves, and recognize when publisher or institutional support was needed.
Explain the purpose, legal context, accessibility principles, and common barriers in clear instructional language.
Use applied activities so faculty work directly with documents, presentations, multimedia, and course materials.
Use quizzes and completion requirements to confirm participation and reinforce key concepts.
Connect training with coaching, follow-up communication, consultation pathways, and guidance for unresolved concerns.
Introduced core accessibility expectations and included a quiz and applied Word or PowerPoint activity.
Extended faculty understanding through self-paced instruction and a required quiz.
Planned as a more hands-on stage focused on applying accessibility practices with guidance and feedback.
Planned to address PDF accessibility and remediation considerations.
Provided a pathway for one-to-one clarification, troubleshooting, and faculty-specific support.
Used communication and workflow tools to support participation, reminders, completion, and next steps.
The pathway connected instructional content with practice and assessment so faculty were not only exposed to accessibility expectations but also required to work with the material.
Self-paced videos and instructional materials introduced accessibility expectations, terminology, and examples.
Quizzes reinforced key concepts and established clear completion expectations.
Word and PowerPoint tasks asked faculty to practice accessibility techniques rather than only read about them.
Consultations, coaching, and follow-up communication connected the training to real faculty questions and course materials.
The pathway was designed to move faculty from awareness toward practical application while acknowledging that not every accessibility problem can be solved within a training module.
Training materials may contain institutional references, faculty instructions, internal workflows, or platform-specific details and are therefore not displayed publicly. Generalized or anonymized examples may be used in future presentations, publications, or professional discussions when they can be shared without exposing confidential information.
Examples may include:
Faculty development can build knowledge and practice, but it does not remove the institution’s responsibility to establish clear processes, provide support, and address barriers that extend beyond an individual faculty member’s authority.
Publisher-created materials required a separate pathway because faculty and instructional designers may not have legal authority, source files, or practical capacity to revise proprietary content.
The guidance emphasized that faculty should first verify that they had the most current version of the publisher material. If the current version remained inaccessible, the next step was to contact the publisher and request an accessible version or remediation guidance.
The pathway also clarified that identifying a problem in publisher content does not automatically make the instructional designer responsible for correcting that content.
Confirm that the most recent publisher version is being used.
Check whether the current version meets accessibility expectations.
Contact the publisher for an accessible version, update, or remediation guidance.
Use institutional support or escalation pathways when the issue cannot be resolved directly.
The project established a repeatable faculty-development pathway designed to build accessibility knowledge, provide structured practice, and connect training with ongoing support.
Its current value lies in creating a clearer sequence for instruction, application, assessment, consultation, and follow-up rather than treating accessibility as a single presentation or isolated checklist.
The pathway also provides a structure that can be revised as legal requirements, accessibility standards, institutional workflows, faculty needs, and available support change.
Faculty accessibility development works best when it is designed as ongoing professional learning rather than a one-time compliance event.
Clear explanations matter, but practice matters more. Faculty need opportunities to work with real content, receive guidance, and understand where their responsibility begins and ends.
I also learned that training cannot compensate for unclear institutional processes. Faculty need defined support, publisher guidance, escalation pathways, and realistic expectations about remediation responsibilities.
Finally, completion workflows matter. Without follow-up, reminders, consultation options, and documentation, even well-designed training can become disconnected from day-to-day course work.
Connect
Connect about faculty training, accessibility strategy, professional learning, conference presentations, or instructional design leadership.