Technology and information are considered to be accessible if it can be accessed in a variety of ways and does not rely on a single sense or ability of the user. For higher education, major accessibility issues fall into three broad areas: web-based learning, in-class technology, and document preparation.
Websites and learning management systems have a variety of content including web pages, learning management system courses, text files in various formats (Word, PDF, Excel, PowerPoint) and audio/video recordings. Each of these content formats are usually developed by faculty or gathered from other sources by faculty to be used in courses.
The key to developing accessible content is to understand the obstacles to accessibility and how simple changes can make content accessible. Incorporating rules at the beginning of new content development is highly recommended to save time. However, there is a large amount of existing content that is available through the university web site and through the learning management system Blackboard. As such, all content that will be accessed by the public or accessed by students must be reviewed for accessibility issues.
This publication, The Athens State University Accessible Technology and Information Guide has been developed to provide a structured set of resources to raise awareness and understanding about the basic practices that make content accessible. This guide relies on references to other resources to provide relevant, up-to-date information and techniques. There is an abundance of assistance through Internet and in software applications such as Microsoft Office. Training opportunities, both in person and online, will also be made available.
WCAG 2.0 Guidelines have been adopted as a standard for making technology and information accessible. These guidelines cover the four principles of accessible content: perceivable, operational, understandable, and robust that should be applied when developing digital content accessed through a web interface or a standalone computer.
The four principles are described in detail in twelve general guidelines listed below:
1. Perceivable – Web content must be perceivable through more than one sense.
1.1. Provide text alternatives for any non-text content so that it can be changed into other forms people need, such as large print, braille, speech, symbols or simpler language.
1.2. Provide alternatives for time-based media.
1.3. Create content that can be presented in different ways (for example simpler layout) without losing information or structure.
1.4. Make it easier for users to see and hear content including separating foreground from background.
2. Operable – The user interface should be navigable using alternative hardware. Example, have both mouse and keyboard functions.
2.1. Make all functionality available from a keyboard.
2.2. Provide users enough time to read and use content.
2.3. Do not design content in a way that is known to cause seizures.
2.4. Provide ways to help users navigate, find content, and determine where they are.
3. Understandable – Make it understandable by using alternative or supplemental representations of information. Example, supplement text with video, audio, illustrations. Likewise, text in the form of a transcript or closed captions can be added to videos.
3.1. Make text content readable and understandable.
3.2. Make Web pages appear and operate in predictable ways.
3.3. Help users avoid and correct mistakes.
4. Robust – Use consistent and accurate coding so that assistive technologies will work.
4.1. Maximize compatibility with current and future user agents, including assistive technologies.
These accessibility rules apply to all online content. Microsoft Office has a number of features to support the development of accessible content.
|Use Style elements in a hierarchical manner.||Why: Assistive Technology such as screen readers can better determine the difference between sections.|
Examples: Heading 1, Title, Emphasis, Outline, etc.
How: Select the text to format and then click the Home tab. Choose the style from the Styles gallery.
|No flashing, flickering and/or animated text.||Why: Flashing or flickering content can cause seizures and the Assistive Technology cannot decipher the content. Watch for use in Banner course banners.|
|Page number must be created by a Microsoft Word process and not manually entered.||Why: Properly formatted page numbers allow assistive technology can identify the page number.|
How: To add page numbers to a document click the Insert tab, then click the Page Number button in the Header & Footer group.
|Footnotes must be created through Word Footnote tool.||Why: Assistive technology recognizes formal footnotes and works them into the body of the text when reading.|
How: To create a footnote click on the References tab, then click the Insert Footnote button located in the Footnotes group.
|Bullet and numbering styles must be used as opposed to manually typed characters such as hyphens or dashes.||Why: Assistive Technology recognizes these items as lists of information and will navigate them accordingly.|
How: Add bullets or numbers by choosing the Home tab, then select the Bullets or Numbering button in the Paragraph group.
|Track changes need to be accepted or rejected and then turned off||Why: Assistive Technology cannot consistently read them.|
How: Turn off track changes in Review tab, and click the Track Changes button in the Tracking group.
|Comments and formatting marks must be turned off||Why: Assistive Technology cannot consistently read comments and formatting marks. They get in the way of the intended message within the content.|
How: To remove Comments select the Review tab. Click the Delete button within the Comments group. You will have the choice to delete comments and markups on the current slide or to the entire presentation.
|Final visual document checks need to be in the Print Preview.||Why: This will show items such as headers, footers, page numbers, and repeating table heading rows.|
How: To view a document click the File tab, and then choose Print. The preview will display in the right panel of the Word window.
|All URLs must contain the correct hyperlink and display the fully qualified URL.||Why: Assistive Technology recognizes formal hyperlinks and it helps the impaired users to navigate to the linked destination.|
|All the URL’s must be active and linked to the correct destination.||Why: Assistive Technology recognizes formal hyperlinks and it helps the impaired users to navigate to the linked destination.|
|Complex images must have descriptive text immediately after the image.||Why: The descriptive text is read by the Assistive Technology and provides the impaired individual additional information regarding the image.|
|The document must be free of background images or watermarks.||Why: Documents for visually impaired individuals are easier to read when they are free of background images or watermarks.|
How: To remove a watermark, click the Page Layout tab. Select Watermark from the Page Background group, then Remove Watermark.
|The image text wrapping style “In Line with Text” must be used for all images.||Why: Assistive Technology reads documents in a sequential order, if the image is not “In Line with Text” the image will be read out of order.|
How: To make an image “In Line with Text”, right-click the image. Choose Wrap Text from the drop down menu, and then select In Line with Text.
|Multiple associated images must be Grouped as One Object (i.e., Organizational Charts)||Why: When the images are grouped as one object, only one alt-tag needs to be applied to the non-verbal element.|
|All multi-layered objects must be flattened into one image and use one Alternative Text (Alt Tag) for the image.||Why: When multi-layered objects are flattened into one image, only one alt-tag needs to be applied to the non-verbal element.|
|Text boxes must not be used for simple graphics.||Why: Text boxes without content presents confusion to someone using a screen reader because the reader expects something to read.|
|All tables must read from left to right, top to bottom.||Why: This is for proper reading order by the Assistive Technology|
How: Plan table content layout so that it reads left to right, top to bottom.
|Tables containing ‘data’ must have the first row designated as a Header Row.||Why: This aids assistive technology to identify the location of the heading information for each column.|
How: To designate the heading row(s), select the rows that contain the heading information. Right-click the selected rows and choose Table Properties. In the Table Properties dialog box select the Row tab and check “Repeat as header row at the top of each page”.
|Tables must not use merged cells.||Why: Assistive technology cannot match the cells with the appropriate heading rows.|
How: Don’t merge cells
|Rows should not break across pages.||Why: It makes it difficult for Assistive Technology to read.|
How: To stop rows from breaking select the rows that contains the heading information. Right-click the selected rows and choose Table Properties. In the Table Properties dialog box select the Row tab and uncheck “Allow row to break across pages.”
Additional Accessible Documents Requirements
|The Inspect Document function will check your document for hidden information, comments, track changes, headers, footers, watermarks, and other items.||How: To run the Inspect Document select the File tab. Choose Check for Issues, Check Accessibility. Note: it is good practice to run the Inspect Document on a copy of the file, preserving the original in case there are issues.|
|The document file name must not contain spaces and/or special characters.||To separate words in a file name use the hyphen (-).|
|The document file name must be concise, generally limited to 20-30 characters.||File name should make it clear the content of the file clear in the context in which it is presented.|
|The document must utilize the recommended fonts.||Recommended fonts: Times New Roman, Verdana, Arial, Tahoma, Helvetica and Calibri.|
|The Document Properties (i.e. Subject, Author, Title, Keywords, and Language) must be properly filled out.||To apply Document Properties click on the File tab, then Properties in the right pane to expand. Choose Show Document Panel to expose the document properties and fill in the fields.|
|Documents that contain a Table of Contents (TOC) need to be created by Microsoft’s Reference tool.||TOC’s are generated by the styles that are applied to the document. To create a TOC, click the References tab, then click the Table of Contents button in the Table of Contents group. Choose the style you would like to use, click the style to apply it to the document.|
|A separate accessible version of the document must be provided when there is no other way to make the content accessible.||Example: An organizational chart|
Microsoft has several helpful guides on creating accessible documents. These guides are accessible from within any Office application (hit F1 key and search on the term “Accessibility”). The following links provide web accessible documentation you can read anytime without being in an Office application.
|Office Accessibility Center||Landing page with links to multiple resources on making content accessible. This page has links to four topics: make content accessible; help for specific Office 365 applications; demos on how to use accessibility features; and what’s new in accessibility.|
|Overview: Creating Accessible Office files||This link has a five minute video on creating accessible content using Microsoft Office.|
|Create accessible Word documents||Online video tutorial on how to create accessible Word documents.|
|Make your Word documents accessible||Learn how to create Word documents that are more accessible to people with disabilities, or who are using assistive technologies.|
|Accessibility Checker||A tool used to check Office files for accessibility. A great way to review existing documents.|
|Rules for Accessibility Checker||One section of the Microsoft Office online resource that explains how the accessibility checker works and rules it follows.|
|Create Accessible PDF files||PDF file format are widely used on the Internet and websites.|
|Make your PowerPoint presentations accessible||Best practices for making PowerPoint presentations accessible|
Audio and video content will require a readable version (transcription or closed captioning) to make it accessible. The ability to create a transcript or closed captioning easily and quickly is the ultimate solution for audio content accessibility.
Athens State has recently implemented TechSmith Relay for all audio/video recordings used in courses. Relay includes a closed captioning tool that adds captions to videos. The captioned video can be viewed with or without captioning. Useful information on using TechSmith Relay is available at: https://athensstateuniversity.zendesk.com/hc/en-us/articles/360009430554-Getting-Started-with-TechSmith-Relay
There are several things that can be done to prepare multimedia content for accessibility. Audio should be clear, understandable, and well edited to remove extraneous content. Likewise, video content should be understandable and well edited. If content is questionable, consider recording again. If possible, before recording any audio or video, script out the content then follow the script as you record. This will allow you to publish the script and the recorded content together, thus making it accessible in two formats.
It is recommended for individuals who create multimedia content to review the website www.w3.org/2008/06/video-notes#q1 for helpful information on accessible audio and video recordings.
The procurement process at Athens State will include the review proposed purchases for accessibility. Products that will be subject to accessibility review are:
Web-based internet and intranet information and applications
Video and multimedia products
Printers/copier, kiosks, fax machines
Desktop and portable computers
If you will be purchasing any of these products or services, do a preliminary review first by gathering the items below to determine accessibility compliance:
- Who will use the product/service? Is it a campus-wide resource or is it only used in academic labs by students.
- Has this product been used on campus before? Do other universities use this product, if so, are there any known issue with accessibility.
- Check the vendor Voluntary Product Accessibility Template URL to find out what the vendor says about their product in relation to accessibility standards.
Textbooks and Academic Software Applications/Websites
Like the general procurement practices described previous, when faculty choose a new textbook and accompanying software applications/guides, accessibility should be part of the review process. Textbook selection, however, differs from general procurement issues because accessibility issues are handled differently. Textbooks are intellectual property and chosen based upon the subject or program requirements. To address accessibility, the availability of an e-text formatted textbook is ideal because the e-text allows for a quicker turnaround time to provide an accommodation for a student. Most large publishing companies have an online request form for e-text versions of the textbook and some may require confirmation of the reason for e-text access and that the student owns a purchased copy of the textbook.
If you receive an e-text of a textbook from the publisher, it may not be in the ideal format for your student, but can be converted to a useable format.
If the same textbook and/or accompanying software application have been used for a long time please to review it for accessibility issues as previously suggested.
Voluntary Product Accessibility Template (VPAT) details how a company will comply with the federal Section 508 standards. Do a Google search on company or product name followed by VPAT and you will find a description of accessibility compliance for that product. While VPATs are currently used to describe Section 508 compliance, any accessibility standards and guidelines, such as WCAG can be applied in a similar format to the VPAT.