![\"Input](\"https:\/\/html5accessibility.com\/stuff\/wp-content\/uploads\/2021\/02\/placeholder.png\")
<\/h2>\n<\/h2>\nThe reasons why use of the I first wrote about \u26a0\ufe0f Use of the placeholder attribute as a replacement for a label can reduce the accessibility and usability of the control for a range of users including older users and users with cognitive, mobility, fine motor skill or vision impairments. While the hint given by the controls label is shown at all times, the short hint given in the placeholder attribute is only shown before the user enters a value. Furthermore, placeholder text may be mistaken for a pre-filled value, and as commonly implemented the default color of the placeholder text provides insufficient contrast and the lack of a separate visible label reduces the size of the hit region available for setting focus on the control.<\/p><\/blockquote>\n Unfortunately for some, the obvious and oft-stated usability\/accessibility crapness<\/em> of The question:<\/strong><\/p>\n ?To conform to 3.3.2 Labels or Instructions (WCAG 2.1 A) does a label have to be present regardless of the state of a control? \/cc @patrick_h_lauke<\/a><\/p>\n \u2014 Steve Faulkner (@stevefaulkner) February 19, 2019<\/a><\/p><\/blockquote>\nplaceholder<\/code> attribute as the only means of providing a user readable prompt for a form control is deficient UX<\/em>, are voluminous<\/a>. It is frustrating having to rehash this discussion endlessly<\/em>.<\/p>\nplaceholder<\/code><\/a> back in 2011, and included a note<\/a>, later a warning<\/a>, about its use in the dear superseded<\/em> HTML5 specification in 2014.<\/p>\nplaceholder<\/code> as label is not reason enough to avoid using it as a label.<\/p>\n“Show us the fail” they ask:<\/h2>\n
\n