Re: javascript accessibility

> I don't entirely agree with this. I view JavaScript as a
> means to provide convenience rather than exclusive function.

It's not convenient to write out parts of a document if they are crucial but
not present for UAs being not capable of or not using JS. It's bad coding
style, too.

> However one of the most accessible ways I know to do it is
> have JavaScript generate the elements which are providing
> that functionality.

It's a difference whether you /generate/ them (elements) or whether you
/hide/ them until a specific event occurs (e.g., via CSS). The latter is
more elegant (though not inevitably good), so I disagree. (My conclusion is
a bit global, but generally applies.)

> For example if you have a button which links to
> javascript.this.print(); then if it is also generated with
> JavaScript only the people able to use it will have it
> included in their content.

Well, if you use JS to offer functionality only available with JS, it might
be okay (if you really limit your scripting efforts to this specific action
and don't 'generate' all buttons with JS, for example). By the way, this
example 'limps' since you seem to copy browser functionality.

> In this way I think it is
> extremely valid to provide redundant or more convenient
> functionality which is also provided by some other server
> or user agent function.

I disagree. It might be pretty convenient if you can print a document
pressing one of fifty buttons available in a document, but hence, what do
you print? (I exaggerate, I know.) -- And 'valid' are many approaches in Web
development (though not most right now), but that doesn't mean they are
useful or reasonable.


Best regards,
 Jens.


-- 
Jens Meiert
Interface Architect (IxD)

http://meiert.com/

Received on Friday, 23 April 2004 04:26:43 UTC