1 Set Up

Before you start writing

Why accessible word documents matter

An accessible Word document is designed so that people can find, understand, and navigate its content using different methods, including screen readers, keyboard commands, magnification, high zoom, and other assistive technologies. Accessibility is most reliable when it is built into the document while the content is being authored, rather than added as a final repair.

The goal is not simply to make a document look organized. The underlying structure must also communicate the same relationships that a sighted reader can perceive visually.

Set a meaningful file name and document title

Use a file name that identifies the document clearly. Avoid vague names such as Final_v8.docx. Also review the document properties and provide a meaningful title when appropriate.

  • Use a concise, descriptive file name.
  • Review File > Info for document properties.
  • Update old metadata when reusing a previous document as a template.

Confirm the document language

The correct language helps screen readers pronounce words appropriately and supports spelling and proofing tools. Use Review > Language to confirm the language for the document or for passages written in another language.

Choose readable formatting

Use a clear, readable typeface and sufficient text size. Keep paragraphs reasonably short, use adequate white space, and favor left-aligned body text. Avoid large blocks of all-capital text and very light text colors.

Core principle

Use Word’s built-in structure and accessibility features to communicate meaning. Do not rely on appearance alone.

2 Organize

Create a navigable document

Create a real heading structure

Headings are navigation landmarks. A screen reader user can move through a document by heading, and Word can use headings to build the Navigation Pane and a table of contents.

Use built-in heading styles

  1. Select the heading text.
  2. On the Home tab, choose the appropriate style from the Styles gallery.
  3. Use Heading 1 for major sections, Heading 2 for sections within them, and Heading 3 for content nested under Heading 2.
  4. Open the Navigation Pane and confirm that the outline matches the intended organization.

Use true lists

When information is a list, use Word’s Bullets or Numbering tools. Assistive technology can then identify the content as a list and communicate the number and relationship of its items.Ìý

  • Use bullets when sequence does not matter.Ìý
  • Use numbering when order, priority, or steps matter.Ìý
  • Use nested list levels only when the hierarchy is meaningful.Ìý

Do not imitate lists with typed hyphens, asterisks, numbers, tabs, or repeated spaces.Ìý

Avoid

Do not create a “heading” only by making text larger, bold, underlined, or a different color. Visual formatting does not create document structure.

3 Add Content

Make information understandable

Write meaningful links

Link text should make sense when read on its own. People using assistive technology may review a list of links without the surrounding paragraph, so the link itself should identify its destination or purpose.

Avoid Better
Click here Download the Accessible Word Checklist
More information Microsoft Word Accessibility Support
A long pasted URL CUNYAccessibility Resources

 

Add useful alternative text

Images, charts, icons, SmartArt, and other meaningful visuals need a text alternative when their purpose or information is not already available in the surrounding text. Good alt text communicates why the visual matters in this document.

For images and icons

  • Describe the information or function that a reader needs to know.
  • Keep the description focused on context rather than cataloging every visible detail.
  • Avoid redundant openings such as ‘image of’ when the object type is already announced.
  • If the visual is purely decorative, mark it as decorative where Word supports that option.

For charts and graphs

Summarize the main message, trend, comparison, or outlier. If the data or conclusion is important, consider also placing the key takeaway in the body text or providing an accessible data table.

Keep in mind

Alt text should add equivalent meaning, not merely repeat a nearby caption or say “graphic” or “chart”.

4 Format

Keep content readable and logical

Keep images and objects in a logical reading flow

Floating text boxes, shapes, callouts, and images can create an unexpected reading order. Whenever practical, place objects In Line with Text. If a more complex layout is necessary, verify that the document still makes sense when read from beginning to end without relying on visual positioning.

  • Prefer inline images and objects.
  • Avoid overlapping objects and decorative sidebars that interrupt the reading sequence.
  • Do not use text boxes as a substitute for ordinary paragraphs or headings.

Build accessible tables

Tables work best when they represent genuine row-and-column data and have a simple, predictable structure. A screen reader must be able to understand which header applies to each data cell.

  • Use a clear header row.
  • Keep the grid simple and consistent.
  • Repeat header rows when a table continues across pages.
  • Avoid merged, split, and nested cells when possible.
  • Do not use tables only to position content on the page.

Do not rely on color alone

