Home
Bookmarks
Leagues
LEARN
Courses
Career Paths
Assessments
Tutorials
Arcade
Glossary
GROW
Certifications
Log in
Glossary
Log inSign up
Courses/Accessible Interface Foundations/Meaning before appearance/
Exercise #5

Form Labels: Why Placeholders Are Not Labels

A rampant web design antipattern is omitting <label> elements and using the placeholder attribute instead to create a 'clean, minimal' form input.

Why Placeholders Fail Accessibility and Usability:

  1. They Disappear on Focus: The moment a user types one letter, the placeholder vanishes. Users with cognitive disabilities, memory impairments, or distractions forget what field they are editing.
  2. Poor Color Contrast: Most default browser placeholder text fails the WCAG 4.5:1 color contrast ratio requirement.
  3. Inconsistent Screen Reader Support: Many screen readers do not announce placeholders as accessible names.

The Bulletproof Standard: Always use an explicit <label for="email-input">Email Address</label> bound programmatically to <input id="email-input">. Clicking the label also expands the click target by focusing the input!

Topics

Structure Carries Meaning: The Accessibility Tree
The Non-Negotiable Rule: Buttons vs Links
Document Outline: The Sacred Heading Hierarchy
Landmark Regions: Navigating Page Architecture
Form Labels: Why Placeholders Are Not Labels
The Alt Text Decision Tree: Informative vs Decorative
Lists as Navigation & Content Containers
The First Rule of ARIA: Do Not Use ARIA
Tabular Data: Making Tables Comprehensible
Master Challenge: Refactoring a 'Div-Soup' Component

From lesson

1

Meaning before appearance

Level 1 · Accessible interaction basics

Top contributors

Community contribution details will appear here once real learner activity is available.

Share