I am wondering if it is (already?) acceptable to omit the explicit
null option in a radio button control?
I have used radiobuttons for a non-required control. To apply the
null option the user would have to 'unselect' the one selected
radio button (this to save place by not adding a fourth radio button
or to not have to use a drop down control).
I suppose it is kind of an unusual behavior but it seems to me that
is is learnable, and I have seen it in product design. Has this kind
of behavior been introduced in forms before?
I'm about to go into a series of form redesigns within a section of
my company's corporate site. We've mandated that any new forms or
form redesigns should comply with WCAG 2.0 AA recommendations.
Most of the 2.0 criterion and techniques seem reasonably clear and
I'm not finding it too difficult to find examples of their
application, but I can't seem to locate a clear rule around the use
But they haven't really focused on what I'm after: your favorite examples
for having a person specify what country they live in, in the context of a
web form. Anyone come across a particularly effective way of collecting this
information recently (including consideration for accessibility)? Bonus
points if it does not involve a gigantic dropdown with ~ 195 countries in
I don’t think placement of action button for search form
with 2 or more search parameters has been discussed in the group yet. Everyone
in the group would have sometime worked to design search forms for intranets or
websites that have 2 or more search parameters. I find a lot of research on registration
forms but not on search forms. Luke has conducted great research on the registration
forms and the design of the forms.
Does anyone know of any data, or have an opinion, about laying out forms in
At my job, the business is constantly complaining about all the white space
on the right side of a long form when I lay it out in the standard way.
Arranging the labels and inputs into two columns, flowing from left to
right, seems an obvious solution to the problem.
As discussed by LukeW in Web Form Design, it's best to have the primary
action of a form be the first button that the user sees. For left-to-right
languages this means having the primary action on the left and any secondary
actions on the right (see A in this illustration http://www.flickr.com/photos/rosenfeldmedia/2366430953/ ).
Just wanted to make folks aware, I recently began work on a book for
Rosenfeld Media about Web Form Design. I hoping there's genuine
interest on this list in the topic as Interaction Designers deal with
forms A LOT.
As such, if you have experiences, ideas, or best practices to share
from your work -I'd be very interested in hearing from you. Either
float me a note directly, leave a comment on the book in progress
site, or subscribe to the RSS feed there to simply stay in the loop
I am working on a client project, where the client is gradually
transitioning forms on their site to use auto completion (w/ AJAX). I
would like to visually signal to users which form fields are auto
completing and which ones are "static". I am wondering if there is a
"pattern" for alerting to users this type of functionality. We can
create something for this client's purpose, but I would like leverage
any convention, if there is already one out there.