BEGIN:VCALENDAR PRODID:-//Microsoft Corporation//Outlook 16.0 MIMEDIR//EN VERSION:2.0 METHOD:PUBLISH X-MS-OLK-FORCEINSPECTOROPEN:TRUE BEGIN:VTIMEZONE TZID:Eastern Standard Time BEGIN:STANDARD DTSTART:16011104T020000 RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=11 TZOFFSETFROM:-0400 TZOFFSETTO:-0500 END:STANDARD BEGIN:DAYLIGHT DTSTART:16010311T020000 RRULE:FREQ=YEARLY;BYDAY=2SU;BYMONTH=3 TZOFFSETFROM:-0500 TZOFFSETTO:-0400 END:DAYLIGHT END:VTIMEZONE BEGIN:VEVENT CLASS:PUBLIC CREATED:20220628T173955Z DESCRIPTION:Accessible Documents: The End-User Experience\nPresented by Jim my Brown\, Accessibility Coordinator\, KY OVR\, DHS Trusted Tester\nAs sig hted users\, we often look at a document in “helicopter view”. We tend to forget that not everyone is able to see the whole document at all time s (or quickly scan over the document with their eyes). Many users of assis tive technologies\, such as screen readers and screen magnifiers\, have a very limited/targeted view of the document. They may only be able to focus on one element at a time.\nCombining accessibility standards and usabilit y processes with real people ensures that your electronic content (website s and documents) are both technically and functionally usable by people wi th disabilities. This is referred to as “usable accessibility” or “a ccessible user experience” (UX). It is just as important to understand h ow your document is read by assistive technology (AT)\, such as screen rea ders\, and not just that it can be read by AT and/or passes an automated a ccessibility checker. Getting the perspective of AT users with real world\ , lived experience is just as important as meeting the standards. In this session\, we will be looking at a sample document\, starting with a comple tely inaccessible version and working through the steps to make the docume nt accessible. Along the way\, we will be testing the document with a scre en reader and visually walking through the tags tree to gain a better unde rstanding of how AT interacts with the documents we create. You will also have the opportunity to hear first hand from users of screen readers and m agnification software about their experiences and preferences with accessi ble documents. \nhttps://www.katsnet.org/atw2022/accessible-documents/\n DTEND;TZID="Eastern Standard Time":20220909T101500 DTSTAMP:20220628T173955Z DTSTART;TZID="Eastern Standard Time":20220909T090000 LAST-MODIFIED:20220628T173955Z LOCATION:Harold R Benson Research Farm\, 1525 Mills Lane\, Frankfort\, KY 4 0601 PRIORITY:5 SEQUENCE:0 SUMMARY;LANGUAGE=en-us:Summer AT Workshop 2022: Accessible Documents: The E nd-User Experience TRANSP:OPAQUE UID:040000008200E00074C5B7101A82E0080000000030241BF7E38AD801000000000000000 0100000007E33938F49330D44B2C97924E041C151 X-ALT-DESC;FMTTYPE=text/html:

Accessible Documents: The End-User Experience

Presented by Jimmy Bro wn\, Accessibility Coordinator\, KY OVR\, DHS Trusted Tester

As sighted users\, we often look at a document in “\;helicopter view”\;. We tend to forget that not e veryone is able to see the whole document at all times (or quickly scan ov er the document with their eyes). Many users of assistive technologies\, s uch as screen readers and screen magnifiers\, have a very limited/targeted view of the document. They may only be able to focus on one element at a time.

Combining accessib ility standards and usability processes with real people ensures that your electronic content (websites and documents) are both technically and func tionally usable by people with disabilities. This is referred to as “ \;usable accessibility”\; or “\;accessible user experience” \; (UX). It is just as important to understand how your document is read b y assistive technology (AT)\, such as screen readers\, and not just that i t can be read by AT and/or passes an automated accessibility checker. Gett ing the perspective of AT users with real world\, lived experience is just as important as meeting the standards. In this session\, we will be looki ng at a sample document\, starting with a completely inaccessible version and working through the steps to make the document accessible. Along the w ay\, we will be testing the document with a screen reader and visually wal king through the tags tree to gain a better understanding of how AT intera cts with the documents we create. You will also have the opportunity to he ar first hand from users of screen readers and m agnification software about their experiences and preferences with accessi ble documents.

https://www.katsnet.org/atw2022/acc essible-documents/

X-MICROSOFT-CDO-BUSYSTATUS:BUSY X-MICROSOFT-CDO-IMPORTANCE:1 X-MICROSOFT-DISALLOW-COUNTER:FALSE X-MS-OLK-AUTOFILLLOCATION:FALSE X-MS-OLK-CONFTYPE:0 END:VEVENT END:VCALENDAR