Ethan ponders what the web might be like if the kind of legal sticks that exist for accessibility in some countries also existed for performance.
Thursday, November 8th, 2018
Monday, September 10th, 2018
Robustness and least power
There’s a great article by Steven Garrity over on A List Apart called Design with Difficult Data. It runs through the advantages of using unusual content to stress-test interfaces, referencing Postel’s Law, AKA the robustness principle:
Be conservative in what you send, be liberal in what you accept.
Even though the robustness principle was formulated for packet-switching, I see it at work in all sorts of disciplines, including design. A good example is in best practices for designing forms:
Every field you ask users to fill out requires some effort. The more effort is needed to fill out a form, the less likely users will complete the form. That’s why the foundational rule of form design is shorter is better — get rid of all inessential fields.
In other words, be conservative in the number of form fields you send to users. But then, when it comes to users filling in those fields:
It’s very common for a few variations of an answer to a question to be possible; for example, when a form asks users to provide information about their state, and a user responds by typing their state’s abbreviation instead of the full name (for example, CA instead of California). The form should accept both formats, and it’s the developer job to convert the data into a consistent format.
In other words, be liberal in what you accept from users.
I find the robustness principle to be an immensely powerful way of figuring out how to approach many design problems. When it comes to figuring out what specific tools or technologies to use, there’s an equally useful principle: the rule of least power:
Choose the least powerful language suitable for a given purpose.
On the face of it, this sounds counter-intuitive; why forego a powerful technology in favour of something less powerful?
Well, power comes with a price. Powerful technologies tend to be more complex, which means they can be trickier to use and trickier to swap out later.
In the web front-end stack — HTML, CSS, JS, and ARIA — if you can solve a problem with a simpler solution lower in the stack, you should. It’s less fragile, more foolproof, and just works.
- Instead of using ARIA to give a certain
rolevalue to a
span, try to use a more suitable HTML element instead.
It sounds a lot like the KISS principle: Keep It Simple, Stupid. But whereas the KISS principle can be applied within a specific technology—like keeping your CSS manageable—the rule of least power is all about evaluating technology; choosing the most appropriate technology for the task at hand.
There are some associated principles, like YAGNI: You Ain’t Gonna Need It. That helps you avoid picking a technology that’s too powerful for your current needs, but which might be suitable in the future: premature optimisation. Or, as Rachel put it, stop solving problems you don’t yet have:
So make sure every bit of code added to your project is there for a reason you can explain, not just because it is part of some standard toolkit or boilerplate.
There’s no shortage of principles, laws, and rules out there, and I find many of them very useful, but if I had to pick just two that are particularly applicable to my work, they would be the robustness principle and the rule of least of power.
After all, if they’re good enough for Tim Berners-Lee…
Tuesday, August 21st, 2018
A deep, deep dive into biomicry in digital design.
Nature is our outsourced research and development department. Observing problems solved by nature can help inform how we approach problems in digital design. Nature doesn’t like arbitrary features. It finds a way to shed unnecessary elements in advancing long-term goals over vast systems.
Thursday, April 12th, 2018
Dave has curated a handy list of eponymous laws.
Tuesday, January 16th, 2018
- Fitts’s Law
- Hick’s Law
- Jakob’s Law
- Law of Prägnanz
- Law of Proximity
- Miller’s Law
- Parkinson’s Law
- Serial Position Effect
- Tesler’s Law
- Van Restorff Effect
- Murphy’s Law
- Sturgeon’s Law
Wednesday, January 3rd, 2018
Tuesday, January 26th, 2016
Remember when I mentioned that you can get free certificates from Amazon now? Well, Oliver has written an in-depth step-by-step description of how he got his static site all set up with HTTPS.
More of this please! Share your experiences with moving to TLS—the more, the better.
Friday, January 22nd, 2016
If you’re hosting with Amazon, you now get HTTPS for free.
Tuesday, September 23rd, 2014
Léonie gives a great, clear description of how screen readers switch modes as they traverse the DOM snapshot.
Wednesday, April 10th, 2013
Keep it under your hat, but Paul has soft-launch his Project Portillo. And very nice it is too.
Friday, May 18th, 2012
Bravo, Bruce, bravo.
I heard Glen Campbell’s “Like A Rhinestone Cowboy” on the radio and began absent-mindedly singing “Like a rounded corner” to it.
Saturday, December 27th, 2008
Further proof, as if any were needed, that the patent system turns into a steaming pile of shit as soon as it has dealings with software.
Thursday, December 4th, 2008
Here's a depressing counterpoint to my feel-good story about Iron Man: someone else who's picture was used in the film (in good faith) decided to sic the lawyers on Jon Favreau.
Sunday, February 10th, 2008
Steve Faulkner gives a rundown of the current state of play between screen readers and Ajax.
Friday, February 2nd, 2007
Thursday, October 26th, 2006
Transcript: Where the rubber meets the road — Web Accessibility and Pragmatism / Geek in the Park 2006 / Bruce Lawson and Patrick H. Lauke / splintered - freelance creativity and design / the portfolio and experimental playground of patrick h. lauke aka
This transcript of Pat'n'Bruce's talk at the Geek in the Park makes for a great, thought-provoking read.