
This is a fantastic rant from Thomas Fuchs on error messages and how to do them well (with lots of examples of how not to write error messages).
This is a fantastic rant from Thomas Fuchs on error messages and how to do them well (with lots of examples of how not to write error messages).
A nice overview of small screen design trends with backgrounds as to why these approaches work well.
There’s some really good forms advice in here. Just be careful when manipulating the tab flow.
I’ve talked about this before: As web designers, we can’t trust the network. Sure, we have to contend with mobile data “dead zones” and dropped connections as our users move about throughout the day, but there’s a lot more to the network that’s beyond our control.
Not on the form
. Noted.
Experiments in radio and checkbox resizing. It’s a sad state of affairs. The small hit targets are why I recommend adding negative margins above and below the label
, coupled with equal padding top and bottom. It’s a recommendation from my forms talk that I will write up soon.
A cheeky fictional conversation about progressive enhancement, though I might take it a bit further: If you want to edit the rich document and JavaScript enhancements aren’t available, there’s always Markdown or Textile or any other plain text pseudo-formatting language. Where there’s a will…
This is a fantastic overview of the accessibility considerations you should be making. Most are far more important than screen reader support.
New ES6 (ECMAScript 2015) features rolling out in V8: spread
and new.target
. Also: Reduced jank.
Jen Simmons and I discuss working on the web and all things progressive enhancement.