Critical: The aria-describedby attribute must point to IDs of elements in the same document.
Critical: The aria-labelledby attribute must point to IDs of elements in the same document.
I’m getting these back from my accessibility scan, in reference to ID: nf-form-errors-1 and ID: nf-form-title-1.
I know this was brought up in a previous post, and was ruled out as a ‘false positive’, however, I believe there’s a solution for this issue:
Add aria-busy=true while the content is loading, and aria-busy=false once loading completes.
aria-busy waits for the wrapped content to complete being “busy”, and only after it is done, will it go through the child elements to look for required relationships.
aria-busy works with the aria-live attribute. It is explained more in this article:
https://accessibilityresources.org/aria-busy
Could this fix be implemented? Thank you!
]]>I’ve waited long enough for an update, so I went ahead and did it myself.
I tested this against WC3.1, and I made my updates to still be compatible with 2.x, although I haven’t tested against 2.x
If you want to get the update, you can get it here:
WooCommerce Digital Signature (fork) on Github
I just wanted to see if anybody else has come across this one.
I was alerted yesterday by my host that I was getting 100’s of inbound requests which they are quarantining until we can suss it out.
In the root /wp-content/cache.. I am finding 100’s of php files which begin with about 30 numbers ad letters IE 3745vhyd857273gbidt78.php. They are always writing to the a folder which beings with 3 random letters. Sometime they are in the Object and sometimes in the Db cache etc.
I am using WC3 and cloud flare. Obviously there is caching going on – and of course I would expect to see files here. But it was the level of the requests we are getting and the file structure.
As I do not quite understand the mechanics of WC3 I was hoping that somebody might explain what I should be seeing in the wp-content/cache.
I can eliminate any that look weird.
Thanks all.
]]>If after updating to wc3.0 you find this doesn’t work, change line 19 from
add_filter(‘woocommerce_product_default_attributes’, ‘setup_swatches’, 10, 1);
to
add_filter(‘woocommerce_product_get_default_attributes’, ‘setup_swatches’, 10, 1);
Cheers,
Joel
Not good.
]]>It seems to be coming from https://api.w.org
Any help or ideas would be great to know how to get rid of this error.
Here is a screenshot…
https://prntscr.com/cn7mlk
Thanks
]]>The first three are:
Error Line 2, Column 1: Missing xmlns attribute for element html. The value should be: https://www.w3.org/1999/xhtml
<html lang=”en-US”>
Error Line 4, Column 23: there is no attribute “charset”
<meta charset=”UTF-8″ />
Error Line 106, Column 228: duplicate specification of attribute “alt”
…13/07/RoyalMileLogowhiteb.png” alt=”Royal Mile Service Centre” alt=”logo”/>
Can anyone help me in solving this? The site loads very slowly and I am not sure whether this issue may be contributing to this or not.
Thanks in advance.
]]>there is no attribute “role”
there is no attribute “autocomplete”
there is no attribute “container”
reference to non-existent ID “s” (<div><label class=”screen-reader-text” for=”s”>Search:</label>)
I’ll be very greatful!
https://www.ads-software.com/extend/plugins/ajaxy-search-form/
]]>How that I have the base of my site dailyandroidreviews.com, (my site is running on WP 4.3.2.) set up and it’s a matter of SEO and general updates and optimization I have a few questions/concerns…
When I Validate WC3, my site is giving me 53 errors and 37 warnings. The first question is; are these errors/warning going to badly affect my site in any major way?
Next up, after playing with my various plugins, I’ve determined that most of the errors/warnings are coming from Jetpack (22 errors from Jetpack alone) and SEO Ultimate. Both are running the most up to date versions. I like these plugins, is there any way to resolve the issues, or maybe get similar plugins that won’t push out some many errors?
I’ll be honest, when WC3 says this line has this issue, I don’t really know how to fix that coding. I’m trying to learn though.
Any feedback would be greatly appreciated.
]]>