Accessible text companion

Accessible Document Design for Beginners

This page holds the same content as the slide presentation, as plain, structured text. It works with screen readers and keyboard navigation, reflows to any text size or zoom, and follows your device’s light or dark setting.

Getting around: use your screen reader’s heading commands, or the list below, to jump between sections. Every section is a heading, and the five keys are numbered in order.

Welcome and our goal

Welcome to Accessible Document Design for Beginners.

Our goal: write and design content in a way that ensures everyone has access to, and can use, the information and data, services, and content we provide.

Learn more in the supporting policy and standards: USER-01 (policy) and USER-01-01-S (standards).

Why accessible design matters

We start with two questions:

Perception and assistive technology

The course explores a few experiences of perception and uses assistive technology together, so the choices we make connect to real people’s needs.

Universal design

Universal design means content designed for use by all people, to the greatest extent possible, without the need for adaptation. Its principles are that a design is:

Where these standards come from

The best practices in this course reflect the W3C’s Web Content Accessibility Guidelines (WCAG 2.2). WCAG evolves over time—draft forms of 3.0 let us look ahead—and its levels, A, AA, and AAA, show deeper levels of accessibility. Washington state agency documents must meet the 2.2 AA standard.

What else informs this work

The tools we use

We apply accessible design with our most common authoring tools: Microsoft Word and Adobe Acrobat (PDF).

Back to top

What makes content accessible

Accessibility comes from how a document is built in the software, not from how it looks on the surface. Accessible content has:

Back to top

The five keys to an accessible document

Five practices turn an ordinary document into an accessible one. Each one is a section below.

  1. Provide document properties
  2. Use styles, not text tools
  3. Use only simple, accessible tables
  4. Pair accessible images with text
  5. Check color, contrast, and sensory cues

Key 1: Provide document properties

Always assign document properties. If you removed the file from the file structure, could people easily tell what it contains?

Key 2: Use styles, not text tools

Use styles to create headings

Assistive technology cannot infer meaning from bold or underlined text, or even from font size. Built-in styles let assistive tech convey text to a reader quickly and accurately.

Heading levels matter

People using screen readers can move through headings to find relevant content and return to it. Levels set the reading order.

Use styles for emphasis too

Use the Strong style instead of the bold text tool. It makes your text bold and signals to assistive tech that it is emphasized. Modify styles to match style guides, other documents, or your preferences.

Make accessible paragraphs

Add space by setting paragraph spacing, not by pressing Enter.

  1. In paragraph formatting, set Space After paragraphs to 14 pt.
  2. To start a new paragraph, press Enter just once.
  3. For a new line within a paragraph (better layout), press Shift + Enter—a soft return.

Back to top

Key 3: Use only simple, accessible tables

These steps build a table everyone can navigate, with perceivable information in every cell. You cannot make complex tables accessible in Word. “Complex” tables contain merged cells, split cells, more than one level of headers, or tables within tables.

Always take these two actions

  1. Build the table in your document—don’t paste a picture of one.
  2. Mark your headers. Use the Table Design tab and check Header Row for your top row. If your left column also labels each row, check First Column too.

Design around your data: if the data is complex, split it up. Turn one complicated table into several simple tables, each with its own clear headers.

A table must be a perfect grid

Avoid blank rows or columns

Empty rows and columns can make a screen reader think the table has ended, so it stops reading.

Avoid

A blank row before the total. A screen reader can read the empty row as the end of the table and stop before the total.

Do

No empty row. Set the total apart with a top border and shading—formatting, not blank space—so a screen reader verbalizes the whole table. The example below is built this way.

Summary of pass rates (accessible version—the total row is set apart by formatting, not a blank row)
Group Number taking assessment Number passing assessment Pass rate (%)
All program completers, Year 11,8001,74697
All program completers, Year 21,7301,730100
All program completers, Year 31,6051,605100
Total5,1355,08199

Back to top

Key 4: Pair accessible images with text

Use visuals wisely

Strong visuals make your message clearer. Build in four habits:

Insert images with built-in tools, not copy and paste

Insert > Pictures keeps the image in line with the text and lets you add real alt text. Copy and paste can lose the description or float the image out of order, and that broken order can follow into a tagged PDF when you export.

Combine related graphics into one object

If images belong together, group them into one object. Readers get one clear description instead of many pieces. For a complex chart, a few lines of alt text can’t explain everything—also give the key information as plain text nearby.

Set images to wrap “In Line with Text”

Floating or fixed images aren’t tied to the text beside them, so a screen reader can lose track of where they belong. “In line” keeps each image in the reading flow, so readers hear its alt text where it makes sense.

Avoid text boxes and images of text

Don’t trap words in a box or a picture.

Provide alt text for every image

Add alternative text to shapes, pictures, charts, SmartArt, and other objects, so a screen reader can describe what they show. Ask yourself why you used the image: if it carries meaning—including a mood or feeling—describe that meaning. If it doesn’t, mark the image decorative.

