Hey @raygulick,
Thanks for reporting this, the icon inside the widget is intended to be hidden from screen readers as it is a visual presenteation element only so aria-hidden is appropriate on that.
That being said it shouldn’t flag as a warning on your pages. I will see about getting that resolved.
Hi again @raygulick,
I have just tested this on my side and I don’t see the aria-hidden flagged on this icon at all when I scan from the editor or when I scan from the button on the frontend highlighter itself. Can you let me know how you scanned the pages to get this to be flagged on your site?
I just scanned the page via the frontend widget. I can send you a screenshot if you like.
@raygulick that’s what I expected about how you were running the scan. We were aware that the scanner could find this and we made updates to to account for it. I can’t replicate it on fresh install of the update however if the previous scan javascript file was cached on your server or in your browser that would explain this.
Do you have a caching plugin on the site? If so could you try to flush it and retest to see if the issue goes away?
I flushed and then rescanned and got the same result. If there is an email address I can send a screenshot to, I’m happy to send it.
Got it, I am still trying to work out how the issue might be happening for you here but am continuing to look into it.
If you could send me the screenshot to (email removed as screenshot was recieved) that would be great.
I completely flushed all javascript and then deactivated the caching plugin. Then flushed DNS cache. Then returned to website and ‘cleared issues’, then rescanned. Same result.
Don’t know if this matters, but I’m on macOS 15.7.5, Vivaldi browser 7.9.3970.55
I will test with Vivaldi browser and see if the results are different for me.
I repled to the screenshot email but keeping the conversation here as well for posterity. I would like to know if the issue is still detected if you scan the page from inside the admin editor instead of through the frontend highlighter. I have a theory about a possible cause which could help be confirmed if the issue is NOT detected when scanned from the editor.
Closing the loop here to say that we discovered this was a browser level cache that was not clearing alongside the other caches that were cleared. A fix to enhance this will be released in the future but it seems as if it is not a widespread issue with all browsers and caches.
Thank you, William, for being so responsive and running this down.
