Quick guide: How to make a Word document accessible
1. Use real headings
Don't just make text bold or larger to look like a heading. Select the text, go to Home → Styles, and choose Heading 1, Heading 2, or Heading 3.
Example: Use Heading 1 for the document title and Heading 2 for major sections. Keep headings in logical order.
2. Describe meaningful images
Right-click an image and select View Alt Text or Edit Alt Text (wording varies by version). Write a short description of the information the image communicates. Mark purely decorative images as decorative.
Example: Instead of “photo,” write “Students volunteering at the ETBU food pantry.”
3. Make links descriptive
Use link text that explains where the link goes. Avoid vague text such as “click here” or “read more” when the destination isn't clear from context.
Better: “View the 2026–2027 Academic Calendar.”
4. Keep tables simple
Use tables for data, not to arrange the page layout. Give data tables clear column headers, avoid merged cells where possible, and don't use blank rows or columns for spacing.
5. Make text easy to read
Use sufficient contrast between text and background. Don't rely on color alone to communicate meaning, and avoid putting essential information only inside an image.
6. Run the Accessibility Checker
In Word, select Review → Check Accessibility. Review the issues and follow the suggestions to fix them. Run the checker again after making changes.
The checker identifies many common problems, but it cannot determine whether every document is fully accessible.
Official resource: Microsoft: Make your Word documents accessible.
How will faculty and staff know if a document is inaccessible?
-
Start with the Accessibility Checker. It can flag common issues such as missing alternative text, problematic tables, and other structural problems.
-
Look at how the document is organized. A document may look attractive but still be difficult for a screen reader to navigate if headings are only visually formatted.
-
Check whether the text is selectable. If a PDF is just a scanned image of a page, a screen reader may not be able to read its contents unless text recognition (OCR) has been applied and the result has been checked.
-
Don't assume that passing the checker means everything is fixed. Automated tools cannot catch every issue, including unclear wording, inaccurate image descriptions, or every problem with reading order.
For PDFs, Adobe Acrobat has tools for checking accessibility and correcting issues, but more complex documents may require specialized remediation.
More Accessibility Resources for ETBU Employees
Website Initiatives for Accessibility
The following resources have been published to ETBU faculty and staff for our upcoming initiatives and creating a more accessible digital experience for all users.
- Accessibility Reminders Archive
-
October 26, 2026
As part of ETBU's ongoing website improvements, we are working to make our digital content more accessible to everyone, including individuals who use assistive technology.
ETBU's Website Accessibility Statement explains our commitment to accessibility and provides a way for visitors to report barriers or request accessible versions of documents.
Accessibility is a shared responsibility. Departments are responsible for the content they create and publish on http://www.ETBU.edu, including the accessibility of PDFs and Word documents. As we continue improving the website, departments will need to review their published documents and address accessibility issues as they are identified.
You do not need to be an accessibility expert to get started. Microsoft Word includes a built-in Accessibility Checker that can identify many common issues and provide suggestions for correcting them. The Web Team can provide guidance on website-related issues and help coordinate updates to published content and has created a checklist of resources for Word and pdfs.
We encourage departments to start with documents currently published on http://www.ETBU.edu, prioritizing materials frequently used or essential to students, prospective students, and the public. When an accessibility barrier is reported, the department responsible for the document should work to provide an accessible version or correct the issue.
Thank you for helping ETBU make its digital content more accessible and inclusive. Your participation is essential to making this effort sustainable across the university.
- Website Timeline
-
There will be six phases of Development working on an iterative development cycle.
-
Back-End Foundation: Strengthened hosting, security, and content management tools to create a stable, reliable foundation for the website.
-
Front-End Transformation: New design, intuitive navigation, and refreshed content will deliver a cohesive, engaging experience at launch.
High Level Project Roadmap Month Range High Priorities Completion Status July-August • Priorities assessment & mission alignment • Technical audit of existing platform, integration & functionality • Identify opportunities to preserve existing work • Findings & roadmap report Complete Sep to Oct • Set up ETBU-owned Pantheon workspace • Migrate existing site into Pantheon • Gap analysis • Resolve all issues identified from gap analysis • Launch Pantheon site with full University ownership of code Complete Oct to Dec Infrastructure Resilience | • Define new menu navigation • Streamline roles, permissions & content governance • Best-practice realignment • Site health, stability & security improvements In Progress Jan to Feb Wireframing and Back-End Structure Not Started March to April Visual Design Mockups | • Homepage • Key sub-page templates • Mobile screens • Styleguide Not Started May to August Front-End Dev & Launch | Content migration • Training • Coordinate launch steps • Final launch! Not Started -