Building this functionality into the page is something I've struggled with
for some time. There's no way to add text resizing functionality without
DECREASING accessibility and usability for a large group of other users.
It does no use to screenreader users. And we expect users to understand
what a little and big A are supposed to mean? What about the added
complexity we introduce for those with cognitive disabilities, let alone
the several extra elements in the tab order of the page. And then we often
require JavaScript to do this kinda stuff. And most people that MUST have
enlarged fonts are going to have them anyways.
In my opinion, the only time this is an issue is when you break your page
by using too small of fonts to begin with. The problems introduced with
this built-in functionality, in my opinion, outweigh the added benefits.
Make a solid, accessible design decision and stick with it. I tend to
prescribe to the "user preferences are for sisses" camp -
http://www.yourtotalsite.com/archives/usability/user_preferences_are_for_/
Jared Smith
WebAIM.org
******************************************************
The discussion list for http://webstandardsgroup.org/
See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list & getting help
******************************************************
