All Tags // standards
In light of Microsoft's plans (or is it just a proposal?) for browser version targeting, I decided to weigh-in on a more philosophical level. There are a lot of very smart people chiming in on this who are much closer to the situation than I am at a practical level. They are better equipped to speak to any implementation concerns. My concern rests at a higher (as in more abstract, not better) level.
Generally speaking, I do everything I can to avoid images in content. Simple text is easier, more maintainable, more accessible and, for added incentive, I'm a spectacularly inept designer. Predictably, though, there's always an exception. When an exception arises and I have to use an image, I still want the markup to be semantic and accessible.
The technique I use isn't revolutionary or even new, but I don't see it used very much where I work, so I thought I'd write it down. Who knows? Maybe it's less common than I've been assuming it is.
Among the (many) things that I'm admittedly anal about with respect to code is nomenclature. I hate obfuscation, I detest ambiguity, I deplore obscure abbreviations. I'm also not a fan of misdirection.
