5 minutes | Floating labels (future?) | Jeff Witt (Deactivated) | Issues with WCAG 2.1 support for autofill attribute Text box and input controls, floating labels, animation, no need for JS, placeholders for a11y were usually too light, most screen readers don't speak them, our solutions were fine Now WCAG 2.1 has an autofill, if we have a floating label, the autofill goes where placeholder should be and obscures readability Floating label thing might not be workable going forward. Can we explore a different pattern? priority level 3 a11y concern right now (we should prioritize, but no time urgency). Either solve the current floating label issue or create new design solution without floating labels Hint and error text ideally above the inputs instead of below [Adam] including both patterns for labels will avoid a breaking change [Jon] Clarity on error above input.
|