Re: ClickZ network article

>>Because, and is evidanced here many times, accessibility = screen
>> readers.
>
> I often come across the misconception: accessibility = catering for the
> "blind guy
> in the corner there".
>
Yes but I meant more that screen readers are the only thing that we need
to be able to support with accessible code.  Not necessarily that it is
for the blind guy.  But you show what I mean in your next para.

>>Why, is this?  Do we send the wrong message by using screen readers as
>> the first, and many times, only example of why pages may be
>> inaccessible?
>
> Of course we need to expand our examples when talking about
> accessibility. In the vein of the quaint shock tactic of taking away a
> user's mouse and asking them
> to navigate the site, I often turn people's speakers off and direct them
> to their
> wonderful corporate video section on their site - which is sorely
> lacking transcripts,
> captions, etc.
>
I like these tactics.... Nothing drives the point home then being able to
demonstrate the problems first hand.

> I might be wrong, but I think part of the problem is also that - from
> what I've seen,
> anyway - organisations such as the RNIB are the most vocal when it comes
> to banging the drum of accessibility...thus further strengthening the
> perception that it's
> all about catering for visually impaired visitors. Maybe part of the
> solution would be
> for other orgs, like the RNID,  to speak up more with regards to access
> needs of
> the particular group they represent.
>
An interesting point here.  I wonder if the lack of support for captions
is because of the closed nature of the deaf community?

> Just rambling thoughts before I've had my cup of coffee...
>
> Patrick

And I puttering around on here because I cant sleep tonight.
LOL

-Steve

Received on Tuesday, 8 June 2004 03:56:47 UTC