WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: WCAG 2.0 Compliance criteria for internal or non public websites

for

From: Julie Romanowski
Date: Dec 8, 2009 1:15PM

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.

-----Original Message-----
From: Sam S [mailto: <EMAIL REMOVED> ]
Sent: Tuesday, December 08, 2009 12:20 PM
To: <EMAIL REMOVED>
Subject: [WebAIM] WCAG 2.0 Compliance criteria for internal or non
public websites

Hello,

I would like to know that if it is necessary to meet the entire WCAG 2.0
success criterion for achieving WCAG 2.0 Compliance. Is WCAG 2.0
flexible as per the needs of the disabled users accessing the content?

Consider an example where in an organization the disabled employees who
need accessibility are only blind users, that is screen reader users and
currently, there are no other disabled users. The organization website
meets all the WCAG 2.0 requirements for screen reader accessibility, and
so is accessible to all employees.

If so, is it still necessary to say for example, provide transcripts for
audio content for hearing impaired persons even if currently there is no
one who needs this feature?

I do not mean to say that accessibility is important only for screen
reader users. I also understand that providing transcripts for audio can
be useful to all users, but is it still *mandatory* for WCAG 2.0
Compliance in such a case?

I just want to know if we can implement accessibility and achieve WCAG
2.0 compliance (at least Level 1) on basis on user requirement. This is
especially for internal or non public websites where the developers have
knowledge of the users accessing the website or application and provide
only those accessibility features which are needed or are important.

Thanks,

Sam