BEGIN:VCALENDAR
PRODID:-//github.com/rianjs/ical.net//NONSGML ical.net 4.0//EN
VERSION:2.0
BEGIN:VTIMEZONE
TZID:America/Phoenix
X-LIC-LOCATION:America/Phoenix
END:VTIMEZONE
BEGIN:VEVENT
DESCRIPTION:Unfortunately when developing WCAG2\, the Working Group did no
 t envision the current world where mobile is almost ubiquitous. For examp
 le\, on a mobile device there is no continual access to a keyboard (unles
 s someone is using it as an add-on to the device – or using a Blackberry 
 Classic). WCAG2 requires that all content be accessible to the keyboard i
 nterface\, but it does not require that all content be accessible to a mo
 use or to a touchscreen user – which is essential on a mobile device. Gia
 n Wild talks about the unique accessibility issues on a mobile site and m
 obile app\, including hover traps\, VoiceOver swipe traps and zoom traps.
DTEND;TZID=America/Phoenix:20161008T163000
DTSTAMP:20260412T041740Z
DTSTART;TZID=America/Phoenix:20161008T153000
GEO:33.293070;-111.796620
LOCATION:Chandler - Gilbert Community College - IRN-130
ORGANIZER:
SEQUENCE:0
STATUS:CONFIRMED
SUMMARY:Unfortunately when developing WCAG2\, the Working Group did not en
 vision the current world where mobile is almost ubiquitous. For example\,
  on a mobile device there is no continual access to a keyboard (unless so
 meone is using it as an add-on to the device – or using a Blackberry Clas
 sic). WCAG2 requires that all content be accessible to the keyboard inter
 face\, but it does not require that all content be accessible to a mouse 
 or to a touchscreen user – which is essential on a mobile device. Gian Wi
 ld talks about the unique accessibility issues on a mobile site and mobil
 e app\, including hover traps\, VoiceOver swipe traps and zoom traps.
UID:42fe18cc-593d-4b48-8423-1ca9f24c499a
END:VEVENT
END:VCALENDAR