Skip to content

How to Make an Accessible Word Document: A Checklist

By · · 15 min read

Title card reading How to Make an Accessible Word Document, a checklist, next to a page icon with three ticked items.

An accessible Word document is one that people can read and navigate whatever way they use it: with a screen reader, magnified, with high-contrast colours, or by keyboard alone. In practice that comes down to a short list of habits. Use real heading styles, give the file a title, describe images, keep tables simple, write links that make sense on their own, and check contrast. Then run Word's Accessibility Checker before you share.

For each item, this checklist gives the exact Microsoft 365 steps (Windows first, with Mac and Word for the web notes where they differ), why it matters, and a place to practise it. This guide is published by Guccibase, who builds and runs this site. The steps were checked against Microsoft Support documentation in November 2026, and the standards come from the W3C, GOV.UK and Section508.gov.

Key Takeaways

  • Structure comes first: built-in heading styles, real lists and a table header row are what screen readers use to navigate.
  • Every informative image needs alt text; purely decorative ones should be marked as decorative.
  • Link text should describe the destination, and text needs a contrast ratio of at least 4.5:1 (3:1 for large text) to meet WCAG level AA.
  • Give the document a Title property and the right language so assistive technology announces and pronounces it correctly.
  • Finish with Review > Check Accessibility, but treat it as a safety net: it cannot judge whether your alt text or link text is actually useful.

What makes a Word document accessible?

A document is accessible when its meaning does not depend on seeing the page layout. A sighted reader spots a heading because it is big and bold; a screen reader user only knows it is a heading if the paragraph uses a heading style. The same is true for lists, table headers and links. Accessibility in Word is mostly about putting that meaning into the file's structure, not just its appearance.

The benchmark most organisations use is the Web Content Accessibility Guidelines (WCAG) from the W3C. Public bodies add their own guidance on top. The UK government's guidance on publishing accessible documents asks for real heading styles, simple tables, descriptive link text, a meaningful title and good contrast. In the US, Section508.gov's guide to creating accessible documents points to Word authoring and testing checklists that cover the same ground.

Microsoft's own list in Make your Word documents accessible to people with disabilities is shorter but lines up: alt text, simple tables with headers, built-in headings in order, meaningful links, no meaning carried by colour alone, enough contrast, and nothing important hidden in headers and footers.

The checklist at a glance

# Check Where in Word (Windows)
1 Use built-in heading styles in order Home > Styles
2 Set the document title File > Info > Properties > Title
3 Set the language Review > Language > Set Proofing Language
4 Add alt text or mark images decorative Right-click the picture > View Alt Text
5 Keep pictures in line with text Picture Format > Wrap Text > In Line with Text
6 Give tables a header row and a simple structure Table Layout > Repeat Header Rows
7 Write descriptive link text Insert > Link > Text to display
8 Use real bulleted and numbered lists Home > Bullets / Numbering
9 Check contrast and do not rely on colour alone Home > Font Color
10 Space with paragraph settings, not blank lines Layout > Spacing
11 Keep text readable and plain Home > Font, Home > Align Left
12 Keep key content out of headers, footers and text boxes Insert > Header & Footer
13 Run the Accessibility Checker Review > Check Accessibility
14 Remove personal data before you share File > Info > Check for Issues

The sections below walk through each one.

1. Use built-in heading styles in order

Headings are the single most useful accessibility feature in a long document. Screen reader users jump from heading to heading the way sighted readers skim, and Word builds the Navigation pane and automatic tables of contents from the same styles.

  1. Click in the heading text.
  2. On the Home tab, in the Styles gallery, choose Heading 1 for main sections, Heading 2 for sections inside them, and so on.
  3. Do not skip levels: a Heading 3 should sit under a Heading 2, not directly under a Heading 1.
  4. Check the outline with View > Navigation Pane. Every heading should appear there in a sensible order.
Heading 1: Annual report Heading 2: Results Heading 3: Sales Heading 3: Costs Heading 2: Next steps Main sections Subsections sit inside a section
A heading outline with no skipped levels, as it appears in the Navigation pane.

