KodingKaro
CSS · Intermediate · Forms and UI Styling

Form control states and labels

Form styling should clarify what a field expects without hiding the label or the control’s state.

✓ What you will learn in this topic

  • Explain the key idea: Preserve labels, recognizable controls, and clear interaction states.
  • Apply the concept: The field has a clear boundary and a visible focus ring when reached by keyboard.
  • Avoid this common mistake:

Concept explanation

Style inputs by type or a component class. The label should remain visible and be programmatically associated with its control in HTML. Use :focus-visible for a clear keyboard state and distinguish disabled or invalid fields without relying only on a faint color change.

Native controls differ across platforms. Styling should improve consistency without removing familiar affordances or reducing usability.

Syntax

A CSS rule has a selector followed by declarations. Each declaration is a property and a value; the braces group the declarations that apply to matching elements.

.demo input {
  width: 100%;
  padding: 0.75rem;
  border: 1px solid #94a3b8;
  border-radius: 0.5rem;
}
.demo input:focus-visible {
  outline: 3px solid #93c5fd;
}

Example 1: a small page element

Use this HTML as the target and place the CSS in a stylesheet linked to the page, or inside a <style> element while experimenting.

<main class="demo card-grid course-grid dashboard-panel course-card-list dashboard-grid card-layout"><h2>Learning card</h2><p>Clear styles make this information easier to scan.</p><nav class="site-nav"><a href="/learn">Courses</a></nav><label class="form-field"><span>Email</span><input type="email" aria-invalid="true"></label><article class="card course-card dashboard-card theme-dark"><span class="badge status">New</span><div class="course-card__image"></div><h2 class="course-card__title card__title">Course update</h2><p class="status">New lessons are available this week.</p><a href="/learn" aria-current="page">Read the details</a><div class="actions course-card__actions dashboard-panel__actions"><button type="button">View lessons</button><button type="button" disabled>Unavailable</button></div></article></main>
.demo input {
  width: 100%;
  padding: 0.75rem;
  border: 1px solid #94a3b8;
  border-radius: 0.5rem;
}
.demo input:focus-visible {
  outline: 3px solid #93c5fd;
}

Expected result: The field has a clear boundary and a visible focus ring when reached by keyboard.

Example 2: a practical interface card

The same idea can style a reusable card on a course page. The class selector keeps the rule attached to this component rather than changing every element of that type.

<section class="demo card-grid course-grid dashboard-panel course-card-list dashboard-grid card-layout"><h2>Learning card</h2><p>Clear styles make this information easier to scan.</p><nav class="site-nav"><a href="/learn">Courses</a></nav><label class="form-field"><span>Email</span><input type="email" aria-invalid="true"></label><article class="card course-card dashboard-card theme-dark"><span class="badge status">New</span><div class="course-card__image"></div><h2 class="course-card__title card__title">Course update</h2><p class="status">New lessons are available this week.</p><a href="/learn" aria-current="page">Read the details</a><div class="actions course-card__actions dashboard-panel__actions"><button type="button">View lessons</button><button type="button" disabled>Unavailable</button></div></article></section>
.form-field input:focus-visible {
  border-color: #1d4ed8;
  outline: 3px solid rgb(29 78 216 / 25%);
  outline-offset: 2px;
}

Expected result: The course update reads as a distinct interface card, and its content follows the spacing, color, and layout choices in the rule.

Common mistake

Removing native control affordances or using placeholder text as the only label.

Best practice

Keep explicit labels, visible focus, clear error text, and adequate target sizes; test native controls on real browsers.

Practice exercise

Build a sign-up form with labeled fields, a visible focus state, and an error message that is not communicated by color alone. Apply it to the example above and inspect the result at a narrow and a wide viewport.

Section summary

  • Preserve labels, recognizable controls, and clear interaction states.
  • Keep explicit labels, visible focus, clear error text, and adequate target sizes; test native controls on real browsers.

Knowledge check

What is the role of a visible field label?

Reveal the explanation

Labels identify fields; placeholders can disappear and should not be the only instruction.

Finish the module lessons, then take the server-scored module quiz to check your understanding.

Practical example

css
.demo input {
  width: 100%;
  padding: 0.75rem;
  border: 1px solid #94a3b8;
  border-radius: 0.5rem;
}
.demo input:focus-visible {
  outline: 3px solid #93c5fd;
}

Expected result:

The field has a clear boundary and a visible focus ring when reached by keyboard.

Hands-on practice task

Build a sign-up form with labeled fields, a visible focus state, and an error message that is not communicated by color alone.

In this section

Other lessons in Forms and UI Styling

Broaden your knowledge

Related learning topics