Demo site should associate labels with text inputs

[scottaohara]

As discussed in #24, ids are not necessary to associate labels with their form controls, as long as those form controls are contained within the label. However, if a label is not a parent for its form control, then the label should have a for attribute, pointing to the unique id of the element it is providing the accessible name to.

The text fields on the demo site would fall into this pattern.

[BcRikko]

Does this mean? ↓ 🤔

Unnecessary

<label>
  Input field
  <input type="text" class="input">
</label>

Necessary

<label for="input_field">Input field</label>
<input type="text" class="input" id="input_field">

That's right, I did not know. 😆

Do you know best practices for not duplicating IDs?
Would you teach me for my future? 🙏

[scottaohara]

We can have a side conversation sometime about this, yes

[BcRikko]

🎉 This issue has been resolved in version 1.0.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