Text that is only made big and bold is a "fake heading". It looks right but carries no structure, and the GOV.UK guidance says plainly not to use bold to mark up subheadings. Change how the heading looks by modifying the style, not by formatting each heading by hand. The guide to using styles in Word covers that in depth, and the lesson on real headings with heading styles explains the rules.

Practise it: Turn look-alike headings into real headings (free) and Repair a skipped heading level (free).

2. Give the document a meaningful title

The Title property names the document independently of its file name. It travels with the file, including when you save it as a PDF, so tools that read it can show a real title instead of something like "final_v3_JB.docx". GOV.UK asks for "a meaningful title" for every published document, and WCAG has a matching requirement, success criterion 2.4.2 Page Titled, for titles that describe the topic or purpose.

Windows: go to File > Info. In the Properties list on the right, click Add a title next to Title and type it. Microsoft's article on viewing or changing the properties for an Office file describes the same steps.

Mac: choose File > Properties, then the Summary tab, and fill in Title.

Word for the web: document properties cannot be changed in the browser. Use Editing > Open in Desktop App and set the title there.

Practise it: Set the document's Title property (free).

3. Set the document language

Screen readers use the language setting to choose a voice and pronunciation rules. A French quotation marked as English will be read with English pronunciation, which can be hard to follow.

  1. Select the text (press Ctrl+A for the whole document, or select just a passage in another language).
  2. Go to Review > Language > Set Proofing Language.
  3. Choose the language and select OK.

In Word for the web the path is Review > Editor > Set Proofing Language, according to Microsoft's article on the languages used to check spelling and grammar.

4. Add alt text to images, or mark them decorative

Alt text is the short description a screen reader reads in place of a picture, chart, SmartArt graphic or shape. Microsoft's guide to writing effective alt text says it usually needs no more than "a sentence or two" and should describe the image's purpose, not its file name. Images that add nothing, such as a decorative border, should be marked decorative so screen readers skip them.

  1. Right-click the picture and choose View Alt Text (some versions say Edit Alt Text). You can also select it and go to Picture Format > Alt Text.
  2. In the Alt Text pane, type a description, or tick Mark as decorative.
  3. If Word generated a description for you, read it and correct it before you keep it.

Charts and tables need a different approach from photos: the description should give the takeaway, not list every value. The full method, with examples for photos, charts, SmartArt and tables, is in Alt Text in Word: How to Write It for Images, Charts and Tables.

Practise it: Replace a file name used as alt text (free) and Mark a decorative divider as decorative (free).

5. Keep pictures in line with text

A picture set to In Line with Text behaves like a character in the paragraph, so it is read at the point where it appears. Floating pictures (Square, Tight, Behind Text and so on) are anchored to a paragraph but positioned separately from the text, so a screen reader may meet them out of order or not at all. Section508.gov's Word training module on text boxes makes the same point for text boxes. It says assistive technology cannot access text box content unless the box is placed in line with text, and its test step is to run the Accessibility Checker and confirm there are no "Object Not In Line" errors.

To fix it, select the picture and choose Picture Format > Wrap Text > In Line with Text, or use the Layout Options button that appears beside a selected picture. If a design really needs text to wrap around an image, keep the image anchored to the paragraph it belongs to and give it alt text.

There is more on the trade-offs, and on positioning images without the layout jumping, in How to Insert and Position Images in Word Without Breaking the Layout.

6. Give tables a header row and a simple structure

Screen readers announce a table's column headers as the user moves from cell to cell, so they know which value they are hearing. That only works if Word knows which row holds the headers.

  1. Click in the first row of the table (the row with the column names).
  2. Choose Table Layout > Repeat Header Rows. Do this for every data table, not only long ones: Section508.gov's Word training on tables explains that the row does not change visually but is then identified to assistive technology as the header row. Microsoft's article on repeating a table header on later pages also gives the dialog route: right-click the row, choose Table Properties, and on the Row tab tick Repeat as header row at the top of each page.
  3. On the Table Design tab, also tick Header Row in Table Style Options so the table style formats that row as a header.