Writing great alt text

Write alt text and captions in plain language—clear, brief, and meaningful. Compare these descriptions of the same chart:

Not useful “A bar chart showing health plan enrollment from 2020 to 2026.”
Better “Enrollment in the high-deductible plan rose from 1,200 employees in 2020 to 4,500 in 2026. It’s now the most-chosen option.”

Another example, for an emissions chart:

Not useful “A bar chart showing emission levels from 1990 to 2050.”
Better “Greenhouse gas emissions peaked at 110 million metric tons in 2000; Washington’s caps aim to cut them to 5 million by 2050.”

The better version gives the reader the point of the image, not just its type.

Practice: summarize an image

A good summary is 1–3 short sentences that carry the meaning—the point a reader needs, not every detail. Aim for about 125 characters or fewer. Start from the facts in the data table, decide what matters, and say it plainly.

Two versions are below. Use the one that matches your course. Each has a visual map, the data behind it, and a prompt. Jump to Department of Ecology or Open enrollment.

Version A—Department of Ecology: county drought status

Map titled Washington Drought Declaration and Advisory. Counties across central and eastern Washington—including Okanogan, Chelan, Kittitas, Yakima, Ferry, and others—are shaded orange for Drought Emergency Declaration. A small area near Puget Sound is shaded yellow for Drought Advisory. Remaining counties are unshaded.
Practice example: a Washington State drought map. The shaded colors are paired with a written legend and described in the alt text, so the meaning does not depend on color alone. (Image for training—not real Washington data.)
View the data—drought status, all 39 counties
Washington drought status by county, grouped by region. (Training example—not real Washington data.)
County Region Drought status
ChelanCentral WashingtonDrought emergency
DouglasCentral WashingtonDrought emergency
GrantCentral WashingtonDrought emergency
KittitasCentral WashingtonDrought emergency
KlickitatCentral WashingtonDrought emergency
OkanoganCentral WashingtonDrought emergency
YakimaCentral WashingtonDrought emergency
AdamsEastern WashingtonDrought emergency
AsotinEastern WashingtonDrought emergency
BentonEastern WashingtonDrought emergency
ColumbiaEastern WashingtonDrought emergency
FerryEastern WashingtonDrought emergency
FranklinEastern WashingtonDrought emergency
GarfieldEastern WashingtonDrought emergency
LincolnEastern WashingtonDrought emergency
Pend OreilleEastern WashingtonDrought emergency
SpokaneEastern WashingtonDrought emergency
StevensEastern WashingtonDrought emergency
Walla WallaEastern WashingtonDrought emergency
WhitmanEastern WashingtonDrought emergency
KitsapWestern Washington (Puget Sound)Drought advisory
MasonWestern Washington (Puget Sound)Drought advisory
ClallamWestern Washington (Puget Sound)No declaration
ClarkWestern Washington (Puget Sound)No declaration
CowlitzWestern Washington (Puget Sound)No declaration
Grays HarborWestern Washington (Puget Sound)No declaration
IslandWestern Washington (Puget Sound)No declaration
JeffersonWestern Washington (Puget Sound)No declaration
KingWestern Washington (Puget Sound)No declaration
LewisWestern Washington (Puget Sound)No declaration
PacificWestern Washington (Puget Sound)No declaration
PierceWestern Washington (Puget Sound)No declaration
San JuanWestern Washington (Puget Sound)No declaration
SkagitWestern Washington (Puget Sound)No declaration
SkamaniaWestern Washington (Puget Sound)No declaration
SnohomishWestern Washington (Puget Sound)No declaration
ThurstonWestern Washington (Puget Sound)No declaration
WahkiakumWestern Washington (Puget Sound)No declaration
WhatcomWestern Washington (Puget Sound)No declaration

Write your summary of the drought map, using the data above as your source. Ask yourself: what is the overall picture, and is there an exception worth naming?

Version B—Open enrollment: health plan by county

