'''MediaWiki has been successfully installed.'''
Consult the [http:// meta. wikimedia.org/wiki /Help:Contents User's Guide] for information on using the wiki software.
the [http://..org/wiki's ] .
Getting started ==
* [http://www. mediawiki.org/ wiki/ Manual: Configuration_settings Configuration settings list]
* [http://www. mediawiki.org/ wiki/ Manual: FAQ MediaWiki FAQ]
* [https: //lists. wikimedia. org/mailman/listinfo/mediawiki- announce MediaWiki release mailing list]
: . .
Revision as of 14:40, 9 December 2015
The Web Accessibility Group (WAG) began at UGA in 2011 and transitioned to Georgia Tech's AMAC Accessibility Center in 2015. Its purpose is to bring together individuals in higher education attempting to navigate the complex Section 508 standards and Web Content Accessibility Guidelines (WCAG) 2.0. WAG currently offers web accessibility information and assistance through a wiki, listserv, and monthly online meetings where expert presenters are invited to share best practices and solutions. WAG works closely with AMAC's AccessGA project.
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 everyone 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
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.”