Public

Resources for Accessible Writing

Link to this doc: goo.gle/accessible-content

Collected by these Googlers:

• Alexandra White, technical writer for the Privacy Sandbox
• Darcy Lima, technical writer for accessibility at Google
• Gwen McLean, UX writer for Google AdMob

Welcome, content creators! If your title says “writer” or you write any content as a part of your job, this collection of resources is for you. These resources are from our videos on accessible writing, with some additional context.

For courses on accessible writing, check out the W3C’s course list for an audience of content authors.

Use inclusive language

When considering how to write and speak with inclusive language, there are words we should use and language to avoid. Language to avoid may sound awkward at best or at worst, be harmful and offensive. Language changes all the time, and these materials will change too, as norms and best practices evolve.

Writing inclusive language in our docs starts with realizing the ways in which we’ve internalized ableism in our everyday lives.

Watch the video about inclusive language, or read the transcript.

Google developer documentation style guide:

• Write inclusive documentation
• Write for a global audience

Other writing guides:

• National Center on Disability and Journalism style guide
• Gender-inclusive language from the University of North Carolina Writing Center
• Guide from the National Association of Black Journalists
• GLAAD media reference guide

Reduce visual cues

Don't rely solely on visual elements to convey information. Always use text or alt text along with visual elements, such as colors, patterns, images, font styles, and directional language.

Watch the video about reducing visual cues, or read the transcript.

From W3C:

• Avoid sensory characteristics
• Use color as one of many elements to communicate

Informative, semantic titles & headings

Heading language should be scannable and understood without context. Additionally, it’s important to use semantic HTML, which means the HTML tags you choose correctly align with the value of the content between the tags.

Watch the video about headings, or read the transcript.

From W3C:

• Semantic HTML guide

Write clear instructions

Clear instructions are the most critical element of a technical writer’s job. We recommend you write short, complete sentences; use precise language; use exact measurements; and use nouns instead of pronouns. Additionally, we recommend that you break up longer tasks into smaller chunks and share examples.

For UI copy, clear instructions mean the user can always answer 3 questions: where am I? What can I do here? How do I move forward?

Watch the video about clear instructions, or read the transcript.

Google developer documentation style guide:

• Write accessible documentation
• Avoid excessive claims

Other writing guides:

• UI Copy: UX Guidelines for Command Names and Keyboard Shortcuts by the Nielsen Norman Group

Book:

• Don’t make me think, revisited by Steve Krug

Be clear & concise

Clear, simple text lets your audience focus on learning or completing a task, rather than deciphering what you're trying to say.

Watch the video about clear and concise text, or read the transcript.

Write with fewer words:

• Guide to using fewer words by Alexandra White
• How to say more with fewer words by Jon Hawkins
• Why Small Words Matter: The Importance of Microcopy UX from Toptal