A practical distraction for the standardistas and accessibility gurus…

Hoping tap your brain for an alternative perspective on the simple and
common HTML scenario of a site search form.
<fieldset>
        <legend>Search this site</legend>
        <label for="search">Keyword/s</label>
        <input type="text" id="search" name="search" />
        <input type="submit" value="Search" />
</fieldset>

As far as I understand it this mark-up meets the requirements demanded
of such a form.
Although, in striving for simplicity, there may be significant redundancy.

My question regards the HTML and text used:
How much mark-up can be removed without breaking it?

- FIeldset / legend combination are required to meet HTML standards
and provides valuable context to my mind.
Am I missing anything?

- Sacrifice the label and add a title attribute on the text input?
<fieldset>
        <legend>Search this site</legend>
        <input type="text" id="search" name="search" title="Keyword/s" />
        <input type="submit" value="Search" />
</fieldset>

- Once supported, will the new HTML5 placeholder attribute make the
label redundant
<fieldset>
        <legend>Search this site</legend>
        <input type="text" id="search" name="search" placeholder="Keyword/s" />
        <input type="submit" value="Search" />
</fieldset>

- How many users know that they can use the Enter key to submit the form?
<fieldset>
        <legend>Search this site</legend>
        <input type="text" id="search" name="search" placeholder="Keyword/s" />
</fieldset>

- The future?
<fieldset>
        <legend>Search this site</legend>
        <input type="search" id="search" name="search" placeholder="Keyword/s" 
/>
</fieldset>

Editable mark-up here
http://fixee.org/paste/bxmsvue/#url=bxmsvue

Redundancy can be a good thing, but where do you draw the line?
Looking forward to your considered thoughts and relevant experiences.

Cheers
Ollie
--
@ollicle


*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
*******************************************************************

Reply via email to