- From: Shara Bunis <sbunis@MAIL.NYSED.GOV>
- Date: Tue, 09 Nov 1999 10:34:09 -0500
- To: <kynn@idyllmtn.com>, <w3c-wai-ig@w3.org>
I have been a listener on this list for a long time. This is my first foray into actually interacting. I am doing so because I think that Kynn is right on target! I am a government employee that heads up Web accessibility at both the state and agency level. My goal is for people to follow the Guidelines as best as they can, but more than that, to strive for accessibility as a true, integrated concept. It is important to keep the balance between innovation, resources and accessibility. Often, if you strive for perfection before moving forward, you will always stand still! Our 'solution' to the problem of, 'What if I can't make it accessible?', is to acknowledge the problem upfront, which will hopefully avoid aggravation on the users part, and to direct them to the next best remedy for that given situation. I think that we need to think about accessibility as being proactive, not reactive. This is not about what we can't do, but what we can do. >>> Kynn Bartlett <kynn@idyllmtn.com> 11/08 9:26 PM >>> At about 1 hour 50 minutes into the webcast of the InterLab accessibility panel, a member of the audience asked an interesting question, "I can interpret some of what you have said to mean that we should stop this video transmission right now -- we have no signer, we have no text. How do you make those judgments?" It brought up an intriguing quandry -- should we refuse to do something, if it cannot be done accessibly? (In this case, there were no funds available to hire real-time transcription or even after-the-fact transcriptions.) Should SLAC have decided not to webcast in that case? Some people would argue "if you can't do it accessibly, you shouldn't do it." I'm not sure I agree with that. Mainly because of how I define accessibility. The way I see it is that any given web service is going to have a potential audience of a given size -- and the percentage of potential users who can use that service will range from 0% to 100%. The GOAL of accessible web design is to MAXIMIZE THE PERCENTAGE OF POTENTIAL AUDIENCE MEMBERS WHO ARE ABLE TO USE THE SERVICE. (Caps to make it stand out, not because I'm shouting.) By that reasoning, ANY CHANGE WHICH INCREASES THE PERCENTAGE IS A STEP TOWARDS ACCESSIBILITY, and conversely, ANY CHANCE WITH DECREASES THE PERCENTAGE IS A STEP AWAY. Applying this to the case in question, let's say that only 50% of the potential audience could use the Real Video file. The other half don't have a compatible viewer, or they can't hear, or they can't see, or they don't have a computer (cell phone, PDA, etc), or any other reason. If we turn off the web cast, the number of people who can access that service goes from 50% to 0%. This is not a step towards accessibility, my friends -- in fact, it's the opposite. TURNING OFF THE WEBCAST WOULD DECREASE ACCESSIBILITY. We need to be careful, when we make mandates about accessibility, that we are not saying "do it this way OR ELSE" -- because then we lead to an overall net effect in which accessibility is decreased. Our goal should always, *always* be to promote changes which increase accessibility, which means INCREASING the number of potential audience members who can use a service, and never to DECREASE that number. Agree or disagree? -- Kynn Bartlett <kynn@idyllmtn.com> http://www.kynn.com/ Chief Technologist, Idyll Mountain Internet http://www.idyllmtn.com/ Next Speaking Stop: New Orleans, 9 Dec 99 http://www.builder.com/live/ CC/PP Builds the Future of the Web --> learn more at http://www.ccpp.org/
Received on Tuesday, 9 November 1999 10:36:44 UTC