- This topic has 25 replies, 2 voices, and was last updated 4 years, 3 months ago by Tom.
February 26, 2018 at 2:32 am #505736Harris
We are getting some errors in w3.org validation that I suspect might be theme (menu) related.
Can you please have a look as the site is subsidized by a EU program and there is a term saying that it must produce 0 errors in the w3 validator?
ThanksGeneratePress 2.0.2GP Premium 1.5.6February 26, 2018 at 10:10 am #506134TomLead DeveloperLead Developer
This is an issue in the theme currently:
An element with the attribute tabindex must not appear as a descendant of the a element.
It will be fixed in the next version 🙂February 26, 2018 at 11:23 am #506184Harris
So I guess the rest might be WP or elementor issues?February 27, 2018 at 8:50 am #507088TomLead DeveloperLead DeveloperFebruary 27, 2018 at 9:38 am #507137Harris
Thanks Tom!February 27, 2018 at 8:45 pm #507497TomLead DeveloperLead DeveloperMarch 16, 2018 at 11:50 am #521856Harris
I cleared all other errors. Is there any way to bypass (even temporarily) the “An element with the attribute tabindex must not appear as a descendant of the a element.” error so I can give the site for accessibility check (check is passed with 0 errors on W3 validator).
Will installing the latest beta version help?
HarrisMarch 16, 2018 at 9:49 pm #522123TomLead DeveloperLead DeveloperMarch 17, 2018 at 1:02 am #522167Harris
Some questions on the issue in order to check the available options as there is a strickt time limit regarding the accessibility check on that:
Will it be on the next GP or on the next GPP update? Any estimation when it will be out?
Will this be bypassed if I disable navigation and add one from Elementor?
Can you please confirm the theme file involved so I can give a try to make a temp fix?
Is it generatepress\inc\structure\navigation.phpMarch 17, 2018 at 11:08 am #522489TomLead DeveloperLead Developer
Aiming for the next GP update. This shouldn’t affect accessibility at all, it’s just an HTML validation warning. It will have no negative effects on your website.
You can try building one with Elementor, but there’s no promises there that their navigation is keyboard accessible.
Yes, the code is in that file.March 17, 2018 at 11:16 am #522497Harris
I know that it has no negative affects on the site and that it won’t affect accessibility, but it gives an error (not just a warning) in W3.org validator, and the terms clearly say “0 errors at W3 validator”.
I know its weird, I know it doesn’t make much sence, but thats how it is.
It’s not me making the rules 🙂
If they see an error they will just reject it, without looking any further, no matter what.
Any estimation on when the next GP update is comming so I can see if its worth rebuilding the menus or messing up with the theme files?
by the way… is that “error” related with a certain feature of the navigation that I can disable?
ThanksMarch 17, 2018 at 9:04 pm #522755TomLead DeveloperLead Developer
The “error” is being caused by some accessibility code we added in 2.0 to make the navigation tab-friendly.
There’s no set date for the update yet – it should be before the end of the month.March 18, 2018 at 12:34 am #522807Harris
Does that mean that if I “downgrade” to a verion <2.0 the “error” will clear?March 18, 2018 at 9:40 am #523113TomLead DeveloperLead DeveloperMarch 18, 2018 at 10:17 am #523132Harris
Can I just replace the navigation.php file of the latest version with the older one?
Reminding that I am just looking for a temp solution to bypass the test.
I will replace things as needed after that.
- You must be logged in to reply to this topic.