Re: Update and Request

We are in process of updating our Web Accessibility Statement of
Encouragement. There appears to be a fundamental shift in logic behind
the development of Higher Ed Accessibility statements that I can share
offline, if you are interested.

 

I am currently MSU's representative on the CIC Accessibility Group which
includes all of the Big 10 schools. I am slated to present on the topic
at the next meeting.

 

Until our revised Statement is made public, I cannot comment
specifically on the list. However, I can give you a heads up on the
issues we are working on if you want to give me a call. 

 

 

Cheers, 

 

Charmane

 

 

<>< ><> <>< ><> <>< <>< ><> <>< ><> <>< ><> <>< ><> <>< ><> <>< ><> <><
><> <>< ><> 

"Creating shared meaning and vision is at the crux of successful
organizational change."  (Corcoran 1997)

 

Charmane K. Corcoran

Information & Accessibility Specialist

Client Advocacy Office

Michigan State University

316A Computer Center

East Lansing MI 48824-1042

 

Direct: 517/432-5318  

E-mail: corcora1@msu.edu

URI: http://www.msu.edu/~corcora1/

Main Office: 517/353-4856   FAX 517/355-0141

 

________________________________

From: Justin Thorp [mailto:justin@mycapitalweb.com] 
Sent: Thursday, February 02, 2006 11:56 PM
To: Wayne Dick
Cc: EOWG (E-mail)
Subject: Re: Update and Request

 

Hi Wayne,

 

At Michigan State University, we have a Statement of Encouragement for
Web Accessibility.

http://www.msu.edu/webaccess/principles/encourage.html

 

Sincerely,

Justin Thorp

 

 

On Feb 2, 2006, at 5:44 PM, Wayne Dick wrote:





 

Hi,

 

The committee I Chair is writing the Accessibility Policy for CSU Long
Beach right now.  Do any of you know of any university accessibility
policies that are especially good.

 

This Campus IT Comittee will be developing policies and operational
procedures for security and accessibility.  In general we will monitor
all human factors issues as we tighten security, but we will make sure
that we don't break and even improve accessibility as we do it.

 

I will appreciate any pointers to preexisting policy.

 

Thank You,

Wayne

 

Received on Friday, 3 February 2006 14:31:57 UTC