Keep the grid simple. Microsoft's Accessibility Checker rules warn against merged cells, split cells and nested tables, and GOV.UK says to use tables only for data. Do not use a table to lay out a page; use paragraph settings, tabs or columns instead.

Practise it: Mark a table header for screen readers (free) and Repeat the header row on a long table (free).

Screen reader users often pull up a list of all the links in a document. A list of "click here", "here" and "more" tells them nothing. GOV.UK's rule is to make sure link text "clearly describes where the link goes" and makes sense out of context.

  1. Select the words that describe the destination, for example "2026 leave policy".
  2. Go to Insert > Link (or press Ctrl+K).
  3. Enter the address. The Text to display box shows the words people will see and hear.

Avoid pasting raw web addresses into body text. They are long to listen to and rarely describe the page.

Practise it: Replace "click here" link text (free).

8. Use real bulleted and numbered lists

A list made with Word's list buttons tells a screen reader how many items there are and where the list ends. A list typed with hyphens or "1." at the start of each line is just a series of paragraphs.

Select the lines and choose Home > Bullets or Home > Numbering. If a list was typed by hand, delete the typed markers first. The lesson on real numbered and bulleted lists shows how to fix numbering that restarts in the wrong place.

Practise it: Use real lists so screen readers count items (free).

9. Check contrast, and do not rely on colour alone

Low-contrast text is hard to read for people with low vision and for anyone reading on a phone in sunlight. WCAG success criterion 1.4.3 sets a contrast ratio of at least 4.5:1 for normal text and 3:1 for large text, which it defines as at least 18 point, or 14 point bold.

  • For body text, Microsoft recommends the Automatic font colour (Home > Font Color > Automatic), which Word shows as black on a light background and white on a dark one.
  • Avoid pale grey text and coloured text on coloured shading.
  • Never let colour be the only way to show meaning. "Items in red are overdue" fails for anyone who cannot tell red from other colours. Add a word, a symbol or a column that says "Overdue". GOV.UK gives the same advice.

The Accessibility Checker flags some low-contrast text, but not every case, and it cannot spot meaning carried by colour alone. The lesson on colour and contrast explains how to check a ratio.

Practise it: Fix low-contrast text (free).

10. Space with paragraph settings, not blank lines

Empty paragraphs and rows of spaces are read aloud by screen readers as "blank" over and over, and they break the layout as soon as the text changes. Set the space instead:

  1. Select the paragraphs.
  2. On the Layout tab, set Spacing Before and Spacing After (for example 0 pt before and 8 pt after for body text).
  3. To push a heading to a new page, use Insert > Page Break (Ctrl+Enter) rather than pressing Enter repeatedly.

Better still, put the spacing into the styles themselves so every paragraph of that type matches. See paragraph spacing instead of blank lines.

Practise it: Delete stray empty paragraphs (free).

11. Keep text readable and plain

Microsoft suggests familiar sans serif fonts such as Arial or Calibri and extra white space between sentences and paragraphs. A few more habits help everyone:

  • Keep body text left aligned. Justified text creates uneven gaps between words.
  • Avoid long passages in italics, all capitals or underlining (readers expect underlined text to be a link).
  • Write in plain English and explain abbreviations the first time you use them, as GOV.UK recommends.
  • Do not put text inside images. It cannot be resized, searched or read by a screen reader unless you repeat it in the alt text.

12. Keep important content out of headers, footers and text boxes

Microsoft's best-practice list warns against putting important information only in headers and footers, because screen readers may not read them in the flow of the document. Page numbers and a running title are fine there. A contact phone number or a key deadline belongs in the body.

The same goes for text boxes: as the Section508.gov module linked in item 5 explains, assistive technology cannot reach text box content unless the box is placed in line with text. If you can, use a normal paragraph with shading or a border instead.

