Main Page: Difference between revisions
No edit summary |
No edit summary |
||
Line 40: | Line 40: | ||
*Closed captioning is provided for both live and recorded sessions | *Closed captioning is provided for both live and recorded sessions | ||
*[http://www.adaconferences.org/Accessibility/ Collaborate Accessibility Guide] | *[http://www.adaconferences.org/Accessibility/ Collaborate Accessibility Guide] | ||
WAG meets next on Wednesday February 3, 2016 to discuss using WAI-ARIA for creating accessible dynamic web content. | '''WAG meets next on Wednesday February 3, 2016 to discuss using WAI-ARIA for creating accessible dynamic web content.''' | ||
[[Monthly_Meetings#Next_Meeting|View more information about our next meeting]]. | [[Monthly_Meetings#Next_Meeting|View more information about our next meeting]]. |
Revision as of 12:57, 6 January 2016
|
|
WAG Listserv
All are welcome to join the WAG Listserv. (Link forthcoming)
WAG Monthly Meetings
WAG meets online via Collaborate (web conferencing solution) on the first Wednesday of every month from 11:00am - 12:00pm EST.Please join the WAG Listserv to receive the login link directly. All meetings are closed captioned. Collaborate accessibility features
Next Meeting
Date: Wednesday February 3, 2016
Time: 11:00am - 12:00pm (EST)
Topic: WAI-ARIA: Intro to Accessible Dynamic Web Content
Presenter: Janet Sylvia, Web Accessibility Group (WAG) Leader
Guest Speakers: Adelle Frank, (Web Developer Manager, Senior at Georgia Tech); and Casey Gordon (Web Developer at UGA FACS) and other WAG Members share their experiences implementing basic ARIA.
Description: Join us for this introduction to Accessible Rich Internet Applications (WAI-ARIA), a suite of attributes used to create accessible content when HTML source-code alone is insufficient. We will discuss core components of ARIA for creating accessible navigation, forms, widgets, and other dynamic content. WAG members who have implemented basic ARIA will share their experiences.
Note: Section 508 allows for “equivalent facilitation” of web-based content. By incorporating ARIA attributes, you are complying with Section 508 by providing “substantially equivalent or greater access to and use of (your website) for people with disabilities.”