PageSpeed Insights related with wc-template-functions.php

  • Resolved nicole0155

    (@nicole0155)


    1 year, 3 months ago

    I’m getting the warning “Elements with visible text labels do not have matching accessible names.”.

    After checking in more detail, I have found that the file /wp-content/plugins/woocommerce/includes/wc-template-functions.php contains the line 

    echo '<a aria-label="' . sprintf( esc_attr__( 'Visit product category %1$s', 'woocommerce' ), esc_attr( $category_name ) ) . '" href="' . //esc_url( get_term_link( $category, 'product_cat' ) ) . '">';

    with “Visit product category” text that is causing the error. As temporary solution I have replaced this line by 

    echo '<a href="' . esc_url( get_term_link( $category, 'product_cat' ) ) . '">';

    However this error hapens always after any woocommerce update.

    Please fix this in future Woocommerce release / update.

    Thanks

    The page I need help with: [log in to see the link]

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

  • Hi @nicole0155

    Thanks for reaching out!

    I understand that you received the error message Elements with visible text labels do not have matching accessible names after you updated your WooCommerce to the latest version, correct?

    I’ve checked the Github repository, however, I did not find any related cases to your issue.

    It looks like a third-party plugin or your theme might be causing the conflict here.

    For us to investigate this further, can you please try to switch to the default Storefront theme and only WooCommerce plugin is enabled and see if this works?

    If so, then this kind of problem is usually caused by your theme or a third-party plugin present on your site. We can run a conflict test to verify this. I’d recommend cloning your site to a staging environment and performing the tests described on this guide without modifying your live site or impacting customers. Many hosts provide staging facilities, so it’s worth checking in with them. It’s also possible to do it using the free WP Staging plugin.

    If this was caused by a third-party plugin present on your site, it would be best to reach out to the developers for further assistance here.

    If this did not resolve the issue, please share your System Status Report, that will help us further troubleshoot.

    You can find it via WooCommerce > Status. Select Get system report and then Copy for support. Once you’ve done that, you can paste it into your reply here.

    If you could also provide the fatal error logs (if any) under WooCommerce > Status > Logs.

    You could copy and paste your reply here or paste it via https://gist.github.com/ and send the link here.

    Or, if you’d like someone else to do this work for you, our trusted partner, Codeable, has an offering where they will run this test for $150 USD. If there is time left, they will also fix the problems they found.

    Let us know how it goes!

    Thread Starter nicole0155

    (@nicole0155)

    Hi @xue28

    Sorry if I did not explain in further detail.

    The warning 

    Elements with visible text labels do not have matching accessible names

    its from PageSpeed Insights.

    This is not any conflict, but an error from the plugin file /wp-content/plugins/woocommerce/includes/wc-template-functions.php

    Let me know if the issue is now clear.

    Please fix this in future Woocommerce release / update.

    Thanks

    Hi there @nicole0155 ??

    Thank you for bringing this to our notice. It’d be best to submit an issue via GitHub about this.

    I trust that points you in the right direction, but if you have more questions, let us know.

    We’re happy to help.

    Thread Starter nicole0155

    (@nicole0155)

    Hi @anastas10s,

    Thank you for your reply.

    I do not have access to GitHub, and not sure how to make such report.

    Can you please help?

    Thanks.

    Hey @nicole0155,

    I do not have access to GitHub, and not sure how to make such report.

    Can you please help?

    I’d be happy to guide you ??

    1. Create a GitHub account here: https://github.com/signup
    2. Create an issue on GitHub here: https://github.com/woocommerce/woocommerce/issues/new/choose
    3. Add all the details required on the report and submit.

    Once this has been submitted, our developers will take a closer look from there.

    Hope this helps!

    Thread Starter nicole0155

    (@nicole0155)

    Is there any other way to report one Woocommerce error?

    Thanks

    Plugin Support Shameem R. a11n

    (@shameemreza)

    Hello @nicole0155,

    Opening an issue on our Github repo to report a bug is the best way for our developers to take a closer look at it.

    However, you can also report a WooCommerce error by submitting a support ticket directly to us. Our support team will then review your ticket and get back to you as soon as possible.

    Make sure to include a link to this thread, so we know what has been done already.

    Thanks!

    Howdy,

    We haven’t heard back from you in a while, so I’m going to mark this as resolved – feel free to create a new topic if you need any further help.

    Cheers!

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘PageSpeed Insights related with wc-template-functions.php’ is closed to new replies.