nunowp

And the solution is…

I also have this problem, but it seems that the team has other priorities at the moment.

However, my site has dropped several positions in the google organic search rankings because of it.

Apparently the bug was introduced 2 versions ago. I’m sure of this because I often monitor the rankings at the end of each relevant update.

Let’s hope there’s interest in resolving it.

https://www.ads-software.com/support/topic/pagespeed-accessibility-errors-last-update-3/

Hi @doublezed2,

Thanks for your reply.

Well… as you know, reverting a theme is not the same as reverting a plugin that manipulates a database. It’s risky.
I concluded, and I concluded well since I only updated these two plugins, so if it’s not one it’s the other.

I’m sure you’ll also be able to simulate and test internally.

If there is no interest, I will solve the problem with code, as usual. That way we all lose.

Hello @doublezed2,
Thank you for your reply.
Indeed, I thought it was related to the theme, I’ve already explained it on their forum, and I’ve come to the conclusion that it’s not related to the theme.

That’s why I’d appreciate your help, as I’m pretty sure the error was introduced with the latest version of woocommerce (I’ve only done these two updates).

I actually downgraded the theme to previous version (4.6.0) and the problem persists. I updated the Woocommerce version at the same time, so it can only be that.

In any case, I apologize for the inconvenience, I will report the case in the woocommerce forum.
Thanks

Hi @reynierc,
Thanks for your reply.

I understand that the situation may be related to ARIA role, however as I reported these errors did not occur before I updated the theme to the latest version. It scored 100% in this accessibility field before the update.

The errors are occurring on the product pages, specifically on the side tabs for additional descriptions and reviews.

So I think it was a bug introduced in the latest version of the theme that you should check.

Hi,

I’m getting the same error, had to deactivate the plugin.

2024-09-06T02:17:21+00:00Crítico Maximum execution time of 30 seconds exceeded

{ “error”: { “type”: 1, “file”: “/html/wordpress/wp-content/plugins/woo-product-feed-pro/classes/class-get-products.php”, “line”: 1275 }, “backtrace”: [ { “file”: “html/wordpress/wp-content/plugins/woocommerce/includes/class-woocommerce.php”, “line”: 400, “function”: “critical”, “class”: “WC_Logger”, “type”: “->” }, {

Using WC 9.2.3, PHP 8.3.10, and plugin v.13.3.6

It seems that the problem is related to the mobile search box. As I use the “Advanced Woo Search” plugin for this purpose, I deactivated this box with this custom code and it was solved.

.storefront-handheld-footer-bar ul li.search .site-search {display: none;}

I hope I’ve helped.

Final result ??

https://ibb.co/Fsh0Vpx
https://ibb.co/sRS9hZP

Hi @shameemreza,

Thank you for your reply,
I understand the priority. However, the 3 bottom bar icons in mobile (account, search and cart) are already quite large, so I have no idea what code to put in. I also can’t compare with the previous version of the theme (which didn’t have the error).

Do you have any suggestions?

Hi,

The “Aria” error has been resolved, apparently it wasn’t related to the theme.

At the moment, the error that persists in mobile is:

“Touch targets do not have sufficient size or spacing”?https://imgbb.com/1dGZhqG

Thanks

Hi,

Seems to be fixed now. Thanks!

Hello @carolm29,
Thank you for your reply.

Regarding the error “Elements use prohibited ARIA attributes”, by chance it appeared on the homepage where I have the trustindex reviews plugin.

However, I tested it on a product page and I don’t have this plugin active there and the error also appears.
Can you test it on a product page? I suspect it’s not the plugin. Thank you

• This reply was modified 9 months ago by nunowp.

Hello @ckadenge
Thank you for your reply.

I haven’t made or noticed any changes to the layout, I just applied the latest update to woocommerce and your theme.

I test the site regularly and it was just after these updates. Only if the test is having some problems, but it’s been going on for about a week.

Hi @shameemreza

Thank you for your help.

The code works. However, as my suffix is ({price_including_tax} w/VAT) it works fine when the variations all have the same price, but it doesn’t make sense when the variations have different prices as it always shows the price of the variation with the lowest price under the product title.

I managed to solve it by changing this field “. wp_kses_post( $suffix )” for “. wp_kses_post( ‘ w/VAT’ )” on line 12.

However, when the variations are all the same price, it naturally also shows this suffix and I end up without the price with VAT calculated because when I choose the variation, if they are the same, by default no price appears below the variation box because it’s supposed to be in the title.

By the way, another question: do you expect a significant drop in page performance with this type of custom code in functions.php? Thank you

It actually affects 4% less in the pagespeed insights accessibility score. I used to get 100% before the theme update, which is why I asked the question.

But I fully understand that the support staff have other more important issues to deal with.

Thanks for your attention anyway.