• Resolved squadhouse

    (@squadhouse)


    If you run the official http://validator.w3.org/nu/ validator there are some errors by the plugin:

    • Error: Bad value true for attribute allowfullscreen on element iframe.
    • Error: The frameborder attribute on the iframe element is obsolete. Use CSS instead.
    • Error: Element style not allowed as child of element body in this context.
    • Can you fix this please since it collides with german law for accessibility by people with health problems.

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author Aert

    (@aahulsebos)

    HI @squadhouse,

    Could you post the URL you check, so we have some context?

    Thanks, regards Aert

    Thread Starter squadhouse

    (@squadhouse)

    Yes of course: https://www.tuticket.de

    Plugin Contributor Leon Wimmenhoeve

    (@leonwimmenhoeve)

    Hi @squadhouse,

    While the errors mention the Complianz placeholder, I suspect that another plugin or theme is causing them:
    – allowfullscreen is not added to the iFrame by Complianz, perhaps by another plugin
    – frameborder the same
    – style elements are via the “head”. So the style attribute can not be added by Complianz as well.

    You could test if temporarily disabling other plugins changes your test results. Let us know if you want us to have another look at the page.

    Kind regards,
    Leon

    Thread Starter squadhouse

    (@squadhouse)

    Hi Leon,

    thank you for your quick reply. I have literally deactivated EVERY plugin except for complianz itself and it still added those tags and styles.

    I even switched the theme to twenty-two default theme (without any modifications) and the problem still occured.

    I don´t really have any more ideas…

    Plugin Author Aert

    (@aahulsebos)

    Hi @squadhouse,

    The iFrame attributes are from the YouTube video, where Complianz adds a placeholder but does not add the attributes.

    You can remove the attributes from the iFrame if it’s an issue,

    regards Aert

Viewing 5 replies - 1 through 5 (of 5 total)

The topic ‘HTML not valid’ is closed to new replies.