WebAIM - Web Accessibility In Mind

E-mail List Archives

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

for

From: Don Mauck
Date: Dec 8, 2009 1:06PM

I'll give you my perspective. I believe that pages should always be designed and tested as though the next person that walks through that door or uses that page might be someone with a different disability than what you already have. The key is that the next person that needs this page might be that next great employee that you might let slip away if your pages can't deal with their disability. I know it's a challenge to cover all things but a page should do the very best it can to give all persons' with disabilities a chance to just maybe land that job because the pages are accessible. That's just my take.

-----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