From a usability standpoint I believe that the description text should be shown between the Field Label and the Field itself.

As it currently stands the text is semantically after the Field which I assume means those using screen readers don't hear the text until after they have encountered the field negating it's use. (will be testing this tonight)

This is also relevant for sighted users, as most people don't read ahead when filling out forms.

Reference material:
http://www.slideshare.net/cxpartners/web-and-mobile-forms-design-userfri...
From slide 61

http://www.w3.org/TR/2008/WD-WCAG20-TECHS-20080430/H65.html
Suggests use of title element on input's

http://www.smashingmagazine.com/2011/04/06/fundamental-guidelines-of-e-c...
Section 2

Comments

lisarex’s picture

lisarex commented

+1 from me. This has been bugging me for a long time for exactly the reasons you mentioned (usability and accessibility). Currently, the flow is interrupted when the user fills out the field and then (possibly) notices the instructions underneath. They have to decide whether to stop and understand the instructions, then decide if they need to edit their entry in that field.

mpearrow’s picture

mpearrow commented

I agree with the assertion that it makes sense to use the description between the label and the field.

Additionally, I think this is a great example of how we could begin codifying design principles using principles, guidelines, empirical evidence, and concrete implementation samples to embody an Evidence-Based Usability standard.

Ideally the two slideshows would have been non-commercial sources (being able to see the research methodology and replicate the findings is critical).

yoroy’s picture

yoroy commented

Probably a duplicate of #314385: Make position of #description configurable via the API, but good to have some sources to backup the argument.
If @realityloop could put this original post in there as a comment we can continue over there.

realityloop’s picture

realityloop commented
Status: Active » Closed (duplicate)

While not technically a duplicate I think the discussion can still be moved to a single thread http://drupal.org/node/314385