Difference between revisions of "Digital Content Accessibility"

From AccessGA Wiki
Jump to navigation Jump to search
Line 14: Line 14:
 
= <span style="font-size:medium"><span style="font-family: tahoma,geneva,sans-serif">Principles</span></span><br/> =
 
= <span style="font-size:medium"><span style="font-family: tahoma,geneva,sans-serif">Principles</span></span><br/> =
  
<u><span style="font-family:tahoma,geneva,sans-serif"><span style="font-size:small">'''Documents'''</span></span></u>
+
<u><span style="font-family:tahoma,geneva,sans-serif"><span style="font-size:small">'''MS Word Documents'''</span></span></u>
  
*<span style="font-family:tahoma,geneva,sans-serif"><span style="font-size: small">Have means of navigation (has headings, bookmarks, etc.)</span></span>
+
*Provide document structure by using appropriate headings (&lt;h1&gt;, &lt;h2&gt;, &lt;h3&gt;). Screen readers rely on document structure for navigation.
 
*<span style="font-family:tahoma,geneva,sans-serif"><span style="font-size: small">Read in a logical order</span></span>
 
*<span style="font-family:tahoma,geneva,sans-serif"><span style="font-size: small">Read in a logical order</span></span>
 
*Contain text rather than scanned image (i.e. scanned documents)
 
*Contain text rather than scanned image (i.e. scanned documents)
Line 25: Line 25:
 
*<span style="font-family:tahoma,geneva,sans-serif"><span style="font-size: small">Provide accurate metadata in document properties</span></span>
 
*<span style="font-family:tahoma,geneva,sans-serif"><span style="font-size: small">Provide accurate metadata in document properties</span></span>
  
<u><span style="font-family:tahoma,geneva,sans-serif">'''PowerPoints'''</span></u>
+
<u><span style="font-family:tahoma,geneva,sans-serif">'''PowerPoint'''</span></u>
  
*Apply document structure
 
 
*Use built in templates
 
*Use built in templates
 
*Text on solid background, not over an image
 
*Text on solid background, not over an image
Line 41: Line 40:
 
*<span style="font-family:tahoma,geneva,sans-serif"><span style="font-size:small">Do not use color as sole meaning of communication (ex:error messages)</span></span>
 
*<span style="font-family:tahoma,geneva,sans-serif"><span style="font-size:small">Do not use color as sole meaning of communication (ex:error messages)</span></span>
 
*<span style="font-family:tahoma,geneva,sans-serif"><span style="font-size:small">Fonts are easy to read</span></span>
 
*<span style="font-family:tahoma,geneva,sans-serif"><span style="font-size:small">Fonts are easy to read</span></span>
*<span style="font-family:tahoma,geneva,sans-serif"><span style="font-size:small">PDF files need to be texts not images</span></span>
+
*<span style="font-family:tahoma,geneva,sans-serif"><span style="font-size:small">PDF files need to be text not images</span></span>
  
 
<span style="font-family:tahoma,geneva,sans-serif"><span style="font-size:small">'''<u>Excel</u>'''</span></span>
 
<span style="font-family:tahoma,geneva,sans-serif"><span style="font-size:small">'''<u>Excel</u>'''</span></span>
Line 51: Line 50:
  
 
*<span style="font-family:tahoma,geneva,sans-serif"><span style="font-size:small">Add tags to PDFs to create document structure and provide logical reading order</span></span>
 
*<span style="font-family:tahoma,geneva,sans-serif"><span style="font-size:small">Add tags to PDFs to create document structure and provide logical reading order</span></span>
*<span style="font-family:tahoma,geneva,sans-serif"><span style="font-size:small">Add alternative text to all meaningful images in your document, which describes the image to someone who cannot see it</span></span>
+
*<span style="font-family:tahoma,geneva,sans-serif"><span style="font-size:small">Add alternative text to all meaningful images in your document</span></span>
 
*<span style="font-family:tahoma,geneva,sans-serif"><span style="font-size:small">Add bookmarks to increase the navigability of the document</span></span>
 
*<span style="font-family:tahoma,geneva,sans-serif"><span style="font-size:small">Add bookmarks to increase the navigability of the document</span></span>
 
*<span style="font-family:tahoma,geneva,sans-serif"><span style="font-size:small">Add appropriate metadata, such as title/author in the advanced properties of your document</span></span>
 
*<span style="font-family:tahoma,geneva,sans-serif"><span style="font-size:small">Add appropriate metadata, such as title/author in the advanced properties of your document</span></span>

Revision as of 15:36, 12 December 2013

About

Content or Document Accessibility refers to documents saved in common file formats, posted to websites or distributed through email, and the need to provide them in an accessible format. Documents designed using accessibility standards and guidelines are beneficial for all users. Accessibility considerations include: document structure, navigation, alternative text descriptions, logical reading order and adequate labels.

Digital content accessibility guidelines are very similar to the guidelines and standards for ensuring web content is accessible, however, the techniques to achieve accessibility will vary depending on the format of the document.

The most common file formats posted on websites and used for sharing and disseminating information are:

  • Microsoft Word .docx
  • Adobe .pdf
  • Mircosoft PowerPoint .pptx
  • Microsoft Excel .xls

Principles

MS Word Documents

  • Provide document structure by using appropriate headings (<h1>, <h2>, <h3>). Screen readers rely on document structure for navigation.
  • Read in a logical order
  • Contain text rather than scanned image (i.e. scanned documents)
  • Have file security disabled
  • Contain images, charts and graphs described using alternative text
  • Contain form fields with appropriate labels to tab through the form fields in the correct order
  • Use meaningful hyperlink text
  • Provide accurate metadata in document properties

PowerPoint

  • Use built in templates
  • Text on solid background, not over an image
  • No flash animations (flash is more than 3x/second)
  • Headers must be checked when creating tables
  • Tab through slide to check order of floating objects
  • Make sure all key information is viewable in the outline format

General

  • Labels to forms
  • Color contrast between text and background colors
  • Do not use color as sole meaning of communication (ex:error messages)
  • Fonts are easy to read
  • PDF files need to be text not images

Excel

  • Alt-text summary information
  • Specificy collumn header information

PDF

  • Add tags to PDFs to create document structure and provide logical reading order
  • Add alternative text to all meaningful images in your document
  • Add bookmarks to increase the navigability of the document
  • Add appropriate metadata, such as title/author in the advanced properties of your document

Resources

Create Accessible Word Documents from Microsoft

Create Accessible Word Documents from WebAIM

Microsoft Word "Cheat Sheet"

Create Accessible pdfs from word documents

Acrobat X Pro best practices for PDF accessibility

Microsoft PowerPoint 2007/2010 (PC)

PowerPoint Accessibility Checklist from HHS.gov

JAWS Forms Mode

Accessible PDF Forms HHS.gov

Creating Accessible Excel workbooks

GSA 508 Tutorials, Guidance, Checklists

Recommendations