All articles can be read in a structured order, staring with the context of this reasearch, followed by the things I did and created, and ending with recommendations.
-
Introduction
-
Everybody’s paradox
The reason why the web is accessible is because it was designed to be used by everyone. The reason why the web isn’t accessible is the same.
-
The defaults suck
Could it be that the web is broken because the defaults our tools use are not very well designed?
-
Flipping things
Inclusive Design as practiced on the web right now could be a nice end goal, but I do think we are not there yet.
-
Fuckup’s mama
Tales of guessing how people use their computers. And then, of course, getting it all wrong.
-
More death to more bullshit
Screen readers tend to talk a lot. Which becomes increasingly annoying with more content. A recalibration of our love for features would be very welcome.
-
Design like it’s 1999
In which Simon Dogger and I wonder why it’s so hard to use the website with all Dutch national television documentaries.
-
Invisible Animations
In which I tell about the tailor made website and the giggling animations I made for Hannes Wallrafen, the famous blind photographer.
-
Semantics schmemantics
In which I explain the contrast between web development best practices, and the way our tools present them.
-
Stress cases
Edge cases in software development means that you use the extremes to test with. In Web design it means you ignore the extremes. Calling them stress cases might help.
-
Coders should learn how to design
We’re developing expertise in choosing rather than in thinking. If we want an accessible web, we need to start designing.
-
Add nonsense
Add nonsense, for fun, for surprise, and because we really need to innovate.
-
Conclusion
In which I try to reach a conclusion.