December 04, 2003
Aging eyes and tiny fonts
Over on Digital Web Magazine, Nick has a pointer to this article: Font Size: No Happy Medium. In it, Dave Shea argues that, at some point, it stops being the designer's fault if people aren't happy with text sizes on web pages: The current standards movement seems to place an awful lot of responsibility on the designer. Its up to the designer to work around browser flaws by not using pixel-value text. Its up to the designer to consider people with perfect vision, low vision, and no vision. Its up to the designer to account for different monitor sizes and resolutions. Its up to the designer to make sure their layout doesnt break when fonts are at 100%, or 150%, or 200%. Reading the comment trail (at 44 so far) has been quite interesting. I'm very sympathetic to the point that Jim Dabell is trying to make: The issue of avoiding the users font size isnt about too small fonts. Its about the difference between font sizes on different websites. I have a good browser. I have a good font size. I dont like having to adjust the font size for every new website I visit just because lots of different designers have lots of different ideas on what the best font size is for me. I have to admit, this has been a bit of a pet peeve of mine. I'm happily surfing along with my 11pt Verdana type and all of a sudden, I'm on an unreadable site. Here's how this looks...you're at a website like Digital Web, which is very readable: And yes Virginia, I know how to resize type in my browser (I have to...bloug is too tiny for me to read by default as well). But I wish I didn't have to manually set it and unset it while surfing. However, unlike Jim, I'm actually quite happy with the workaround that Jeroen Coumans provided -- set a minimum type size in Mozilla. For me, Verdana just isn't readable at 8 pts or less on my monitor (1280x1024, 20"). But 9 will do in a pinch. As Jim points out though, this may cause the page to lose relative sizes between styles. Unlike him, I'm willing to put up with this to make my life easier.
Comments
You can fix it by defining a custom stylesheet, setting the font size for the top level tag - html. It works in Safari at least. I just did it with this site, and the relative sizes flow naturally from that. I guess it might break if the designer had set further pixel and point sizes for other elements, more testing required methinks. The style sheet I did was: html {
Post a comment
Note: Your comment will be reviewed prior to posting to minimize comment spam. Management regrets the inconvenience!
|
IDblog is Beth Mazur tilting at power law windmills. A little bit Internet, a little bit technology, a little bit society, and a lot about designing useful information products. Send your cards and letters to .
search this site
archives
August 2004
July 2004 June 2004 May 2004 April 2004 March 2004 February 2004 January 2004 December 2003 November 2003 October 2003 September 2003 August 2003 July 2003 June 2003 May 2003 April 2003 March 2003 February 2003 January 2003 December 2002 November 2002 October 2002 September 2002
categories
blogs and wikis
business and design content and writing design process education experience design hci information architecture information design marketing and brands multimedia & broadband politics search society & technology usability visual design web design wifi words can't describe
key links
STC Information Design SIG
boxes and arrows iawiki information design journal informationdesign.org infodesign usability sig usable web
groups
aiga experience design
a(o).i.r asilomar institute for information architecture asis&t sigchi society for technical communication usability professionals association
about moi
feeds
gratuitous right-nav promos
|