HOWTO: let the viewer change the text size
Thanks to Andante - I stole this from her site
Here is a nifty little thing you can do to to allow your viewser change the size of the text on the fly. Create a text widget and set the title as 'Change Text Size'. In the text area of the widget add HTML Code:
<a href="javascript:void(0);" onclick="javascript:body.style.fontSize='.8em'"><span style="font-size: xx-small;">+</span></a> |
Great post. I have just used this to allow toggling the background colour of my photo blog, by changing 'fontsize' in the code to 'background'
|
This is great and easy to implement. What would it take to have only the text in the body of pages and posts be affected (as oppposed to the entire page)?
Not sure if this for another thread, but is there a way to change the fonts of the Category' font size, as well as other things like the body text, titles, etc.? Thanks! |
Hi Juggledad,
Your code works fine. But only with TEXT. The website background remains constant. This destroys the homogenous look to the website -- and can be confusing. I had to remove the text in the top decorative bar. (since updating the WP to 3.0 the font resizer doesn't work there anymore, but I left it in -- in the hope of a solution). Is it possible to have code that enlarges the whole screen image? Not just the Font-size? Thanks! Janine |
Quote:
ATA 3.5.3 WP 3.1.3. The above code used in a Text Widget increases the text in my body content and Title plus strap line but not in the sidebars. In ATA 3.6.7 WP 3.1.3 it increases the size in the sidebars plus Title and strap line but not the body content. Do you have any magic!!! solution to the 3.6.7 theme. |
odd, I just tested it and in both 353 and 367 it effects the sidebars. can you show me your site for 353 where it doesn't effect the sidebars?
|
Hi Juggledad
Sent sites to you privately. |
Do you have all BUGFIX's for 367 applied? (they can be found in the 'New Version & Updates' forum and sub forum)
--if not, apply them before we go any further and re-test |
I have not updated but have now started to do so.
Some bugfixes are described as "replacing other bugfixes" Is there a list of "bugfixes" which at this date should be used or should I just start at No 1 and work onwards ?? |
there are currently 5 and #4 contains #2. #5 is really only needed if you use 'WordPress SEO by Yoest', so if you are not using that plugin, you should apply 1, 3 and 4.
You know, since all modern browsers have a way built in to make the type bigger, maybe you should just tell people to use the browser ZOOM function. |
Hi Juggledad
Thanks for your assistance it helps. Regarding browser zoom I am coming to that opinion, but am presently playing around with "Accessibility" options and I am considering all ways of making things easier for those who are less able (is that the correct PC term). So the bugfixes, I do use yoast. I will use bugfix #1,3,4 & 5 BUT I see there are #8 & 9 and others. I have already used bugfix #9, it was at this stage that I could see that #9 replaced #8 hence my question about which fixes to use. Should I leave #9 as it now is and just use #1,3,4,5 My apologies if I am being slower than normal in this matter. |
If you are on 367 you only want to apply the ones that start with 'BUGFIX 367-nn....'
|
Quote:
Thank you very very much for the Text sizer, I like having accessibility options for the visually impaired. |
Quote:
What you want to see if if they get fixed and that's what the patches are for. |
Quote:
|
All times are GMT -6. The time now is 06:12 AM. |
Powered by vBulletin® Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.