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:
- What can we do to help all people easily find, understand, and use what we write?
- What design decisions and authoring actions create a good experience for people who read what we write?
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:
- Equitable.
- Flexible.
- Simple and intuitive.
- Perceptible.
- Tolerant of error.
- Low in physical effort.
- Considerate of size and space for approach and use.
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
- Wisdom from user communities. Insight from users, lived experiences, and case studies helps us create good customer experiences beyond the standard.
- Plain language principles of layout and design. This course builds skill in plain language information design from a more technical base, so people can find, understand, and use what they need.
The tools we use
We apply accessible design with our most common authoring tools: Microsoft Word and Adobe Acrobat (PDF).
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:
- Properties assigned in the software.
- Structure that comes from the software, not from visual design.
- Reading order determined by tags and elements, not by visual cues.
- True tables, headings, and subheadings.
- True text—not images of text.
- Alternative text for every image.
- Plain language captions for every image.
The five keys to an accessible document
Five practices turn an ordinary document into an accessible one. Each one is a section below.
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?
- Make it easy for people to find what they need.
- Save the file with a descriptive name to identify it among many and make its purpose clear.
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
- Your title is Heading 1 (H1), or the Title style.
- Every major heading is Heading 2 (H2).
- You can create true subheadings for subsections: Heading 3 nests under Heading 2, and so on.
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.
- In paragraph formatting, set Space After paragraphs to 14 pt.
- To start a new paragraph, press Enter just once.
- For a new line within a paragraph (better layout), press Shift + Enter—a soft return.
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
- Build the table in your document—don’t paste a picture of one.
- 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
- Every row has the same number of cells.
- Every column has the same number of cells.
- Every cell has data—no empty cells.
Avoid blank rows or columns
Empty rows and columns can make a screen reader think the table has ended, so it stops reading.
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.
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.
| Group | Number taking assessment | Number passing assessment | Pass rate (%) |
|---|---|---|---|
| All program completers, Year 1 | 1,800 | 1,746 | 97 |
| All program completers, Year 2 | 1,730 | 1,730 | 100 |
| All program completers, Year 3 | 1,605 | 1,605 | 100 |
| Total | 5,135 | 5,081 | 99 |
Key 4: Pair accessible images with text
Use visuals wisely
Strong visuals make your message clearer. Build in four habits:
- Use it with purpose. Every visual should make a point clearer, not just fill space.
- Keep it simple. Remove clutter so the main message stands out.
- Don’t rely on color alone. Pair color with labels, shapes, or text.
- Add alt text. Describe each image so screen readers can share it.
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.
- Images of text: the words won’t be read aloud, resize cleanly, or show up in a search.
- Text boxes: they float above the text layer, so a screen reader reads right past them. For callouts and labels, set off normal text with borders and shading instead.
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
View the data—drought status, all 39 counties
| County | Region | Drought status |
|---|---|---|
| Chelan | Central Washington | Drought emergency |
| Douglas | Central Washington | Drought emergency |
| Grant | Central Washington | Drought emergency |
| Kittitas | Central Washington | Drought emergency |
| Klickitat | Central Washington | Drought emergency |
| Okanogan | Central Washington | Drought emergency |
| Yakima | Central Washington | Drought emergency |
| Adams | Eastern Washington | Drought emergency |
| Asotin | Eastern Washington | Drought emergency |
| Benton | Eastern Washington | Drought emergency |
| Columbia | Eastern Washington | Drought emergency |
| Ferry | Eastern Washington | Drought emergency |
| Franklin | Eastern Washington | Drought emergency |
| Garfield | Eastern Washington | Drought emergency |
| Lincoln | Eastern Washington | Drought emergency |
| Pend Oreille | Eastern Washington | Drought emergency |
| Spokane | Eastern Washington | Drought emergency |
| Stevens | Eastern Washington | Drought emergency |
| Walla Walla | Eastern Washington | Drought emergency |
| Whitman | Eastern Washington | Drought emergency |
| Kitsap | Western Washington (Puget Sound) | Drought advisory |
| Mason | Western Washington (Puget Sound) | Drought advisory |
| Clallam | Western Washington (Puget Sound) | No declaration |
| Clark | Western Washington (Puget Sound) | No declaration |
| Cowlitz | Western Washington (Puget Sound) | No declaration |
| Grays Harbor | Western Washington (Puget Sound) | No declaration |
| Island | Western Washington (Puget Sound) | No declaration |
| Jefferson | Western Washington (Puget Sound) | No declaration |
| King | Western Washington (Puget Sound) | No declaration |
| Lewis | Western Washington (Puget Sound) | No declaration |
| Pacific | Western Washington (Puget Sound) | No declaration |
| Pierce | Western Washington (Puget Sound) | No declaration |
| San Juan | Western Washington (Puget Sound) | No declaration |
| Skagit | Western Washington (Puget Sound) | No declaration |
| Skamania | Western Washington (Puget Sound) | No declaration |
| Snohomish | Western Washington (Puget Sound) | No declaration |
| Thurston | Western Washington (Puget Sound) | No declaration |
| Wahkiakum | Western Washington (Puget Sound) | No declaration |
| Whatcom | Western 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
View the data—health plan by county, all 39 counties
| County | Region | Majority plan |
|---|---|---|
| Chelan | Central Washington | Value HMO |
| Douglas | Central Washington | Value HMO |
| Grant | Central Washington | Value HMO |
| Kittitas | Central Washington | Value HMO |
| Klickitat | Central Washington | Value HMO |
| Okanogan | Central Washington | Value HMO |
| Yakima | Central Washington | Value HMO |
| Adams | Eastern Washington | Value HMO |
| Asotin | Eastern Washington | Value HMO |
| Benton | Eastern Washington | Standard PPO |
| Columbia | Eastern Washington | Value HMO |
| Ferry | Eastern Washington | Value HMO |
| Franklin | Eastern Washington | Value HMO |
| Garfield | Eastern Washington | Value HMO |
| Lincoln | Eastern Washington | Value HMO |
| Pend Oreille | Eastern Washington | Value HMO |
| Spokane | Eastern Washington | Standard PPO |
| Stevens | Eastern Washington | Value HMO |
| Walla Walla | Eastern Washington | Value HMO |
| Whitman | Eastern Washington | Value HMO |
| Clallam | Western Washington (Puget Sound) | Value HMO |
| Clark | Western Washington (Puget Sound) | Standard PPO |
| Cowlitz | Western Washington (Puget Sound) | Value HMO |
| Grays Harbor | Western Washington (Puget Sound) | Value HMO |
| Island | Western Washington (Puget Sound) | Standard PPO |
| Jefferson | Western Washington (Puget Sound) | Value HMO |
| King | Western Washington (Puget Sound) | Standard PPO |
| Kitsap | Western Washington (Puget Sound) | Standard PPO |
| Lewis | Western Washington (Puget Sound) | Value HMO |
| Mason | Western Washington (Puget Sound) | Value HMO |
| Pacific | Western Washington (Puget Sound) | Value HMO |
| Pierce | Western Washington (Puget Sound) | Standard PPO |
| San Juan | Western Washington (Puget Sound) | Value HMO |
| Skagit | Western Washington (Puget Sound) | Standard PPO |
| Skamania | Western Washington (Puget Sound) | Value HMO |
| Snohomish | Western Washington (Puget Sound) | Standard PPO |
| Thurston | Western Washington (Puget Sound) | Standard PPO |
| Wahkiakum | Western Washington (Puget Sound) | Value HMO |
| Whatcom | Western 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
- Right-click the image.
- Select “View Alt Text” from the menu.
- In the Alt Text pane, write 1–3 short sentences that describe the image in a useful, brief way.
Key 5: Check color, contrast, and sensory cues
Color and sensory cues
For all users, for all use of color:
- Never rely on color to convey meaning. Duplicate the meaning with words.
- Symbols may reinforce the words but should never stand alone to convey meaning.
- Check all warnings and danger notices—anything that could lead to harm or loss if missed.
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.
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
- Accept all edits. Select the Accept icon, then Accept All Changes and Stop Tracking from the drop-down menu.
- Turn Track Changes off. Select the Track Changes icon to see whether it’s on or off; if it’s on, select it again to turn it off.
- Remove all comments. In the comments section, select the drop-down arrow under the Delete icon and choose Delete All Comments in Document.
Acrobat settings
Select the Acrobat tab in the top menu bar, then choose Preferences. Under Application Settings, turn on these options:
- Create Bookmarks.
- Add Links.
- Enable Accessibility and Reflow with Tagged Adobe PDF.
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:
| Element | Adobe 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:
- Press the down arrow to move through the tag tree. A fuchsia box frames each tagged item.
- Ask: does the content flow in the order you intended?
- 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.
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.