-
AuthorPosts
-
April 27, 2024 at 12:21 pm #1441040
Hello Kriesi-Team,
I’ve some challenges concerning the strong accessibility requirements for an official school website.
When “Checking the serialized DOM of current page” I get several errors like:
Bad value true for attribute disabled on element button.
Attribute percentage not allowed on element div at this point.
Element style not allowed as child of element div in this context.
An element with role=menuitem must be contained in, or owned by, an element with role=menubar or role=menu.You can check it on the page: https://pags-kuelsheim.de/pags-new-2024/
Therefore you need the following 2 Bookmarklets “Check serialized DOM of current page” and “Check for WCAG parsing compliance”.
You can find them here: https://validator.w3.org/nu/about.html#extras (just save the above mentioned Bookmarklets as Bookmarks)
After you saved the Bookmarklets open the URL to test: https://pags-kuelsheim.de/pags-new-2024/
and then first open the Bookmarklet “Check serialized DOM of current page”
Then you should get the whole list of errors (for a better overview deactivate the warnings).
How can I eliminate those errors?For the errors concerning the role “menuitem” I checked the source code and in fact there is a role “menu” on the UL-tag.
So I don’t understand why the errors occur.The errors I need to eliminate definitely are the ones that remain after the second check.
So after the first checking of serialized DOM in the same window open the second Bookmarklet “Check for WCAG parsing compliance”.
After this there are 3 Errors left:Error: Attribute percentage not allowed on element div at this point.
[… <div class=”autoptimize-radial-bar” percentage=”1″> … ]
Error: Element style not allowed as child of element div in this context. (Suppressing further errors from this subtree.)
[… <style type=”text/css” data-created_by=”avia_inline_auto” id=”style-css-av-av_heading-35a281d039331e73961c1fb16c90aea2″> …]
Error: Element style not allowed as child of element div in this context. (Suppressing further errors from this subtree.)
[… <style type=”text/css” data-created_by=”avia_inline_auto” id=”style-css-av-jhe1dyat-381e073337cc8512c616f9ce78cc22d9″> …]These errors need to be eliminated definitely and therefore I need your support.
Do you have an idea how to get rid of them? It’s quiet urgent, so it would be great if you can provide me a solution for that as soon as possible.In case you need some further information or a login credentials, don’t hesitate to contact me by e-mail.
Thanks in advance and kind regards.- This topic was modified 8 months ago by dbha.
May 2, 2024 at 4:25 pm #1441934Hi,
I’m sorry for the delayed response.
We’ve investigated the errors on your site. The first issue is coming from the Autoptimize plugin. The second and third issues seem to be related to Enfold’s cookie bar.
Please go to the Enfold theme options > Privacy and Cookies > Cookie Handling > Enable cookie consent messages, disable it, and check if that resolves the error.
Best regards,
YigitMay 2, 2024 at 4:44 pm #1441936Hi,
yes, the errors disappear when disabling the Cookie Consent Banner. But the question is how to solve the errors with Cookie Consent Banner turned on…
May 3, 2024 at 11:33 am #1442123Hi,
I checked with our development team to see if it’d be possible to disable this using a filter or some other customization but unfortunately, there is no way to avoid this at the moment.
My only recommendation at this point would be to use a third-party content management plugin instead. I’m sorry about that.
Best regards,
Yigit -
AuthorPosts
- You must be logged in to reply to this topic.