Webmasters Stack Exchange is a question and answer site for pro webmasters. It only takes a minute to sign up.
Sign up to join this community
I see some text-heavy sites implement the little JavaScript widgets that allow you to choose smaller or larger text sizes on sites. (e.g.: as described on the Guardian's website)
Are these little widgets worth the screen real estate they take up? If you have them on a site you webmaster, do you run any metrics to see if they are used?
Thoughts and studies on the usefulness of these widgets would be welcome.
I think the most important thing is to make sure your sizes scale no matter if the user does it through a JavaScript widget you add or through a the browsers default support.
As for adding it or not, I think it depends on your targeted demographic. If you site is build for tech savvy people, I would definitely say no. If your site is built for older people who may not be so tech savvy, like online news sites or things like that then I would say yes it would be of use. Many times less savvy users won't know they can enlarge their text as a browser default and so they either struggle with the site or pass over it for ones with those options.
I have spoken to someone in the Royal London Society for the Blind who works with assistive technologies regarding a project I was working on for them, and he is dead against them for the simple reason that users who need to increase font size in order to be able to read the content will not see the widget in the first place!
I wouldn't waste the real estate, instead I would provide a nice accessibility statement including instructions on how to increase the font size using your browser.
I agonised over this one for ages for a site I worked on. There's a huge part of me that echoes Dan Diplo's feelings on the matter: it's built-in browser functionality, it doesn't need replicating in a subtly different way by every individual site on the www. If you add a font-sizing widget to your web site, you might as well also add 'print this page', 'go back', and 'bookmark this page' links all over the place.
BUT, people argued that other people didn't know how to resize the text in their browser. A lot of people don't even know that it's possible.
I started reading up on the matter, and thinking about it a little less passionately. In particular, I came across this question on uxexchange and the top-rated answer there just about had me convinced. I added the widget, in such a way that it's reasonably obvious without wasting valuable screen estate. I haven't looked back.
Other than the argument on the uxexchange post, my main reason for implementing the widget was the ignorance of font-sizing options in the browser. I wish everyone was more aware of that feature, but wishing it doesn't make it happen. I think it's a real shame that most of the browsers removed the prominent font sizing icons that used to be on the main toolbar - you have to go back as far as IE3 (!) to see this excellent feature (in that particular browser, at least). It's far more hidden than print, back, and bookmark and - mainly for that reason - I think the font-resizer widget is, on balance, justified.
em-based layouts, you can also let the browser change the page "zoom" while the widget only changes text size.
– Lèse majesté
Nov 9 '10 at 8:10
I say no, because the users around my office that prefer a larger font have it already set larger by default everywhere. They don't click those things any more often than I do.
It is far more important to make sure you sizes scale properly without blowing up your design, and assume a good percent of your users come to the site with something other than the default font size.
Just to add my two penny worth - I also think they are a waste of time. Enlarging text and zooming is functionality that should be performed by the web browser (user agent), not the website. It is the website designer's responsibility to ensure this works when using the browser's in-built mechanism.
It is ridiculous to expect every website in the world to adopt some propriety means of re-sizing text, each with it's own UI, when this functionality is provided in a much better way by any decent browser. Any visually impaired user will already know how to perform this task via their browser and may well already have a custom style-sheet to over-ride font-sizes or have set an increased zoom level.
It is a variation on the old adage: Give a man a web page text-resizer and he can view one website. Teach a man how to re-size text via his browser and he can view any website for the rest of his life.
I've thought about it and decided against it. You should make the website accessible meaning that you provide all the meaningful content but it does NOT mean you have to add a font-resizing widget, a contrast widget, etc. It's already built in the OS/Browser. They HAVE to learn how to use them and learn that it works for ALL websites, not just yours. It's a responsibility for all disabled people - I work with the blind, the deaf (I am deaf myself), and I am so annoyed that people who think that they should do everything to provide accessibility have no clue what it's REALLY about.
Disabled people do have to learn on their own to take advantage of the BUILT IN accessibility features and it's BAD when every website has its own widgets to cater to them. Think about it - you have a person who is far-sighted and that can be corrected with a pair of eyeglasses. Do you provide glasses for them while on your website then take them away when they leave the site? NO! It's a WRONG way to teach the disabled. I teach them HOW to use the Web with the built in accessibility features. They'd appreciate THAT kind of independence more because they realize it works for ALL accessible websites.
