Hi Ron,
Pringle, Ron wrote:
<snip> Again, no color or background-color is applied to this
since all paragraph text is colored on the <p> tag and I obviously want the
background image in the secondaryBottom div to show through. And yet the
validator throws specific errors indicating that I haven't declared
background-color to go with the (i assume, inherited) color declaration.
I haven't seen this warning on elements with inherited color. Can you
give us an example?
Declaring a color on each and every element that inherits color for its text
seems patently absurd (and overkill) and declaring a background color on the
elements mentioned above would obviously destroy the layout.
Yes -- you've done exactly what the warning is there for -- you checked
out your page, determined that you didn't need to change anything in
this instance, and moved on. No worries. :-)
I've used the Firefox Web Developer Toolbar to test my pages with no color
and/or with no images and everything appears to be readable/accessible with
no problems. I've even run the site through the color blindness tools to
ensure that when background colors/images are used, they still work for all
types of color blind users.
Am I missing something here?
Yes. The possibility that someone may have a user style sheet set up
with his or her own colors, which may end up contrasting with your
colors. So the idea is that if you're going to reset one of the user's
preferences (color or background color), make sure you reset both of
them so they don't inadvertantly match and make the text unreadable.
I don't understand the point of the validator
invalidating my css on these issues.
It doesn't invalidate your CSS, just gives you warnings of things to pay
attention to.
I'm inclined to ignore these issues
with the validator, but at some point I'm going to have to explain to my
bosses exactly WHY the code doesn't validate and why that's ok.
A machine can't tell if you are doing something well. It can only check
if you are following certain rules to a T. So it gives you a warning
and relies on you to check and make sure the code in question is not
causing any problems, because it can't tell. Thus, you shouldn't ignore
the warnings, in that you should read them and see if they are valid --
but if they aren't, you don't have to worry about fixing them.
Remember, the validator is only a tool. Your bosses shouldn't care if
your pages validate, as long as you know why they don't validate and
know the errors aren't causing any problems.
Zoe
--
Zoe M. Gillenwater
Design Services Manager
UNC Highway Safety Research Center
http://www.hsrc.unc.edu
______________________________________________________________________
css-discuss [EMAIL PROTECTED]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