13. Run the Accessibility Checker

Once the structure is in place, let Word look for what you missed.

  1. Go to Review > Check Accessibility. The Accessibility pane opens, grouping problems as errors, warnings and tips.
  2. Select an issue to see the affected items, then use the arrow next to an item for Recommended Actions.
  3. Recheck until the list is clear, or until the only items left are ones you have deliberately decided to keep.

In Word for Microsoft 365 on Windows, an Accessibility: Investigate button also appears in the status bar when the document has issues. Microsoft lists the checker's rules in Rules for the Accessibility Checker.

Every warning and how to fix it is covered in The Accessibility Checker in Word: How to Fix Every Warning. Keep in mind what the checker cannot do: it will accept alt text that is wrong, link text that is vague, and a heading order that is technically valid but confusing. A quick human read with the Navigation pane open is still part of the job.

14. Remove personal data before you share

Accessibility and privacy checks often happen at the same moment, just before a document goes out. Use File > Info > Check for Issues > Inspect Document to find comments, tracked changes, hidden text and personal information in the file's properties. Remove what should not be shared, then set the Title property again if it was cleared.

The lesson on titles and safe metadata covers what to keep and what to strip. If you are exporting to PDF, fix the Word file first: the PDF can only carry the structure the document already has.

Practise it: Remove a personal name from document properties (free).

Differences on Mac and Word for the web

Most of the checklist works the same way on every version of Word, but a few steps differ:

  • Accessibility Checker: the path is Review > Check Accessibility on Windows, Mac and the web. On Mac the results are grouped as errors, warnings and tips. In Word for the web the pane shows Errors, Warnings, Tips and Intelligent services options, and a Recheck button.
  • Alt text on Mac: Control-click the picture and choose View Alt Text or Edit Alt Text, or use Picture Format > Alt Text.
  • Document title: set it with File > Properties > Summary on Mac. Word for the web cannot edit properties, so open the file in the desktop app.
  • Language in Word for the web: Review > Editor > Set Proofing Language.
  • Pictures in Word for the web: the browser version has fewer wrapping and positioning options. Pictures with wrapping set in the desktop app may not be movable in the browser.

Frequently Asked Questions

Does an accessible Word document make the PDF accessible too?

It is the essential first step. Microsoft's guide to creating accessible PDFs explains that Microsoft 365 uses the document's structure to create accessibility tags in the PDF. On Windows, choose File > Save As, pick PDF, select Options and make sure Document structure tags for accessibility is ticked. If the Word file has fake headings or missing alt text, the PDF will have the same problems. GOV.UK goes further and recommends HTML over PDF wherever possible.

Is passing the Accessibility Checker enough?

No. A clean result means Word found no rule violations it can detect. It cannot tell whether your alt text is accurate, whether link text makes sense, or whether colour alone carries meaning. Use the checker, then read the document once with the Navigation pane open and a critical eye on images and links.

Which WCAG level should a Word document meet?

Level AA is the usual target. UK public sector bodies are asked to meet WCAG 2.2 AA, and the US Revised 508 Standards incorporate WCAG 2.0 Level AA and apply it to electronic documents as well as web pages. For a Word document, that mainly means the items on this checklist: structure, text alternatives, link purpose, contrast and language.

How long does it take to make an existing document accessible?

It depends on how it was built. A document that already uses styles may need only alt text, a title and a checker pass. One built with manual formatting needs its headings and lists rebuilt first. Building with styles from the start is far quicker than fixing later.

Practise the whole checklist

Each item on this list is a habit, and habits come from doing. On Word Exercises you can practise them on real .docx files in a browser editor that checks your work automatically. A good place to start is Fix four accessibility problems in a report (free), followed by the full accessible documents module.

Related guides in this series:

If a step here does not match what you see in your version of Word, let us know through the Help page so the guide can be corrected.

Related posts

Written by Guccibase; see how these guides are written. Word Exercises is independent and not affiliated with Microsoft. Menu names follow Microsoft 365 as of 2026.