![Check out Enfold](https://kriesi.at/wp-content/themes/kriesi/images/banner-enfold.jpg)
Tagged: accessibility, WCAG
-
AuthorPosts
-
July 18, 2024 at 8:20 pm #1462426
Wen testing a website for errors in the code in W3 Validator, these are the errors that show up. They all seem to be linked to the Modal PopUp in the Privicy settings. Is there a way to get rid of all of these?
Error: Element style not allowed as child of element div in this context. (Suppressing further errors from this subtree.)
Error: Element style not allowed as child of element div in this context. (Suppressing further errors from this subtree.)
Error: No p element in scope but a p end tag seen.
Error: No p element in scope but a p end tag seen.
Error: No p element in scope but a p end tag seen.
Error: No p element in scope but a p end tag seen.
Error: Duplicate attribute aria-hidden
Error: An element with role=tab must be contained in, or owned by, an element with role=tablist
Error: An element with role=tab must be contained in, or owned by, an element with role=tablist
Error: An element with role=tab must be contained in, or owned by, an element with role=tablist
Error: An element with role=tab must be contained in, or owned by, an element with role=tablist
Error: An element with role=tab must be contained in, or owned by, an element with role=tablist12 errors in all, and all between line 445 and line 480.
It would be great if these errors could be fixed in order to get the site up to WCAG standards
Regards
NinaJuly 20, 2024 at 2:16 pm #1462550Hey Advantage09,
Thank you for your patience and the link to your site, but the W3 Validator is not the same as a WCAG Validator.
Often when I check the W3 Validator gives false errors, such as Error: No p element in scope but a p end tag seen. when you check the source code the “p” tage is there:
As for the role=tablist issue, when I check your site on a WCAG Validator this is not flaged, as I understand the tab element can be in the tabpanel element.
On May 7 the Dev Team made some adjustment to this to be compliment with the European Accessibility Act (EAA) documentation, and this is outside my expertise, but since the WCAG Validator is not flaging this it would seem that this is correct.
If you wish I can ask this on the Dev Team Github threadBest regards,
Mike -
AuthorPosts
- You must be logged in to reply to this topic.