Welcome to today’s AEM Center Webinar The webinar will begin shortly Material for this webinar is available for download at this module’s page on the AEM Center website: http://aem.cast.org/about/module-2-new- educator-training.html

View Closed Captions Click on the Closed Caption button Captions will appear along the bottom of your screen

Contribute to the Conversation To use the text chat: Open the chat panel Choose “all panelists and attendees” from the dropdown above the text entry field And please tweet out to #aem4all

Materials and Recording Material for this webinar is available for download at this module’s page on the AEM Center website: http://aem.cast.org/about/module-2-new-educator-training.html The link to the recording will be available within a week at the same web page

Creating Accessible Documents Cynthia Curry, Director Luis Pérez, TA Specialist National AEM Center

Review – Module 1 What were some of your ahas from Module 1? @AEM_Center | #aem4all

Best Practices JOY Tips to make your documents more accessible and inclusive @AEM_Center | #aem4all

Advice from Maya Angelou “Do the best you can until you know better. Then when you know better, do better.” @AEM_Center | #aem4all

POUR on the Accessibility: WCAG Web Content Accessibility Guidelines 2.1 Information, interface, navigation, components, content must be: Perceivable Operable Understandable Robust Photo credit: Credit: Jenny Downing on Flickr/CC BY 2.0   Perceivable: Information and user components must be presentable to users in ways they can perceive. This means that information must be able to be perceived by everyone.   Operable: User interface components and navigation must be operable. This means that the interface cannot require interaction that a user with a disability cannot perform.   Understandable: Information, as well as the operation of the user interface, must be understandable. This means that all users must be able to understand the information and the operation of the user interface.   Robust: Content must be robust enough that it can be interpreted reliably by a wide variety of user agents (such as browsers), including assistive technologies. This ensures that your content remains accessible as technologies evolve. @AEM_Center | #aem4all

POUR: Perceivable Text alternatives for visuals Closed-captioned media CCan everyone perceive (see/hear) the content? Text alternatives for visuals Closed-captioned media Sufficient contrast Photo credit: Credit: Jenny Downing on Flickr/CC BY 2.0 @AEM_Center | #aem4all

POUR: Operable CCan everyone navigate the content with ease? A clear structure with properly marked up headings Descriptive hyperlinks Photo credit: Credit: Jenny Downing on Flickr/CC BY 2.0 @AEM_Center | #aem4all

POUR: Understandable IIs the language appropriate for my audience? Use templates for a consistent, predictable experience Use plain language Photo credit: Credit: Jenny Downing on Flickr/CC BY 2.0 @AEM_Center | #aem4all

POUR: Robust DDoes my content follow best practices? Conduct an accessibility check @AEM_Center | #aem4all

What is your experience with POUR? Which of the techniques mentioned are familiar? Which ones are new?

Demo: Microsoft Word and Google Docs Add alternative text to an image Create proper headings Make sure hyperlinks are descriptive http://aem.cast.org/creating/designing-for-accessibility-pour.html @AEM_Center | #aem4all

Quality Image Descriptions WebAIM: Alternative Text DIAGRAM Center (more complex images) An alt Decision Tree (WAI)

Ensure sufficient contrast The following tool can help you check the color contrast: Colour Contrast Analyser (Paciello Group) Available for Windows/Mac Not Enough Contrast Enough Contrast

Use unique slide titles (View > Outline View in PowerPoint) Screen reader users can use an outline created from the slide titles to more easily navigate a long presentation and go right to a desired slide. For others: easier to scan the presentation for the big ideas/key points. @AEM_Center | #aem4all

Name your worksheets in Excel and Google Sheets More helpful than hearing “Sheet 1, Sheet 2, etc.” when navigating with a screen reader.

Determine the Reading Level (1 of 2) Add Reading Statistics to the Spell and Grammar Check Word, Preferences, Authoring and Proofing Tools on Mac File, Options, Proofing on Windows

Determine the Reading Level (2 of 2) Check Spelling and Grammar to get Reading Level at the end Between 60 and 70 for Flesch-Kincaid Between 7.0 and 8.0 for Grade Level Test

Alternative: Hemingway Editor Available at hemingwayapp.com

Run the Accessibility Checker Found in the Ribbon under Review. @AEM_Center | #aem4all

Use Grackle for Google aGrackle will perform an accessibility check and provide tips for addressing errors.

Demo: Doing An Accessibility Check

AEM Center Resources http://aem.cast.org/creating/designing-for-accessibility-pour.html @AEM_Center | #aem4all

What are your TQAs? Thoughts, questions and ahas. How do you plan to use what you learned today?

Thank You! Cynthia Curry ccurry@cast.org @clcurry Luis Pérez lperez@cast.org @eyeonaxs @AEM_Center | #aem4all