Yes, this blog supports CSS Naked Day.
Not only is it a hip meme to join along – yes, I follow the crowd sometimes – it’s also a good way to force myself to ensure my blog is reasonably well-designed in terms of output and structure.
More importantly, it’s crucial to realize that not everyone can see. Whether it’s language, color, bandwidth or choice (i.e. using a text-only browser), or personal choice of stylesheets, it’s nice to allow your readers to see things their own way. But it’s even more important to provide your content for people who actually can’t see.
I’ve always tried to provide for that, and recently working closely on a team with someone who is blind reinforced that. It was also quite amazing both to see how they thought, as well as to see the different way they read pages, even ones that you thought were accessible. There were a number of websites that he could read, but that didn’t make as much sense as they should, mostly because of layout (not just CSS) that made sense on the screen, but doesn’t quite make sense in the reader. Even basic attempts to include accessibility in your sites is really appreciated.
The really amazing co-worker is one who works on compiler design. I find it hard enough to understand how modern compilers work, and I can see the architectural diagrams, and quickly scroll up and down the stack of tokens and layers. Imagine not just understanding a compiler, but building a new one when you’re blind – and to some degree only have sequential access to data. Now, that is an organized mind.
Read more about accessibility in software at IBM’s ABLE site.