Eileen Webb on the accessibility issues created by “modern” storytelling on the web:
The issue usually isn’t the motion itself, or the existence of animation. The problem is a mismatch between my expectations for what I’m going to encounter on a webpage and what actually displays on that page.
She documents a handful of real issues and shows you how to resolve or at least mitigate them. She’s also included a bunch of real world examples of “dos” and “don’ts”. It’s well worth a read.
I love posts like this that get into the nitty-gritty detail of seemingly simple undertakings like updating a site’s font stack, especially one based on system fonts! There’s a lot to learn from this post and it’s well worth your time.
This excellent piece breaks down many of the issues around what it means (in the larger, societal sense) to store information digitally.
In the 21st century, more and more information is “born digital” and will stay that way, prone to decay or disappearance as servers, software, Web technologies, and computer languages break down. The task of internet archivists has developed a significance far beyond what anyone could have imagined in 2001, when the Internet Archive first cranked up the Wayback Machine and began collecting Web pages…
What I want is a way that both sides can get what they want: companies and projects can be data-driven, and users don’t get their privacy compromised.
Amen.
This is an excellent round up of excellent naming recommendations for writing more readable code.
I agree with pretty much every one of the recommendations here, but I’d argue that generating the JS-requiring button with JavaScript is a far better approach.
This is an excellent case study from Alice Lee on making Wordpress’ branding illustrations more inclusive.
Kelly, Oscar, and I are getting ready to head out for a long weekend up in Gatlinburg, TN to take a break from house selling insanity and kick off the celebration of our 16-year anniversary. We love the Fall, but not everyone is equipped to take in the awesome beauty of Fall foliage. Thankfully, Tennessee is doing something about that.
disabled or readonly?Web forms are complex beasts. There are a lot of field types to remember, each with dozens of attributes. It’s hard to know which is the right way to go, especially when presented with a choice between two seemingly similar options for disallowing a field to be edited: disabled and readonly. TL;DR: If you really need it, which you probably don’t, readonly is what you want.
This is an excellent roll-up of coding best practices from Brandon Gregory.