W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > January to March 2002

on the future: was: Re: forms problem

From: David Poehlman <poehlman1@home.com>
Date: Tue, 15 Jan 2002 09:12:26 -0500
Message-ID: <010d01c19dce$a95ad290$c2f20141@cp286066a>
To: <David.Cobb@rnib.org.uk>, <DPawson@rnib.org.uk>, <w3c-wai-ig@w3.org>
We are always looking towards the future, but a flaw in this until thing
is that it seems to me not to be explicit enough in that just because
something is possible does not mean that it will be done.  In other
words, it goes back to the old question of whether or not I should
implement something because the latest and greatest and a narrow
selection of those makes it possible?  We have to maintain a
groundedness in the current reality even in the future in which it takes
a long time for the world to catch up.  So, in my view, we should look
at "untill" to mean. "untill user agents that ... become prevalent"

----- Original Message -----
From: <David.Cobb@rnib.org.uk>
To: <poehlman1@home.com>; <DPawson@rnib.org.uk>; <w3c-wai-ig@w3.org>
Sent: Tuesday, January 15, 2002 8:49 AM
Subject: RE: forms problem


Just to re-iterate what was originally mentioned regarding pop-ups...

Checkpoint 10.1 states '... do not cause pop-ups or other windows to
appear
...'
Surely this implies that we shouldn't be using pop-up windows at all!?

I understand that this is one guideline that is 'until user agents
allow',
if future browsers enable users to disable spawned windows, then having
any
content in a pop-up window is not a feasible solution?

Regards

Dave Cobb

-----Original Message-----
From: David Poehlman [mailto:poehlman1@home.com]
Sent: 15 January 2002 13:21
To: DPawson@rnib.org.uk; w3c-wai-ig@w3.org
Subject: Re: forms problem


I would suggest that the site be designed so that this is minimized so
for instance, if you want instructions on how to use the form, that is
what you get,  you can put a link to the help from the form and a link
to the form from the help and do some other things to minimize
navigation problems but the fact is that if people don't learn how to
use their browsers to go back and forth between pages, they are going to
have trouble just about everywhere.

----- Original Message -----
From: <DPawson@rnib.org.uk>
To: <poehlman1@home.com>; <w3c-wai-ig@w3.org>
Sent: Tuesday, January 15, 2002 8:18 AM
Subject: RE: forms problem


thanks David.
What about the navigation problems, flicking back and forward?
How much of an issue do you perceive that to be for a new user?

Regards DaveP



> in that case, onclick would be a joy and many other things would be
> solved.  From my years of use on the web and with forms in
> particular, I
> find the little examples spread through out the form to be quite
> helpful.  This can even be suplemented with a little tutorial
> on how to
> fill out the form that people can look at before they fill
> out the form
> as many times as they wish.  you can put the tutorial into several
> formats one of them being flash so that the graphical user
> can take full
> advantage of it.  In some ways, this is an intrieguing question as it
> brings up a whole host of other questions that we have
> discussed in some
> form or another on this list before.  This is a situation
> which is going
> to cause problems or dissatisfaction for some no matter what you do so
> what can be done to minimize access barriers?  The answer is that if a
> help is required, treat it like help.  On this page, there is a form.
> to recieve instructions on filling in this form, go to the
> help page and
> then return to fill in the form.  the form can link to the
> help page and
> vice versa and have little examples through it so that the swift don't
> have to slow down too much.


-

NOTICE: The information contained in this email and any attachments is
confidential and may be legally privileged. If you are not the
intended recipient you are hereby notified that you must not use,
disclose, distribute, copy, print or rely on this email's content. If
you are not the intended recipient, please notify the sender
immediately and then delete the email and any attachments from your
system.

RNIB has made strenuous efforts to ensure that emails and any
attachments generated by its staff are free from viruses. However, it
cannot accept any responsibility for any viruses which are
transmitted. We therefore recommend you scan all attachments.

Please note that the statements and views expressed in this email
and any attachments are those of the author and do not necessarily
represent those of RNIB.

RNIB Registered Charity Number: 226227

Website: http://www.rnib.org.uk



-

NOTICE: The information contained in this email and any attachments is
confidential and may be legally privileged. If you are not the
intended recipient you are hereby notified that you must not use,
disclose, distribute, copy, print or rely on this email's content. If
you are not the intended recipient, please notify the sender
immediately and then delete the email and any attachments from your
system.

RNIB has made strenuous efforts to ensure that emails and any
attachments generated by its staff are free from viruses. However, it
cannot accept any responsibility for any viruses which are
transmitted. We therefore recommend you scan all attachments.

Please note that the statements and views expressed in this email
and any attachments are those of the author and do not necessarily
represent those of RNIB.

RNIB Registered Charity Number: 226227

Website: http://www.rnib.org.uk
Received on Tuesday, 15 January 2002 09:12:28 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 19 July 2011 18:14:00 GMT