Difference between revisions of "Accessible Word Documents"
From Help Wiki
(4 intermediate revisions by one other user not shown) | |||
Line 1: | Line 1: | ||
− | |||
− | |||
− | |||
− | |||
− | === | + | <div class="container-fluid"> |
+ | <div class="row"> | ||
+ | <div class="col-md-8"> | ||
+ | <div class="lead"> | ||
+ | Best Practices for Creating Accessible Word Documents | ||
+ | </div> | ||
+ | |||
+ | ===Microsoft Guide=== | ||
+ | *[https://support.microsoft.com/en-us/office/make-your-word-documents-accessible-to-people-with-disabilities-d9bf3683-87ac-47ea-b91a-78dcacb3c66d Make your Word documents accessible to people with disabilities] | ||
+ | |||
+ | === General Guidelines for Making Content Available to Screen Readers=== | ||
+ | There are a variety of adaptive technology software options that rely on optical character recognition ([[Optical Character Recognition|OCR]]) techniques in order to convert text to audio. Basic OCR programs are limited in their ability to “read” text so the structure of your document can make all the difference in making your content accessible and readable by text-to-speech tools. | ||
*'''Structure''' – Simple screen readers scan text left to right and top to bottom; making your document hierarchical and linear can ensure the text you include makes sense to someone using a screen reader. | *'''Structure''' – Simple screen readers scan text left to right and top to bottom; making your document hierarchical and linear can ensure the text you include makes sense to someone using a screen reader. | ||
− | *'''Typeface''' – The typeface you use in your document can aid readers with visual impairments. Use standard fonts, particularly fonts without serifs (sans serif) to help | + | *'''Typeface''' – The typeface you use in your document can aid readers with visual impairments. Use standard fonts, particularly fonts without serifs (sans serif) to help better distinguish between different letters of the alphabet. |
*'''Conveying emphasis''' – Proper punctuation can help you convey emphasis in the text if you know how it is interpreted. Screen readers provide a brief pause at commas and a longer pause at periods. You may want to include periods at the end of section headers to convey the start of a new section. Screen readers generally don’t read hyphens and parentheses so you may want to use commas in lieu of other punctuation marks. | *'''Conveying emphasis''' – Proper punctuation can help you convey emphasis in the text if you know how it is interpreted. Screen readers provide a brief pause at commas and a longer pause at periods. You may want to include periods at the end of section headers to convey the start of a new section. Screen readers generally don’t read hyphens and parentheses so you may want to use commas in lieu of other punctuation marks. | ||
*'''Templates and Formatting''' – Some screen readers are quite advanced and make use of Word templates. Using a template and the formatting options already built into Word can make your work easier and more accessible for your audience.<br> <br> | *'''Templates and Formatting''' – Some screen readers are quite advanced and make use of Word templates. Using a template and the formatting options already built into Word can make your work easier and more accessible for your audience.<br> <br> | ||
− | + | ||
− | === | + | === Additional Resources === |
− | *[https:// | + | *[[Accessibility Checklist]] |
− | + | * [https://canvas.evergreen.edu/courses/5890 Self-enroll to the Accessibility Micro-Courses] | |
− | + | ||
− | + | ||
− | + | <!-- end col-md-8 --> | |
− | + | </div> | |
− | + | <div class="col-md-1"></div> | |
− | = | + | <div class="col-md-3 sidebar"> |
− | + | {{AccessibilityResources}} | |
− | + | {{CreatingAccessibleContent}} | |
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
---- | ---- | ||
{{GetHelp}} | {{GetHelp}} | ||
− | + | ||
+ | <!-- end col-md-3--> | ||
+ | </div> | ||
+ | <!-- end row--> | ||
+ | </div> | ||
+ | <!-- end container--> | ||
+ | </div> | ||
+ | <!-- Generator=Template:TwoColumn --> | ||
+ | __NOTOC__ | ||
+ | __NOEDITSECTION__ | ||
[[Category:Accessibility]] | [[Category:Accessibility]] |
Latest revision as of 15:10, 22 December 2023
Best Practices for Creating Accessible Word Documents
Microsoft Guide
General Guidelines for Making Content Available to Screen Readers
There are a variety of adaptive technology software options that rely on optical character recognition (OCR) techniques in order to convert text to audio. Basic OCR programs are limited in their ability to “read” text so the structure of your document can make all the difference in making your content accessible and readable by text-to-speech tools.
- Structure – Simple screen readers scan text left to right and top to bottom; making your document hierarchical and linear can ensure the text you include makes sense to someone using a screen reader.
- Typeface – The typeface you use in your document can aid readers with visual impairments. Use standard fonts, particularly fonts without serifs (sans serif) to help better distinguish between different letters of the alphabet.
- Conveying emphasis – Proper punctuation can help you convey emphasis in the text if you know how it is interpreted. Screen readers provide a brief pause at commas and a longer pause at periods. You may want to include periods at the end of section headers to convey the start of a new section. Screen readers generally don’t read hyphens and parentheses so you may want to use commas in lieu of other punctuation marks.
- Templates and Formatting – Some screen readers are quite advanced and make use of Word templates. Using a template and the formatting options already built into Word can make your work easier and more accessible for your audience.
Additional Resources