My
full answer is below, but,
if you're just trying to avoid a fight with the boss, make the home page validate & review the WAI's
WCAG (Web Content Accessibility Guidelines). Check your site in Lynx, and then you can slap the logos to the home page.
As you are able, get the rest of the site up to speed.
Yes, there are serious flaws with this solution, however, it may be the best solution for your
work situation. (And obviously only you can decide that.)
====================
While his motives are undoubtedly misguided, perhaps you can translate this request of his into the time you need to create valid markup and an accessible site.
I certainly understand that time constraints can put a serious hamper on investigating & implementing a truly accessible site, but you can knock off the bulk of these things without breaking a sweat.
Alt attributes are the quickest way to improve accessibilty and help a site validate. If the graphic serves no semantic purpose, the attribute should be null:
<img src="myUselessImage.gif" alt="">
CSS will help you eliminate any color attributes you have: I tend to use external, but remember if you're trying to save time, you can always slap inline CSS in:
<tr><td style="background: #fff;">equvialend of bgcolor="white"</td></tr>
What development tool are you using? Dreamweaver and GoLive both help you out with both of these things; Dreamweaver in particular has a separate add on called Lift that can automate some great things (complex data tables are nothin' to it!).
I truly believe that developing these habits now will only help you in the long run.
Best of luck!
--jbelle
P.S. as a related side note, I work to ensure all my sites validate and are accessible, but I wouldn't put that logo on them! You can always tell him those can often look like "Made with a Mac" graphics; who cares? (And I love my Mac!)
P.P.S. You can also use
Bobby to test accessibility, but without an understanding of the WCAG, I don't think Bobby is as useful.