ED510 Journey Week 4: Microsoft Word & Accessible Document Design

Microsoft Word & Accessible Document Design

One important lesson from this project came from a misunderstanding on my part. Initially, I built the entire instructional manual in Canva because I misread the assignment and believed the final product could be created using a design platform. After completing the full Canva version, I realized the assignment specifically required the document to be built in Microsoft Word to demonstrate accessibility features native to that platform. As a result, I had to rebuild the entire project in Word.

While this error cost me additional time, it ultimately strengthened my understanding of accessible document structure. Rebuilding the manual required me to intentionally apply Word heading styles, construct a functional Table of Contents, format accessible tables, add alt text to images, embed descriptive hyperlinks, and run the built-in Accessibility Checker. Because I am comfortable using Word, the rebuild process was efficient; however, the experience reinforced the importance of carefully reviewing assignment requirements and aligning tools with instructional goals.

In hindsight, the revision process deepened my learning more than the original build alone would have. Converting a visually designed document into a structurally accessible Word document required me to think critically about format versus function, appearance versus usability, and design versus compliance.

Here is my original Blog post prior to finding my error. 

Module 4 challenged me in ways I did not initially expect. While the primary focus of the assignment was accessible document design, the most significant learning experience for me centered around implementation and platform limitations.

For this project, I intentionally chose to create a document that would serve a real purpose beyond the classroom. I am currently working to relaunch the National Technical Honor Society at Southern Union State Community College, and I wanted this project to function as a practical implementation guide for our Technical Division faculty. Rather than creating a document that existed only for grading purposes, I built something I intend to use professionally.

One of the more challenging aspects of this project involved working within Microsoft 365. I typically use Google Docs for form creation and collaboration because I am comfortable with that environment. However, our institution recently transitioned to Microsoft 365 through the Alabama Community College System (ACCS), and many collaborative tools—such as SharePoint—are restricted. My goal was to create truly functional, fillable forms that would store information and be shareable among faculty without requiring downloads and email attachments. Due to system restrictions, that process became far more complex than anticipated.

Creating interactive, fillable documents in Microsoft Word required learning new features and navigating platform constraints. While I could have completed the project more quickly using Google Docs, I chose to use Microsoft 365 to align with our institutional platform and ensure the materials would be usable in a real-world setting. Ensuring that forms retained entered data, could be shared properly, and met accessibility expectations required careful formatting and testing.

A major focus throughout this project was applying accessibility principles intentionally rather than incidentally. I paid close attention to using structured heading styles instead of manually enlarging text so that screen readers could navigate the document properly. I ensured font sizes were large enough for readability and selected clean, professional fonts that reduce visual strain. I was also mindful of color contrast, especially when using National Technical Honor Society purple and Southern Union colors, to make sure text remained legible against backgrounds. All images were given alternative text descriptions so assistive technologies could interpret them, and hyperlinks were written in descriptive language rather than using generic phrases like “click here.” Thinking consciously about these elements changed how I approach document design. Instead of focusing only on appearance, I began prioritizing clarity, structure, and equitable access.

Another important takeaway from this module was the practical application of Universal Design for Learning principles. Designing with accessibility in mind reinforced that inclusive practices do not just benefit students with identified disabilities—they improve usability for everyone. Clear organization, strong contrast, and meaningful link text make documents easier to navigate for all readers.

Overall, this project became more than an academic assignment. It is now a working framework for launching National Technical Honor Society within our Technical Division. My plan is to remove the course labeling from the final version and implement it as part of our recruitment and induction process. This dual-purpose approach made the learning experience more meaningful and directly connected course content to leadership practice.

While navigating Microsoft 365 restrictions was frustrating at times, the experience strengthened my problem-solving skills and deepened my understanding of digital content creation within institutional constraints. In the end, the project reflects both academic growth and professional application. 

Here is a link to view the project.