1 / 42

Is Your Course Content Accessible?

Is Your Course Content Accessible?. Terrill Thompson tft@uw.edu http://staff.washington.edu/ tft http:// terrillthompson.com @ terrillthompson. “Accessible” to whom?. Everyone!. Ability on a continuum. See Hear Walk Read print Write with pen or pencil Communicate verbally

Télécharger la présentation

Is Your Course Content Accessible?

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.


Presentation Transcript

  1. Is Your Course Content Accessible? Terrill Thompson tft@uw.edu http://staff.washington.edu/tft http://terrillthompson.com @terrillthompson

  2. “Accessible” to whom?

  3. Everyone!

  4. Ability on a continuum See Hear Walk Read print Write with pen or pencil Communicate verbally Tune out distraction etc.

  5. Old School Technologies

  6. Today: Technological Diversity

  7. We All Have Choices

  8. Student Photo #1

  9. Student Photo #2

  10. Student Photo #3

  11. Can everyoneaccess your course content?

  12. Blurry site example

  13. Home page

  14. Example: Images with No Alt Text

  15. Test #3 Example – Slide 1

  16. Test #3: Example – Slide 2

  17. Test #3: Example – Slide 3

  18. Test #3: Example – Slide 4

  19. Example: Mouse-Dependent Menus

  20. Design Tip: Don't assume users have mice!

  21. There are no mice on this slide.

  22. Example: Inaccessible CAPTCHA

  23. Example: Type the RED WORD

  24. Example: Requires Flash

  25. Example: Is this webinaraccessible?

  26. What about electronic documents?

  27. An accessible electronic document: • Has good structure • For headings, use headings • For lists, use lists • Provide details about each item • For images, add alternate text • For all content, identify the language • Is created in a way that communicates structure to assistive technology • HTML, Word, & PDF all support accessibility

  28. HTML • The most accessible document format • Alt text for images • Structure (e.g., headings, lists) • Document language (e.g., “en”,”es”,”fr”) • Accessible markup for forms • Accessible markup for tables • Accessible math (MathML) • Accessibility is not automatic—Authors must know to use these features

  29. It is possible to create a reasonably accessible Microsoft Word document

  30. An Accessible Word Doc Includes: • Alt text for images • Heading styles (Heading 1, Heading 2, etc.) • Lists, created using Word’s list buttons • Simple tables, with column headers identified • Language identified

  31. Adobe PDF • Three general types: • Image • Image with embedded fonts • Tagged (optimized for accessibility)

  32. To Create an Accessible PDF • Use an authoring tool that supports: • Creating documents with headings & subheadings • Adding alt text to images • Exporting to tagged PDF • Use these accessibility features anytime you create a document

  33. It is possible to create an accessible tagged PDF from Microsoft Word (Windows only)

  34. It is possible to create an accessible tagged PDF from Adobe InDesign

  35. Other Authoring Tools that support Tagged PDF And maybe a few others: http://lists.w3.org/Archives/Public/w3c-wai-gl/2011AprJun/0061.html

  36. With Adobe Acrobat Pro, you can make an accessible PDF from an inaccessible one

  37. PDF Accessibility Workflows • http://uw.edu/accessibility/pdf.html

  38. Always Consider Accessibility • When creating websites • When creating documents • When considering which technologies to use

  39. Questions to Always Ask When Choosing Technologies • Is it accessible? • Can users perform all functions without a mouse? • Has it been tested using assistive technologies such as screen readers? • If it supports audio, does it support captions? • Is accessibility documentation available? • If it’s an authoring tool, how does one create accessible content with it?

  40. Example: Google Docs

  41. For more information… • Terrill’s slides and other resourceshttp://staff.washington.edu/tft • AccessComputinghttp://uw.edu/accesscomputing • University of Washington IT Accessibilityhttp://uw.edu/accessibility • Terrill’s bloghttp://terrillthompson.com

  42. To Do: Add accessibility to my everyday document authoring process

More Related