Really interesting. It’s good to hear what a lot of people think are specialist ideas about accessibility getting an airing.
From past experience if you start with the principles of accessible CSS then you’re less likely to write unmaintainable CSS, or CSS where one specifier suddenly conflicts with another and you can’t work out why. Always pairing background and foreground colours in the same pair of braces is a must for clarity (even if it’s background-color:inherit), for example.
(I think Yahoo!‘s login page still has the no-background CSS bug. Tsk tsk.)
J-P Stacey
Really interesting. It’s good to hear what a lot of people think are specialist ideas about accessibility getting an airing.
From past experience if you start with the principles of accessible CSS then you’re less likely to write unmaintainable CSS, or CSS where one specifier suddenly conflicts with another and you can’t work out why. Always pairing background and foreground colours in the same pair of braces is a must for clarity (even if it’s background-color:inherit), for example.
(I think Yahoo!‘s login page still has the no-background CSS bug. Tsk tsk.)