Stay organized with collections
Save and categorize content based on your preferences.
Technical Writing for Accessibility focused on the following ideas:
Accessibility in documentation benefits
people with permanent, temporary, or situational disabilities.
Every image requires an alt text element. Alt text acts as a functional
equivalent for an image by providing a concise summary of the image's purpose
and context.
Sufficient color contrast helps readers with color blindness or low vision.
Write for a broad spectrum of readers.
Avoid relying only on visual indicators, such as colors or patterns, to
communicate important information.
Practice editing for accessibility to ensure proper heading structure,
descriptive link text, and clear language.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-04-17 UTC."],[],["Documentation accessibility benefits all users, especially those with disabilities. Key actions include providing alt text for every image, which describes its purpose. Writers should ensure sufficient color contrast and avoid relying solely on visual cues. Inclusive language is necessary to reach a wider audience. Editing should enforce proper heading structures, descriptive link text, and clarity. The linked guidelines offer further resources on creating accessible documentation.\n"]]
