> It's a browser thing, actually. Modern browsers allow you to override
> font sizes in the browser.

> Modern OSs supply accessibility features that are supposed to help
> users with accessibility problems experience computing at levels close
> to those of users without.

Well, they should. IE/Win doesn't. Until it does, I believe it's the
designer's job to make sure their users are able to read the content, and
that means making sure font sizes are resizeable. It's a flaw in the
browser, and one that us designers are responsible for making up for.

> It will remain a good idea as long as pixels are the only truly native
> measurement for screen. Points are native for printing only. That's
> why you'll find only pixels in my @media screen rules and only points
> (or inches) in my @media print rules.

> NO! Not until all browsers conform to the standards, until then it's a
> mess. NS ignores cascading rules for em and % sizes, even 6.0 and 7.0,
> and then there are the poor last-century souls using 4.x whose case is
> even more desperate.

I fully agree that point's are a bad unit to use for screen. I won't argue
for percentages or em's, since those are really buggy in some browsers, as
you said. However, font size keywords, while offering somewhat less control
for the designer, are fully resizeable to the user. There's only a couple of
bugs involved with them, and those can be worked around with Tantek's box
model hack.

While I understand that pixels are the only unit of measurement that are
truly reliable to look the same on all screens, since they create
accessibility hassles for some users, they should be avoided until browsers
catch up.

 - Slime
[ http://www.slimeland.com/ ]

Post a reply to this message