Our registration form wizard used a mix of inaccessible default browser error messages and ambiguous custom form validation messages in red text.
Tag: HTML
Proper document markup. Separating structure from presentation and behavior. The lowercase semantic web. Building accessible, cross-platform, cross-browser pages. Using web standards correctly. HTML evolves into a language built for applications, not just documents. New semantics. Responsive images and other conundrums. Canvas and accessibility. Audio, video, and fallbacks. The politics of HTML: WHAT WG and the W3C.
When and where to set input spellcheck =false
A form will spellcheck your name, email and postal address, giving false positives. I’ll share how I tweak this for a less jarring form-filling experience.
Identify input purpose for awesome usability and accessibility
Identify input purpose (autocomplete values) makes easier and faster form filling experiences for everyone entering personal or payment information.
Input width makes it easy to guide sighted users
Setting input width to guide sighted users reduces cognitive effort needed to fill out forms. I’ve created HTML and CSS code to set width of a postcode field.