W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > October to December 2001

Re: Combining Server/Client-side techniques for accessibility

From: Jim Ley <jim@jibbering.com>
Date: Sun, 21 Oct 2001 17:39:38 +0100
Message-ID: <013601c15a53$ecc1e500$763c70c2@7020CT>
To: <w3c-wai-eo@w3.org>
Cc: <w3c-wai-gl@w3.org>
bill@eramp.com wrote:
> I agree with Chuck's solution. Defaulting to client processing but
> providing "slide-ability" of that functionality up to the server when
necessary
> can (depending on the script) often be as simple as combining browser
sniffing

Browser Sniffing? this is an impossibility, there are no mechanisms (until
(if) CC/PP becomes available) the HTTP_USERAGENT is not appropriate for
this.  As you seem to be suggesting ASP, then hopefully by now the
relevant Microsoft Knowledge Base Articles have added a disclaimer that
this doesn't work even for "standard" browsers, let alone issues like
browser configuration (no images, no script etc. etc.) or Accessibility
technology based on top of them.  For example Jaws for Windows, makes
IE5.5's capabilities radically different.

> Why not design the scripted functionality with client-side techniques
that
> will be used by the vast majority of visitors to the site (i.e. those
whose
> user agents do support and who can access client-side services).  Then,
> instead of making the accessible "fall-back" a non-scripted alternative,
> make it a call to an equivalent server-side script.

The majority of uses for client-side scripting either already have server
duplication (form validation), or are not duplicatable in the server
(popup menus, rollovers, etc. etc.)

> By the way, please don't ask me to provide you with a real example of
this
> suggestion.  I don't have one.  I would be really happy if someone who
is
> knowledgeable in both server- and client-side programming techniques
could
> try this and report back to us (and probably the WCAG group).

Just about every form, on any page has form validation with server side
validation aswell as client (if it doesn't then the server has a
problem...)

Jim.
Received on Sunday, 21 October 2001 13:14:15 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:47:16 GMT