A | B | C | D | E | F | |
---|---|---|---|---|---|---|
1 | Creating and Selecting Accessible Course Materials | |||||
2 | Contact the IT and Web Accessibility Coordinating Group, accessibility@cio.wisc.edu. URL for this list: go.wisc.edu/accessible-course-materials. | |||||
3 | MATERIAL TYPE | STEPS AND RESOURCES | REFERENCES | |||
4 | CAMPUS SERVICES | |||||
6 | Printed course packets. Examples: Scanned printouts, PDFs, blogs, URLs, book chapters | 1. Keep original files such as Word documents, electronic versions such as PDFs, and sources/URLs of originals. 2. Work with McBurney's Document Conversion Service and Library Course Pages. | http://www.mcburney.wisc.edu/services/documentconversion/facultytips.php | |||
7 | Course reserves | 1. Keep original files such as Word documents, electronic versions such as PDFs, and sources/URLs of originals. 2. Create tagged PDFs. (See PDF resources below.) 3. Ask the library about Library Course Pages. | http://www.library.wisc.edu/lcp/ | |||
8 | Learn@UW | The Learn@UW (D2L) platform is quite accessible. The overall accessibility, however, depends on the accessibility of all the content you add to your courses, including audio, video, links, files, and reserves. | https://kb.doit.wisc.edu/luwmad/page.php?id=3236 | |||
9 | PDF (Portable Document Format) | 1. Make PDFs electronically from the original document rather than a scan, when possible. 2. Use tools such as Adobe Acrobat and Microsoft Office than can make tagged PDFs. 3. In Adobe Acrobat, test a file by choosing Advanced > Accessibility > Full check. 4. See how well your PDF reads in Adobe Reader or Adobe Acrobat with the Read Out Loud feature by choosing: View > Read Out Loud. | http://go.wisc.edu/accessiblepdf | |||
10 | PDFs with images need alternative text. | http://go.wisc.edu/accessiblepdf-images | ||||
11 | PDFs need a check for reading order. | http://go.wisc.edu/accessiblepdf-custom | ||||
12 | PDF tips | http://webaim.org/techniques/acrobat/ | ||||
13 | Social media: Facebook, Twitter, etc. | Accessibility of social media varies. Search for information on a site's accessibility or consult with DoIT Academic Technology | ||||
14 | Textbooks | 1. Ask textbook representatives what accessibility options they provide. 2. Select textbooks early to allow time for conversion when an accessible version isn't available. 3. When using e-textbooks, ask if the corresponding e-reader is accessible. | http://www.mcburney.wisc.edu/services/documentconversion/facultytips.php | |||
15 | UW-Madison Google Apps | Google apps accessibility, resources for developers and publishers, advocacy | http://www.google.com/accessibility/ | |||
16 | Accessible GoogleDocs | http://accessibility.psu.edu/googledocs | ||||
17 | Google Apps for technical administrators | http://support.google.com/a/bin/answer.py?hl=en&answer=2821355 | ||||
18 | UW-Madison Moodle | Watch development or forum pages for new features. | http://docs.moodle.org/dev/Accessibility | |||
19 | Video captioning (CC or closed captions) | 1. Select videos that already have captions when possible. 2. Keep any scripts that are created as part of the production/recording process. 3. Work with McBurney's Media Captioning Service if you have videos that are not available with captions and for further assistance. | http://www.mcburney.wisc.edu/services/captioning/mediaaccessibility.php | |||
20 | Audio recordings (podcasts) | 1. Keep any scripts that are created as part of the production/recording process. 2. Offer a text transcript. 3. If a transcript is not available, work with McBurney's Media Captioning Service." | http://www.mcburney.wisc.edu/services/captioning/mediaaccessibility.php | |||
21 | http://jod.id.au/tutorial/accessible-podcast.html | |||||
22 | Course websites | 1. Be sure all images and photos have alternate text. 2. Learn and work toward the other 15 Section 508 guidelines. | http://www.doit.wisc.edu/accessibility/ | |||
23 | Designing with web standards | http://search.library.wisc.edu/catalog/ocn606572906 | ||||
24 | Testing webpages with Wave. | http://wave.webaim.org | ||||
25 | Testing webpages with the Functional Accessibility Evaluator. | http://fae.cita.uiuc.edu/ | ||||
26 | Writing alternate text | Describe photos and images. Skip alternate text for decorative elements. | ||||
27 | Writing tips from WebAIM | http://webaim.org/techniques/alttext/ | ||||
28 | Writing tips from the World Wide Web Consortium | http://dev.w3.org/html5/alt-techniques/#sec2Tips | ||||
29 | APPLICATIONS | |||||
30 | Adobe applications | Accessibility resources for Adobe products | http://www.adobe.com/accessibility/ | |||
31 | Adobe applications - Acrobat | https://admin.adobe.acrobat.com/_a295153/p16268622/ | ||||
32 | Adobe applications - Flash | http://webaim.org/techniques/flash/text.php | ||||
33 | http://www.adobe.com/accessibility/products/flash.html | |||||
34 | Microsoft Office (Word, Excel) | 1. Use styles (Heading 1, Heading 2, etc.) in the correct order to identify heading structure. Making tables of contents will be a snap as a result! 2. For each image, insert alternate text to describe the picture and its importance. In Word 2010, for instance, right-click an image or object, select Format, and then choose, "Alt Text." 3. Use the Accessibility Checker (File > Info > Check for Issues > Check Accessibility) | http://office.microsoft.com/en-us/word-help/creating-accessible-word-documents-HA101999993.aspx?CTT=1#_Toc275414986 | |||
35 | Microsoft Office (PowerPoint) | 1. Use a unique title for each slide. 2. For each image, insert alternate text to describe the picture and its importance. Right-click the image or object, select Format, and then choose "Alt Text." 3. Use the Accessibility Checker (File > Info > Check for Issues > Check Accessibility) | http://office.microsoft.com/en-us/powerpoint-help/creating-accessible-powerpoint-presentations-HA102013555.aspx?CTT=1 | |||
36 | WEB AND APPLICATION DEVELOPMENT | |||||
37 | Websites, upgrading code with new ARIA roles for HTML5 | http://mcdlr.com/wai-aria-cheatsheet/ | ||||
38 | Websites, quick test | Illinois Information Technology Accessibility Act (IITAA) checklist | http://www.dhs.state.il.us/iitaa/webaccessibilityquicktestchecklist.html | |||
39 | Websites, general | Designing with web standards, chapter 14, "Accessibility: The Soul of Web Standards" | http://search.library.wisc.edu/catalog/ocn606572906 | |||
40 | Websites, developer testing extension, Firefox | OpenAjax Accessibility Extension | https://addons.mozilla.org/en-us/firefox/addon/openajax-accessibility-exte/ | |||
41 | Websites, developer testing extension, Chrome | Accessibiity Developer Tools | https://chrome.google.com/webstore/detail/accessibility-developer-t/fpkknkljclfencbdbgkenhalefipecmb | |||
42 | Javascript | |||||
43 | Cascading style sheets (CSS) | Code for screenreaders allows a few accessibility features to be moved outside the page without interfering with the software to read pages aloud. | .screenreader { position:absolute; top:-1000px; left:-1000px; width:1px; height:1px; overflow:hidden; visibility:hidden; z-index:-1000; } .hide-text { text-indent: 100%; white-space: nowrap; overflow: hidden; } /* Jeffrey Zeldman; may not collapse space in some browsers. */ .ir { font: 0/0 a; text-shadow: none; color: transparent; } /* Nicholas Gallagher */ | |||
44 | Mobile apps | Use techniques from the W3C Web Accessibility Initiative. | http://www.w3.org/WAI/mobile/ | |||
45 | iPhone | Supporting the iOS Human Interface Guidelines | https://developer.apple.com/technologies/ios/accessibility.html | |||
46 | Android | Developing and testing accessible apps | http://developer.android.com/guide/topics/ui/accessibility/apps.html | |||
47 | Java | An accessibility summary for Java from Oracle. | http://docs.oracle.com/javase/7/docs/technotes/guides/access/ | |||
48 | Perl | |||||
49 | Python | https://wiki.gnome.org/Accessibility/PythonPoweredAccessibility |