Anthony Barnes

@phillbaker That would work if we assumed that the transparency resulted in mixes of just colours, but what I suspect might happen with transparent backgrounds is revealing images or text...

@phillbaker That sounds like a solid way forward and for (1) the example for showing a warning is correct. FYI I think we don't account for css opacity which will...

Hi @waffledonkey, are you able to provide more information to replicate the issue where HTMLCS is showing errors from its own UI? The errors themselves do need to be fixed,...

Thanks, I can replicate the issue you see on that particular site. I haven't seen this occur before so my initial thought it some conflicting JS, I will debug further.

I had initially thought the errors you posted were from the HTMLCS Auditor UI, but it appears they are coming from the source of the page. One issue is that...

If I understand the documentation on that site the 508 refresh now fully adopts WCAG 2.0 (which HTMLCS already supports). We currently maintain separate standard checks for 508 and WCAG,...

@philga7 Thanks. I'll keep this issue open as a reminder to remove 508 specific code for the next release.

Reading the code it looks like it doesn't support positioned or pseudo elements at all (will add a failure on absolute positioning). It was a deliberate coding decision probably owing...

Hi @stefanruijsenaars, are you able to provide some example code where this fails?

This is a bit late in the reply, but it sounds like the HTMLCS javascript files are not being included. We'll need more detailed information to give you a better...