Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • #1360749

    Hello,

    The theme has an issue “No p element in scope but a p end tag seen” from https://validator.w3.org/nu/?showsource=yes&showoutline=yes&showimagereport=yes

    Your editor is dropping </p> out of nowhere and for no reason. Please see the attachment for a printscreen from validator.w3.org

    Based on your forums, this issue was reported in earlier posts in 2016, 2017 and also 2019. In those posts you said you would solve it but it is still not solved in 2022…

    By the European Union, all websites which participate within NSRF programs, they must comply with accessibility requirements. These are required since 2015-2016. So, if a website is not error-free when checked by some online validators, the EU agents will not consider it as suitable for people with disabilities.

    Please provide us with a way to fix it ASAP.

    #1360837

    Hey ik,

    I can only see warnings when I check your site, please see screenshot in private. How can we get the results you are getting in the test?

    Best regards,
    Rikard

    #1361063

    Hello,

    As stated in the other thread which we also asked for support for issues the theme has with the accessibility validators, we had to remove all the parts of the website which were not passing the validator. This changed the website appearance drastically and we had to explain to the customer that it’s 100% a theme’s mistake.

    Also, due to your slow support on the other ticket, we had to find a way ourselves by disabling or removing every part of your theme which was causing errors. We did not fix the theme, nor the errors which are still there, but we found a way around (it’s not CSS – it’s a rather bizarre and weird way which works for no logical reason).

    In order to fix this weird </p> issue, we had to add each content element (text, image) on a different layout element. There was only 1 case which weirdly enough it did not require us to do that. In every layout element we had to place a single content element inside it in order to avoid having this </p> issue appear out of nowhere. We also had to remove or place elsewhere many elements the website had before we start managing it (in order to make it pass the validator) which changed the way look of the website.

    You should definitely see these errors as they date from 2016…

    You may close this ticket.

    #1361065

    Very often it is caused by WordPress autop function.
    Can you try these filters if it will solve that issue:

    remove_filter( 'the_content', 'wpautop' );
    remove_filter( 'the_excerpt', 'wpautop' );
    remove_filter( 'widget_text_content', 'wpautop');

    refresh merging of enfold js and css rules – and refresh all cachings ( browser or optimization tools)

    ____

    Sometimes it is caused by manually make some errors in f.e. editor by adding tags yourself.
    W3C it is not allowed to have block-elements inside p-tag ( including p-tag itself)
    see here a list of allowed elements inside p-tag: https://html.spec.whatwg.org/#phrasing-content
    f.e. no ul nor ol tag etc.

    and btw: i do not see any errors on your starting page! : Link
    only warnings are present

    #1361077

    It’s not THAT simple. And of course when developing, no caching is being used.

    The theme’s page builder has the issues. Now, main language has no problems, second language has problems out of nowhere although we use WPML to make the translations…

    Anyway, this thread can be closed.

    #1361109

    Hi,

    Thanks for the update. Could you let us know how to reproduce the problem you were seeing on your end? If you could share your method of fixing it more specifically, then that would be appreciated as well.

    Best regards,
    Rikard

Viewing 6 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic.