Forum Replies Created

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • in reply to: No p element in scope but a p end tag seen #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.

    in reply to: No p element in scope but a p end tag seen #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.

    Hello,

    For one, 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.

    For two, your support is so slow (4 days to reply…) that 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).

    You should definitely see these errors as they date from 2016 as mentioned in my other thread…

    Below i give you the errors from the validator. We had kept them in a notepad.

    You may close this ticket.

    ————————————————————–

    Nu Html Checker

    This tool is an ongoing experiment in better HTML checking, and its behavior remains subject to change
    Showing results for https://dimitrawines.gr
    Checker Input

    Show sourceoutlineimage report

    Check by

    moved to: https://pastebin.com/2qPqAWJJ

    • This reply was modified 1 year, 8 months ago by ik. Reason: private reply

    Hello,

    Almost 48 hours later and no reply. In the meantime, tickets opened later than ours did get a reply.

    How does that make any sense? Is there a selective support?

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