> > > Those tools should be accurate for text-only combinations that don't use > transparency*, but I don't think they can detect the contents of images. > Regardless, if you need something that works absolutely on the final rendered > result, try http://www.paciellogroup.com/resources/contrast-analyser.html > which gives you an on-screen selector.
Thanks Ben, and others for the suggestions. > > * if you're using alpha transparency i've expanded on that point at > http://weblog.200ok.com.au/2009/09/accessibility-vs-alpha-transparency.html > Good article on using alpha transparency. Trying to get the site passes SC1.4.3, I have learned something new that I was not aware before. The bar is high to building accessible site that needs to take all WCAG 2.0 guidelines :-) In my case, the site has made fully accessible (except that some part of the site cannot work if Javascript switch off) the problem I have had isn't about alpha transparency but background images that are not solid colors but gradient with blended colors with variation of hues, and each section consists a number of blocks that have lighter/darken texts. I would have thought declaring a background color for the outer div wrap, use darken text where lighter background area, lighter text for darken background area should take care of it. This approach takes care of site performance issue as it reduces extra http request, and keeping the layout integrity with text size increases/decreases; the way I see it, it's clean, and effective approach. But putting color contrast into play, depending on the background color, it will go against either darken or lighter foreground color. Should SC1.4.3 not treating the background image as the measurement? tee ******************************************************************* List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [email protected] *******************************************************************
