Sent by Austin, Darrel on 5 August 2004 21:09
>them to learn your method instead of the perfectly good one that is built
in to the browsers of their choice.
Your point is valid, but realize there are a lot of people that do NOT know
how to use the 'perfectly good, built-in' text resizing ability of their
browser.
If you use the browser's built-in ability, you'll accomodate everyone that
knows how to use it, but not those that don't. If you use your own widget,
you'll accomodate those that don't know how to use their browser's built in
feature, but might hinder those that do.
Again, you can please some folks, but not everyone. At least not yet.
> If they have visual problems, it's more likely that they already know how
to enlarge text on their browser.
No, it's not likely. At least not from my real-world observations. A serious
handicap? Then perhaps...but when my dad is squinting at the screen, he just
complains. In my office (an IT office...with web developers) few knew how to
do it.
> And once they learn that, it works exactly the same for every site they
visit (unless the site designer has removed that capability)
Ah...see that's the issue. If you go with the 100% theory, then yes, you are
correct. But not all developers that want people to be able to use their
built-in browser tool use a base font of 100%, so the end-user needs to
resize upon each page. This is one area where the on-screen widget has an
advantage...it only changes the font size of THAT particular site.
Bottom line, you're right. I'm right, and most of the other posts are right.
We're still a long way from a perfect solution.
-Darrel
______________________________________________________________________
css-discuss [EMAIL-REMOVED]]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
