My Action Item: Multiple interface guideline

The general idea behind using the server to enhance accessibility is that
you can use logic running on the server to send content that is optimized
for the user in some way, rather than sending the same markup to all users
and letting the browser sort out what to do with it. At a very high level,
this is a an application of Guidelines 1 and 2, but at a page level rather
than an element level.

We discussed several techniques for accomplishing this at the F2F, which are
summarized in my last mail.  My action item dealt with a proposed guideline
that came out of that discussion.  

On further reflection, I think this is actually a checkpoint, and not a
guideline.  It could fit in GL 4 of GL 5.

Here's the scenario:

A site author could allow a user to pick from a variety of representations
of the same data:  a flash version of the content, a version rendered by
DHTML scripts, or a linear HTML 4.0 AAA Compliant version.  If, however, the
user picks the flash version, s/he must be able to get back to the other
versions whether or not s/he can access the flash version.  The control for
switching between versions must be accessible, even if the version the user
has selected is not.  

And here's the checkpoint:

x.x When multiple interfaces are provided for the same content, the
mechanism for switching between interfaces must be accessible and easy to
find.
NOTE: The switching mechanism must be accessible even if the currently
selected interface is not.  This ensures that a user who has selected it by
accident will be able to recover.


Thoughts and Comments?

--Cynthia

Received on Friday, 13 October 2000 01:20:16 UTC