alt131 - 10:52 am on Oct 15, 2012 (gmt 0)
Hi smallcompany, as birdbrain has said, this is an issue with ie9 and the users OS. Css can't mess with the OS, even if, as responsible coders, we were prepared to try, but text readibility extends into accessibility and usability issues so it's unpleasant to leave the issue at that point.
For those who haven't followed the background, simplistically, the way fonts are rendered was changed from whole-pixel to sub-pixel positioning in ie9, which also lacked a way for users to turn cleartype on/off. The cleartype issue has been addressed, but that still depends on the user. As smallcompany said, there is a lot of discussion, but I think the msdn ieblog [blogs.msdn.com] sumarises quite well. Follow the first link to the cleartype overview article if you like pic's.
So if there isn't a way css can turn cleartype on/off, but it creates a usability issue, then it may be necessary to find ways of making even small improvements in the display. The above article has a highlight box that states:
So the first question is whether the readability issue is better or worse with sub-pixel positioning. If worse, it can be avoided by serving documents in quirks or compatibility mode. (Hopefully not quirks!) But if the target market has a large percentage of users on XP, that may not be as awful as it sounds, and there are a lot of arguments ie9 will never attract a large market share.
ClearType font rendering is used in all IE9 document modes; sub-pixel positioning is used only in IE9’s default standards mode. IE9’s compatibility modes—Quirks, 7, and 8—use whole-pixel text metrics.
Another consideration is font-size as this seems worse at smaller sizes, especially if using pts that do not map to an exact px. Another possibility is to adjust font-weight or font-stretch and even letter- and word-spacing to see if that improves readability. Finally, the issue seems exacerbated by common "web-safe" fonts, so that also creates the option of considering whether to serve a substitute font that does not blur when antialiased.
Overall I think it useful to remember that most users (depending on your target), won't be comparing the site using different browser versions side-by-side. Given "equal" is usually impossible, best aim for usability and "equivalent.