|
|
Posted by dorayme on 10/04/07 22:28
In article <mhjag313qv2bgeosk322d9083maov83v6d@4ax.com>,
Andy Dingley <dingbat@codesmiths.com> wrote:
> On Thu, 04 Oct 2007 11:48:11 -0700, Animesh K <animesh1978@gmail.com>
> wrote:
>
> >OOT, what is a good site to know about accessibility features? I presume
> >w3 must be having something.
>
> You presume wrongly, sad to say. The W3C efforts here have been
> pitiful.
>
> The best resource is Joe Clark's site, and his excellent accessibility
> book. This both puts the case for it, and explains the techniques to
> achieve it. Best of all, the full text is online for free
> http://joeclark.org/book/sashay/serialization/
Good one. Out of the many positive things which speak for
themselves, I was reminded of something that is an irritating
design fault, which this url is a very very mild case of. It is
tiresome to be having to click next buttons when you want to
simply read a lot of an article on line. It is a mild case
becaiuse to be fair to the designer, he provides a fair chunk.
Sites like How Stuff Work are infuriating in this regard, and
there are many others as bad or worse. I can understand placing
limits for bandwidth where there are a lot of pictures.
Basically, with text articles there should be more generous
limits before user *has* to press buttons. There are some very
useful devices I use to go up and down, scroll wheels, up and
down arrows on keyboard, page up and down buttons. Easier than
the *interruptions* from locating visual buttons and clicking.
At the very least, authors might consider providing a facility
where the whole of an article can be read on line by simple
scrolling. Authors often provide a print version, they might
consider more often providing a "continuous" online version for
those who would like such.
(I have not read the URL here completely, I do not know if author
raises this matter? As I say, his is a very minor irritation, I
might be a little unusual in this regard? But thegeneral point I
make is good.)
--
dorayme
Navigation:
[Reply to this message]
|