Databases
StackOverflow2013
Postsdbo
POShould we put <input> inside <label>?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POShould we put <input> inside <label>?
    primarykey
    data
    text
    <p>I saw 2 different method on same form example:</p> <p>on <a href="http://www.alistapart.com/articles/prettyaccessibleforms/" rel="noreferrer">http://www.alistapart.com/articles/prettyaccessibleforms/</a> why they are using 2 method in first <code>fieldset</code> they are keeping <code>input</code> after <code>label</code>and in 2nd <code>fieldset</code> they are keeping <code>input</code> after <code>label</code>. Why?</p> <pre><code>&lt;fieldset&gt; &lt;legend&gt;Delivery Details&lt;/legend&gt; &lt;ol&gt; &lt;li&gt; &lt;label for="name"&gt;Name&lt;em&gt;*&lt;/em&gt;&lt;/label&gt; &lt;input id="name" /&gt; &lt;/li&gt; &lt;li&gt; &lt;label for="address1"&gt;Address&lt;em&gt;*&lt;/em&gt;&lt;/label&gt; &lt;input id="address1" /&gt; &lt;/li&gt; &lt;li&gt; &lt;label for="address2"&gt;Address 2&lt;/label&gt; &lt;input id="address2" /&gt; &lt;/li&gt; &lt;li&gt; &lt;label for="town-city"&gt;Town/City&lt;/label&gt; &lt;input id="town-city" /&gt; &lt;/li&gt; &lt;li&gt; &lt;label for="county"&gt;County&lt;em&gt;*&lt;/em&gt;&lt;/label&gt; &lt;input id="county" /&gt; &lt;/li&gt; &lt;li&gt; &lt;label for="postcode"&gt;Postcode&lt;em&gt;*&lt;/em&gt;&lt;/label&gt; &lt;input id="postcode" /&gt; &lt;/li&gt; &lt;li&gt; &lt;fieldset&gt; &lt;legend&gt;Is this address also your invoice » address?&lt;em&gt;*&lt;/em&gt;&lt;/legend&gt; &lt;label&gt;&lt;input type="radio" » name="invoice-address" /&gt; Yes&lt;/label&gt; &lt;label&gt;&lt;input type="radio" » name="invoice-address" /&gt; No&lt;/label&gt; &lt;/fieldset&gt; &lt;/li&gt; &lt;/ol&gt; &lt;/fieldset&gt; </code></pre> <p>why they are sometime keeping <code>input</code> after <code>label</code> and sometime inside?</p> <p>Update:</p> <p>here <a href="http://www.usability.com.au/resources/forms.cfm" rel="noreferrer">http://www.usability.com.au/resources/forms.cfm</a> they are also keeping <code>input</code> after <code>label</code> not inside</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USJitendra Vyas
    1. USJitendra Vyas
    plurals
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTDuplicate
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POShould we put <input> inside <label>?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POShould we put <input> inside <label>?
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POShould we put <input> inside <label>?
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThe link you added tells you the reason for not using implicit labels: "Until user agents support explicit associations between labels and form controls, for all form controls with implicitly associated labels ensure that the label is properly positioned." Web Content Accessibility Guideline Checkpoint 10.2" Some impaired people still hold on to their old screen readers, so you're better off using explicit labels.
      singulars
      1. POShould we put <input> inside <label>?
      1. USGert Grenander
    2. CO@Gert G - yes you are right
      singulars
      1. POShould we put <input> inside <label>?
      1. USJitendra Vyas
    3. CO@Jørn Schou-Rode - oh yes same question
      singulars
      1. POShould we put <input> inside <label>?
      1. USJitendra Vyas
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload