Replying to a tweet from @Una
- Kindred by Octavia Butler
- The Fifth Season by N.K. Jemisin
- Ancillary Justice by Ann Leckie
- The Calculating Stars by Mary Robinette Kowal
- The Power by Naomi Alderman
- The Future Home Of The Living God by Louise Erdrich
Thank you, Sebastian! Here are some links to the resources mentioned:
I think you’re conflating hamburger menus with progressive disclosure: one is a subset of the other. Saying any progressive disclosure pattern is basically a hamburger menu is like saying all animals are basically fish. 🍔 🦒 🦔 🦓 🐟
Here’s a nice example of showing pages offline. It’s subtly different from what I’m doing on my own site, which goes to show that there’s no one-size-fits-all recipe when it comes to offline strategies.
I really like this latest addition in Firefox to show how many tracking scripts are being blocked. I think it’s always good to make the invisible visible (one of the reasons why I like RequestMap so much).
HTML lets you create the structure of a website.
CSS lets you make the website look nice.
If you’re saying that a hamburger icon is a common convention, the data from usability testing disagrees.
But good point about the positioning of the close icon—I’ve fixed that now (the open/close trigger is persistent). Thanks for that!
I reckon a lot of websites have bad accessibility not because folks don’t care, but because they don’t know there’s an issue in the first place.
The headline is begging the question (I don’t think accessible websites are so hard to build), but I agree with Robin’s idea:
What if our text editors caught accessibility issues and showed them to us during development?
This is something that Hidde has been talking about recently too, looking at content management systems.