Tue 04 Mar 2008
Up until this point, whenever I heard someone from Microsoft start talking about standards, I couldn't help but laugh while thinking of how badly IE has butchered them in the past. Standards compliance was somewhat improved with IE7, but it sounds like Microsoft has finally agreed to step up to the plate and make IE8's standards mode actually standards-compliant.
MS has fought standards-compliance as the rest of the world knows it for several iterations of IE, knowing that it would break a lot of old sites that were specifically targeted towards IE's faults. With IE8 they will admitedly break sites that do not specifically request a special http header/meta tag to trigger IE7 standards mode. It will be quite interesting to see how many sites this affects. I'm guessing a VERY large number.
Since some (but certainly not all) of the rendering differences between IE and standards-compliant browsers have been due to a certain degree of ambiguity in the W3C documentation, Microsoft's definition of "the most standards compliant way possible" may be far different than that of Firefox or Safari. It would be nice if they just used Firefox and Safari's interpretation of the W3C standards, but I'm sure that Microsoft will come up with their own creative way of interpreting them.
So kids, this is why you code to standards and make IE the exception, not the rule. For those who ignored the standards evangelists, let the fun begin...
Share This
Tue 05 Feb 2008
Well, if you're a frequent (or even infrequent) visitor to my blog, you'll notice that I've changed up the theme quite a bit. I was never really completely happy with the old one, and did quite a bit of searching to find one I liked better, but could never find one that really jumped out at me. So, after much procrastination, I finally decided to buckle down and create a theme of my own. I'm much more happy with this one - it's cleaner, more readable, and not as cluttered as the old one.
Hopefully, I'll have the time (and motivation) to work on it more over the next few weeks. There are still a few things that I want to do with it before I call it done. I'm planning on adding an "About" page, fine tuning the code to ensure W3C standards compliance, and possibly making the panoramic image above into a slideshow.
I've tested the new theme in FF 2/Mac, Safari 3/Mac, and IE6/Win, and there were no glaring issues. I'll be testing in IE7 tomorrow, but I don't anticipate any major issues. If you happen so see anything crazy going on, please let me know by leaving a comment on this post.
Thanks!
Share This
Sun 20 May 2007
Search Engine Optimization
Search engines place greater emphasis on certain tags within your page, such as <title> and <h1>. This means that pages with the keywords a user is searching for in the title and top level headings will get a bump in the search results vs. pages with the keywords in <p> or other less important tags. For more on SEO benefits of semantic markup, check out this great post on semantic markup for blogs at pearsonified.com.
Accessibility
Semantically marked up pages result in greater accessibility. For example, screen readers can't decipher a top level heading from the rest of your content unless it is surrounded by <h1> tags. This is not to say that using semantic markup will guarantee that your site will be fully accessible, but it's a good start. For more on accessibility, see The W3C Accessibility Initiative website.
Maintainability
Semantic markup is easier to maintain. Sure, you could surround all of your headings with <div> or <span> tags, but then you'd have to specify a class or an ID in order to accurately target them with CSS. If you have all of your top level headings in <h1> tags and all your paragraphs in <p> tags, then when it comes time to style your page, you can just style the elements themselves and you don't have to worry about classes or IDs. Overall, you'll end up with less clutter in your pages and your stylesheets.
Share This