[27097] in Public-Access_Computer_Systems_Forum

home help back first fref pref prev next nref lref last post

Designing and checking Accessible Web pages

daemon@ATHENA.MIT.EDU (Prof Norm Coombs)
Tue Sep 22 06:07:15 2009

X-Barracuda-Envelope-From: owner-pacs-l@LISTSERV.UH.EDU
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Message-ID:  <6.0.3.0.2.20090920212842.023b5ec0@pop.gmail.com>
Date:         Sun, 20 Sep 2009 21:30:14 -0700
Reply-To: Public-Access Computer Systems Forum <PACS-L@LISTSERV.UH.EDU>
From: Prof Norm Coombs <norm.coombs@GMAIL.COM>
To: PACS-L@LISTSERV.UH.EDU

Designing and checking Accessible Web pages

Four Webinars on tools to assist you in checking the accessibility of your 
Web pages for people with disabilities
AChecker
Firefox Extension
Wave
Cynthia Says
The archives for these Webinars will be at:
http://easi.cc/archive/achecker/resources.htm
The recordings of Achecker and Firefox are there now and the other Webinars 
are this Tuesday and Wednesday.  Read and register online for these free 
Webinars at
http://easi.cc/clinic.htm

BARRIER-FREE WEB DESIGN COURSE: starting October 5
  Do you have trouble reading computer and software manuals? EASI will take 
the jargon out of Web design and out of the technical requirements for Web 
accessibility. Instructors are always available in email to provide individual
support. Having technical information originally designed in acceptable 
technical language to promote clear technical requirements and to meet the 
needs
of technicians is important, and the WCAG guidelines do an excellent job of 
this. But, EASI strives to translate this precise information for the many 
designers
who, while making Web pages, are not real technical types. EASI will make 
creating accessible Web pages easier than you think!

Course registration is $350 with discounts for EASI annual Webinar members.

Read more and register online at:
http://easi.cc/workshops/easiweb.htm

Course Structure
After an introductory lesson, the course will follow the 4 principles and 
the 12 guidelines around which WCAG 2 are organized:

Principle 1 Perceivable
Guideline 1.1 Provide text alternatives for any non-text content so that it 
can be changed into other forms people need, such as large print, braille, 
speech, symbols or simpler language.
Guideline 1.2 Provide alternatives for time-based media.
Guideline 1.3 Create content that can be presented in different ways (for 
example simpler layout) without losing information or structure.
Guideline 1.4 Make it easier for users to see and hear content including 
separating foreground from background.

Principle 2 Operable
Guideline 2.1 Make all functionality available from a keyboard.
guideline 2.2 Provide users enough time to read and use content.
Guideline 2.3 Do not design content in a way that is known to cause seizures.
Guideline 2.4 Provide ways to help users navigate, find content, and 
determine where they are.

Principle 3 Understandable
Guideline 3.1 Make text content readable and understandable.
Guideline 3.2 Make Web pages appear and operate in predictable ways.
Guideline 3.3 Help users avoid and correct mistakes.

Principle 4 Robust
Guideline 4.1 Maximize compatibility with current and future user agents, 
including assistive technologies.


The course is asynchronous and available in EASI's Blackboard system.
Participants should plan to complete the course in a month. Those who are 
not able to finish will be automatically enrolled for the next course 
offering and have a second opportunity to complete the work.

Read more and register online at:
http://easi.cc/workshops/easiweb.htm

Norm Coombs CEO EASI
norm.coombs@gmail.com



  . . . . . . . . . . . . . . . .
Once you choose hope, anything's possible.  Christopher Reeve

Norman Coombs norm.coombs@gmail.com
CEO EASI Equal Access to Software and Information
phone (949) 855-4852 (NOTE pacific time zone)
****READ ABOUT THE DICK BANKS MEMORIAL SCHOLARSHIP:
http://easi.cc/scholarship.htm

home help back first fref pref prev next nref lref last post