Difference between revisions of "Accessible Word Documents"

From Help Wiki
Line 1: Line 1:
{{TwoColumn|lead=
+
 
Best Practices for Creating Accessible Word Documents and Google Docs  
+
<div class="container-fluid">
|content=
+
<div class="row">
 +
<div class="col-md-8">
 +
<div class="lead">
 +
Best Practices for Creating Accessible Word Documents and Google Docs
 +
</div>
 +
 
 
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.
 
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.
  
Line 13: Line 18:
  
 
*'''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>
|sidebar=
+
 
 +
 
 +
<!-- end col-md-8 -->
 +
</div>
 +
<div class="col-md-1"></div>
 +
<div class="col-md-3 sidebar">
 
====Accessibility Reasorces====
 
====Accessibility Reasorces====
 
*[https://www.evergreen.edu/accessibility Evergreen's Guide on Accessible Technology ]
 
*[https://www.evergreen.edu/accessibility Evergreen's Guide on Accessible Technology ]
Line 31: Line 41:
 
----
 
----
 
{{GetHelp}}
 
{{GetHelp}}
}}
+
 
 +
<!-- end col-md-3-->
 +
</div>
 +
<!-- end row-->
 +
</div>
 +
<!-- end container-->
 +
</div>
 +
<!-- Generator=Template:TwoColumn -->
 +
__NOTOC__
 +
__NOEDITSECTION__
  
 
[[Category:Accessibility]]
 
[[Category:Accessibility]]

Revision as of 15:13, 30 September 2017

Best Practices for Creating Accessible Word Documents and Google Docs

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.

Several guidelines to follow:

  • 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 designate the form a letter.
  • 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.