WebAIM - Web Accessibility In Mind

E-mail List Archives

RE: Font Resizers (WAS RE: back to top)

for

From: Austin, Darrel
Date: Jan 11, 2006 5:20PM

> Why? If your site's purpose is to teach browser usage, fine.
> Otherwise, questionable. Accessibility info page? Aren't they
> write-only pages?
> Does someone actually _read_ them?

Right. Good point. ;o)

(FYI, our's will actually be read and write...there will be some
preferences folks can set there if they so choose to so do).

> Now you are saying that you design something that duplicates
> browser functionality in one way, and if you are logical, you
> won't stop there but will create your version of many other
> functions as well.

I'm not saying that. I'm saying this particular browser functionality is
rather useful, and not apparent to a lot of folks that will be visiting
our site.

> What makes you think that you will have
> much better success?

Well, for starters, it will be visible by default. Which gives us a
slight advantage already.

Secondly, observation. We implemented this feature on our intranet and
within a week we had a few folks...software developers for that matter,
thank us for such a great feature.

> Would your strategy really be suitable
> for web authoring in general? That would typically mean that
> one underpaid employer, allowed to spend a small amount of
> his working time to web stuff, reinvents the wheel that was
> designed by a large number of computer professional over the years.

I think that's a larger discussion...and an interesting one to be had.

Bottom line is that it depends. Yea, reinventing the wheel can often be
pointless. It can often be necessary.

> What is "simple" and "intuitive" is not a simple question at all.

Nope. But in this case, it's not too big of a stretch. As mentioned,
just showing the option on the screen puts it ahead of the built in
browser controls.

-Darrel