Anthony Barnes

Leaving a comment here just to acknowledge this hasn't been forgotten. It's technically achievable to read the content inside `` tags and analyse it for issues but would require new...

In my tests I was able to get this to occur using the minified bookmarklet code. Running the code that caused this error manually in the browser console doesn't result...

I can replicate this. The element positioning math needs to be reviewed so that it works correctly for content inside iframes (Roughly in Auditor/HTMLCSAuditor.js line 1978 where targetY is calculated).

The error looks correct to me. From the example you posted there is no programatic way to determine what accessible text is available. I'd suggest looking at the WCAG guidelines...

I'm not seeing this on the success criterion links in the HTMLCS Auditor, the urls are formatting like this: https://www.w3.org/TR/WCAG21/#non-text-content Could you provide more context on where you are seeing...

I was able to replicate with just the source HTML of that page so we can probably rule out conflicts with other (external) JS running on the page as the...

This is partially solved with recent changes to the way HTML code sniffer will exclude `aria-hidden=true` and `role=presentation` and all of the descendent elements (this can be used as an...

I've put this into branch 'pmcelhaney-report-download' for now with a few changes. Will look at a merge after more testing and confirmation of the location we would add the button...

@phillbaker An updated PR would be great, I can't merge this one as it stands. There aren't a lot of details from @saltybeagle about the issue this PR was trying...

Thanks @phillbaker for the concise explanation. I'd agree giving a hard pass or fail wouldn't work well here due to the transparency (similar reason why we can't accurately detect font...