Map titled Statewide Health Plan Enrollment by County. Most of Washington's 39 counties are shaded orange, where a Value HMO is the majority plan. Eleven counties are shaded blue for a Standard PPO majority: a Puget Sound cluster of Whatcom, Skagit, Snohomish, Island, Kitsap, King, Pierce and Thurston, plus Clark in the southwest and Benton and Spokane in the east. The colors are paired with a written legend, so meaning does not depend on color alone.
Practice example: a Washington State health plan enrollment map. The two plan colors are paired with a written legend and described in the alt text, so the meaning does not depend on color alone. (Image for training—not real Washington data.)
View the data—health plan by county, all 39 counties
Majority health plan by Washington county, grouped by region. (Training example—not real Washington data.)
County Region Majority plan
ChelanCentral WashingtonValue HMO
DouglasCentral WashingtonValue HMO
GrantCentral WashingtonValue HMO
KittitasCentral WashingtonValue HMO
KlickitatCentral WashingtonValue HMO
OkanoganCentral WashingtonValue HMO
YakimaCentral WashingtonValue HMO
AdamsEastern WashingtonValue HMO
AsotinEastern WashingtonValue HMO
BentonEastern WashingtonStandard PPO
ColumbiaEastern WashingtonValue HMO
FerryEastern WashingtonValue HMO
FranklinEastern WashingtonValue HMO
GarfieldEastern WashingtonValue HMO
LincolnEastern WashingtonValue HMO
Pend OreilleEastern WashingtonValue HMO
SpokaneEastern WashingtonStandard PPO
StevensEastern WashingtonValue HMO
Walla WallaEastern WashingtonValue HMO
WhitmanEastern WashingtonValue HMO
ClallamWestern Washington (Puget Sound)Value HMO
ClarkWestern Washington (Puget Sound)Standard PPO
CowlitzWestern Washington (Puget Sound)Value HMO
Grays HarborWestern Washington (Puget Sound)Value HMO
IslandWestern Washington (Puget Sound)Standard PPO
JeffersonWestern Washington (Puget Sound)Value HMO
KingWestern Washington (Puget Sound)Standard PPO
KitsapWestern Washington (Puget Sound)Standard PPO
LewisWestern Washington (Puget Sound)Value HMO
MasonWestern Washington (Puget Sound)Value HMO
PacificWestern Washington (Puget Sound)Value HMO
PierceWestern Washington (Puget Sound)Standard PPO
San JuanWestern Washington (Puget Sound)Value HMO
SkagitWestern Washington (Puget Sound)Standard PPO
SkamaniaWestern Washington (Puget Sound)Value HMO
SnohomishWestern Washington (Puget Sound)Standard PPO
ThurstonWestern Washington (Puget Sound)Standard PPO
WahkiakumWestern Washington (Puget Sound)Value HMO
WhatcomWestern Washington (Puget Sound)Standard PPO

Write your summary of the enrollment map, using the data above as your source. Ask yourself: what is the overall picture, and is there an exception worth naming?

Working from an image you can’t see? That’s normal practice, not a workaround. People who can’t see an image get its contents from a colleague, from the source data, or from an image-description tool, and then apply their own judgment to write the description. The judgment—deciding what matters and saying it well—is the real skill, and it’s the same for everyone. Here, the table is your source data.

The pattern to copy: when a graphic carries this much data, pair it with the data itself. The image gives the gist; the table gives the full detail. Both are great ways to read the same facts—neither one is an extra or an afterthought.

Adding alt text in Word

  1. Right-click the image.
  2. Select “View Alt Text” from the menu.
  3. In the Alt Text pane, write 1–3 short sentences that describe the image in a useful, brief way.

Back to top

Key 5: Check color, contrast, and sensory cues

Color and sensory cues

For all users, for all use of color:

Ensure strong contrast between text and background

Check every text-and-background pairing with a free, easy contrast checker. Sentient Learning made one aligned to your standards: Sentient Learning color and contrast checker (sentient-learning.com/color-contrast-checker). Aim for at least 4.5:1 for normal text and 3:1 for large text.

A word of warning: areas of silence

Vital elements never go in watermarks, headers, or footers. Assistive technology can pass over those areas, so anything essential—including classification and distribution authorization—must live in the main content.

Back to top

Check your document

Use the Accessibility Checker. It verifies your file against a set of rules that identify possible issues for people who have disabilities, and it classifies each issue as an error, a warning, or a tip.

Preparing for PDF conversion

Clean up the file

Acrobat settings

Select the Acrobat tab in the top menu bar, then choose Preferences. Under Application Settings, turn on these options:

Back to top

Reading order and the tag tree

A screen reader performs your PDF like a script—top to bottom, one tag at a time. The tag tree is that script.

Understanding the tag tree

When you export to PDF, each element becomes a tag:

How document elements become Adobe Acrobat tags
ElementAdobe Acrobat tag
Heading 1<H1>
Heading 2<H2>
Heading 3<H3>
Paragraph text<P>
Image or non-text content<Figure>
Table<Table>
Table row<TR>
Table header cell<TH>
Table data cell<TD>
List<L>
List item<LI>

Check the reading order

If it’s not in the tag tree, it doesn’t exist. To review:

  1. Press the down arrow to move through the tag tree. A fuchsia box frames each tagged item.
  2. Ask: does the content flow in the order you intended?
  3. If not, reorder it so assistive technology moves through correctly.

Try it in Acrobat

Open the file, walk the tag tree, and run Acrobat’s built-in Accessibility Check.

Back to top

Great work—share your feedback

Please share your thoughts. Open your course evaluation link in the chat, or from the Learning Center home page go to: SELF > Learning > Learning Activity Evaluations.

Back to top