WebAIM - Web Accessibility In Mind

E-mail List Archives

Thread: Solution to Text Size Changer problem

for

Number of posts in this thread: 3 (In chronological order)

From: Leesa Lavigne
Date: Tue, Mar 09 2004 4:15PM
Subject: Solution to Text Size Changer problem
No previous message | Next message →

I posted a couple weeks ago looking for advice on how to make one of the
many

From: Randy Pearson
Date: Tue, Mar 09 2004 4:53PM
Subject: RE: Solution to Text Size Changer problem
← Previous message | Next message →

Leesa,

FWIW, I also include P and BLOCKQUOTE in my generic selctors for font-size,
however I cannot remember why, but it must have been some UA issue from long
ago. Doesn't seem to hurt though:

BODY, TH, TD, BLOCKQUOTE, P { font: ... ; }



_____

I posted a couple weeks ago looking for advice on how to make one of the
many "Text Size Changers" work on my site so the user could change the
site's text size to suit their needs.



I finally found out why I couldn't get any of the scripts to work.



I use TopStyle Pro to create my style sheets. I think all the scripts
worked. It was my CSS. It showed the font-size as being compatible with
most all the browsers but I decided to run the 'script checker' and a red
exclamation point showed up in front of the Body tag.



Table tags do not inherit the body tag attributes. I had to create a
selector that included the ASP code for the font size and include the td and
th in the selector like so:





body{

background-color: #CCCC66;

From: julian.rickards
Date: Wed, Mar 10 2004 6:50AM
Subject: RE: Solution to Text Size Changer problem
← Previous message | No next message

I tend to use the body selector for only those properties/attributes that
applied to the <body> tag pre-XHTML: for example, body margins, body
background/color and text color. For example:

body {background: url(image.gif) top left repeat-y #F0F; color: #FF0;
margin: 0em 1em; padding: 0.5em;}

I know these work for all browsers in the sense that if the browsers
understand CSS, these properties seem to cascade down (where applicable) and
work properly. Notice the absence of font-family.

Lately, I have been containing the content in <div>s, generally 4 such as
<div id="masthead">, <div id="navbar">, <div id="body"> and <div
id="footer"> and using relationships to set the specific properties such as:

div#navbar {font: 0.8em/0.9em Arial bold}

Just my 2cents (Canadian currency, which seem to be growing in value against
the US currency of late: does that mean my comments are of greater value now
than before? :-)

---------------------------------------------------------
Julian Rickards
Digital Publications Distribution Coordinator
Publications Services Section
Ontario Ministry of Northern Development and Mines
Phone: (705) 670-5608
Fax: (705) 670-5690


----
To subscribe, unsubscribe, suspend, or view list archives,
visit http://www.webaim.org/discussion/