E-mail List Archives
Re: WCAG 2.0 Compliance criteria for internal or non public websites
From: Julie Romanowski
Date: Dec 8, 2009 1:15PM
- Next message: Moore,Michael (DARS): "Re: WCAG 2.0 Compliance criteria for internal or non public websites"
- Previous message: Geof Collis: "Re: WCAG 2.0 Compliance criteria for internal or non public websites"
- Next message in Thread: Moore,Michael (DARS): "Re: WCAG 2.0 Compliance criteria for internal or non public websites"
- Previous message in Thread: Geof Collis: "Re: WCAG 2.0 Compliance criteria for internal or non public websites"
- View all messages in this Thread
We can't predict the future, and organizations can't know what their
employees' future needs will be. What we can do is design our sites and
web applications with accessibility in mind.
It's important to note that screen reader accessibility does not
guarantee the site is accessible to all users. What about those with
limited vision or color blindness? How about speech-recognition or
keyboard-only users? How about the older employee who now needs hearing
aids? That video transcript Sam seems reluctant to provide might come in
handy for the employee who just can't quite make out what the person in
the video is saying.
WCAG 2.0 A compliance isn't that difficult, and AA compliance isn't much
harder. And updating the intranet sites are much less expensive than the
potential lawsuit that may occur if an employee can't access a required
web application because of accessibility issues.
- Next message: Moore,Michael (DARS): "Re: WCAG 2.0 Compliance criteria for internal or non public websites"
- Previous message: Geof Collis: "Re: WCAG 2.0 Compliance criteria for internal or non public websites"
- Next message in Thread: Moore,Michael (DARS): "Re: WCAG 2.0 Compliance criteria for internal or non public websites"
- Previous message in Thread: Geof Collis: "Re: WCAG 2.0 Compliance criteria for internal or non public websites"
- View all messages in this Thread