etre.com/tools/colourblindsimulator/); and
the Cynthia Says Portal Tester (www.cynthiasays.com/fulloptions.asp), which can
aid you in Section 508 and WAI (Web Accessibility Initiative??”see www.w3.org/WAI/)
compliance.
Here are some of the more common errors you might make that are often overlooked:
Spelling errors: Spell a start tag wrong and an element likely won??™t appear; spell an
end tag wrong and it may not be closed properly, wrecking the remaining layout. In
CSS, misspelled property or value names can cause rules??”and therefore entire layouts
??”to fail entirely. British English users should also remember to check for and
weed out British spellings??”setting colour won??™t work in CSS, and yet we see that
extra u in plenty of web pages (which presumably have their authors scratching
their heads, wondering why the colors aren??™t being applied properly).
Incorrect use of symbols in CSS: If a CSS rule isn??™t working as expected, ensure
you??™ve not erred when it comes to the symbols used in the CSS selector. It??™s a
simple enough mistake to use # when you really mean . and vice versa.
DEALING WITH BROWSER QUIRKS
349
9
Lack of consistency: When working in XHTML, all elements and attributes must be
lowercase. In CSS, tag selectors should also be lowercase. However, user-defined id
and class values can be in whatever case the author chooses. Ultimately, decide
on a convention and stick to it??”always. If you set a class value to myvalue in CSS
and myValue in HTML, chances are things won??™t work.
Pages:
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447