Color can support meaning, but it should not be the only way meaning is conveyed. A reader who cannot distinguish the colors should still receive the same information.

Color-only instruction Accessible alternative
Items in red are required. Required items are labeled ‘Required’ and may also appear in red.
Green = approved; yellow = pending. Use text labels or icons with labels in addition to color.

 

Also check that foreground and background colors provide enough contrast, particularly for body text, links, labels, and information placed over images.

Avoid layout shortcuts

Manual spacing can make a page look aligned while producing confusing output for screen readers and unstable results when text is resized or exported.

  • Do not use repeated spaces or tabs to create columns.
  • Use paragraph spacing, indents, styles, or Word’s Columns feature instead.
  • Avoid watermarks when they carry important information. If a watermark is necessary, repeat its meaning in regular document text.
  • For long documents, consider a Word-generated table of contents based on heading styles.

Design alternative

If the information does not need row-and-column relationships, paragraphs, lists, or Word’s Columns feature may be more accessible.

5 Check

Check accessibility before publishing

Use the Accessibility Checker throughout authoring

Word’s Accessibility Checker can identify many common problems and explain why they matter. Run it while you work, correct the issues it identifies, and run it again after substantial edits.

  1. Open Review > Check Accessibility. In some Word versions, accessibility checking may also be available through File > Info.
  2. Review errors, warnings, and recommendations.
  3. Select each item to locate the affected content.
  4. Read Word’s explanation and recommended action, then correct the source.
  5. Rerun the checker after changes.

Perform a manual accessibility review

Before sharing the file, perform checks that automated tools cannot fully judge:

  • Open the Navigation Pane and review the heading hierarchy.
  • Confirm that links are understandable out of context.
  • Review alt text for usefulness and context.
  • Confirm tables have understandable headers and simple relationships.
  • Zoom to 200% and check that content remains readable and usable.
  • Check that information is not communicated by color alone.
  • Use Read Aloud or a screen reader spot-check to listen for awkward reading order or missing context.
  • For high-impact documents, include accessibility specialist or assistive-technology user testing when feasible.

Important

Passing the checker is not the same as proving that a document is fully accessible. Human review is still necessary.

6 Export

Prepare your document for sharing

Export to PDF carefully

If a PDF is required, remediate the Word source before exporting. Accessibility features are easier to establish and maintain in the source document than to repair later in a PDF.

  • Use Word’s Save As or Export to PDF workflow rather than Print to PDF.
  • Preserve document structure tags and heading-based bookmarks when the export options are available.
  • Open the resulting PDF and spot-check title, headings/bookmarks, links, alt text behavior, tables, and reading order.
  • For externally published or high-impact PDFs, perform an additional accessibility review in Adobe Acrobat Pro.

Remember

PDF conversion is not an accessibility repair step. A weak Word source usually produces a weak PDF.

Common Accessibility Mistakes

Common problem Better approach
Bold, large text is used as a heading. Apply the correct built-in Heading style.
A list is typed with hyphens or manual numbers. Use Word’s Bullets or Numbering feature.
A link says ‘click here.’ Name the destination or action in the link text.
Alt text says only ‘image’ or repeats the caption. Explain the visual’s purpose or essential information.
A table uses merged cells and multiple header levels. Simplify the table or reorganize the information.
Tabs and spaces are used to line up columns. Use styles, indents, or the Columns feature.
The author waits until the end to run the checker. Check accessibility throughout the drafting process.
The Word file is immediately printed to PDF. Fix the Word source, export properly, then verify the PDF.

Quick Checklist Before Sharing

  • The file name and document title are meaningful.
  • The document language is correct.
  • Built-in Heading styles create a logical hierarchy.
  • Lists use Word’s Bullets or Numbering tools.
  • Meaningful visuals have appropriate alt text; decorative visuals are treated as decorative.
  • Images and objects follow a logical reading order.
  • Tables are simple and include clear headers.
  • Link text describes the destination or action.
  • Color is not the only way meaning is communicated, and contrast is sufficient.
  • Tabs, repeated spaces, and layout tables are not being used to position content.
  • The Accessibility Checker has been reviewed and rerun after fixes.
  • A manual review has been completed.
  • If a PDF was created, the exported PDF was checked before distribution.

References and Further Guidance