I have recently performed a Lighthouse Audit on Google Chrome for my mobile site and it failed on a few issues in the Accessibility category. Please see the list below and advise how these can be fixed:
Buttons do not have an accessible name
<i class=”td-icon-search”></i>
Links do not have a discernible name
<i class=”td-icon-close-mobile”></i>
<i class=”td-icon-font td-icon-mobile”></i>
<i class=”td-icon-menu-right”></i>
Hi,
Please provide some more details with the problem, and some screenshot .
Thank you for your understanding.
The mobile theme failed on some accessibility issues in the Google Chrome Lighthouse Audit. Users are not able to discern the purpose of button that has no accessible name. See the image below:
Hi,
For a better inspection please provide your website url, end we’ll check if there is a problem.
Thank you for your understanding.
I think there is some misunderstanding. The issue is with the theme, not my website. If you go to your own website Tag Div Newspaper Demo Page on Google Chrome then to Developer Tools and Audit, the results will bring the same issues I have experienced with my website.
Certain buttons and links on the theme do not have accessible or discernible names. As a result, google is giving a poor score for Accessibility, which can affect page ranking.
Please see the screenshot below:
Please can you let me know when the fixes have been implemented.
Ok, keep in touch.
Thank you.
Hello @Dev_wp
For Accessibility issues with mobile theme in Lighthouse, go to mobile/parts/header-menu.php
Add button or anything else before /i>/a>
Screenshot:
https://drive.google.com/file/d/1FjCz9Z5IeOiPaIVVV2Q_nfimELltiDj2/view
Sorry, i mean like it
https://drive.google.com/file/d/1FMkdoVFF5zzbVvsMC4nlr9ZxI4Pnc_c8/view
Thanks @fikrizaky2711
I am using a Child theme. Would I need to create a new header.php file in my child theme?
@Calin, you said on the 3rd December 2018: “I note this on our issue list, we’ll make some investigations/test and implemented some fix’s.” As far as I am aware it is not a major correction to fix, yet has not been fixed yet
However, I am starting to feel that the people running the theme are not focusing on important issues such as improving the speed and functionality of the site.
Rather, the impression that many are getting is that you are simply trying to attract more people with features that are not all necessary. For example, have you asked your customers whether they need features such as Logo Creator? which adds extra bloat to the site and is probably unnecessary as most people are happy to make a logo offsite and upload it.
Whilst, I understand you need to make money by attracting more customers, you are going to loose many customers who will find other themes that are more focused on speed, clean coding and fixing important errors.
I agree that the Live Header Search and Auto Loading are good features, but they should be accessible from the theme panel, without having to use another plugin.
I have to be honest, I am getting very upset with how the theme is being run. You have recently announced a “big update” but are not listening to loyal customers who want a fast, clean site that is easy to update and where SEO issues and other problems are fixed quickly.
Hi devy,
The problem with the accessible or discernible names is still in work, that is way we did not set the fix for mobile accessibility in this update, there are more elements that was change and need to be tested, so in the coming updates, will be implemented this fix too, sorry for the inconvenience!
Please note that all the features that the team developers implemented in this update has been requested by our customers.
Also our team developers are working to the theme optimization/speed that is way those plugins appear, the customers will use it only if they need the feature from that plugin, if note will no install/activate the plugin.
Thank you for your understanding!
2 year later and we are facing the same problems, with another item:
Buttons do not have an accessible name:
a.tdb-header-search-button-mob.dropdown-toggle
Form elements do not have associated labels:
input#login_email-mob.td-login-input
input#forgot_email-mob.td-login-input
Links do not have a discernible name
Hi josp, we from the support team are trying to do all we can to provide a good support and support our theme and members, unfortunately when is coming to suggestions, improvements, problems … all we can do is to note theme on our list that and from there our developers check the list and decide further.
Thank you for your understanding and sorry for the inconvenience, I will make again a note about this problem.
Well, that’s a shame!
I thought the support was supposed to, well.., support; that is, give us support for resolving problems, not only forwarding a note to some unknown team, that seems to not read your notes, since this is a problem with more than 2 years!
Hi josp, I understand what you are mean, but please notice that the support team can provide only support and no implementation of code. Usually those problems appearing when you are using the responsive version of theme, using the mobile theme plugin you’ll get better results.
Also since now all is around on Largest Contentful Paint and Cumulative Layout Shift our developers will try that the coming them updates to have better results in lighthouse.
Thank you for your understanding!
I was using the mobile theme, and there was no difference between one or another. I’ve made the change when you guys introduced the option to do the mobile version of the pages, without the need for the mobile theme (that was only adding space and resources)…
Nonetheless, if this problem is related to me not using the mobile theme, then it is your fault, as you (the team) proposed us costumers to use the mobile pages version, in mid October.
Hi josp, normally there should be no problems using the mobile page, I will make some deep investigations and send a note to our developers with the results.
Thank you for your understating!
Ok! If you could share your notes with me, I’ll be glad.
Thanks!
Calin it seems NewsPaper developer teams is not fixed the issue yet even with recent update. Now Dec End 2020 but still the problem is exists which is really disappointed.
I feel its simple code changes in the theme, but I’m not sure why it’s taking so long to fix it.
I’m getting less score because of the issue otherwise my site will be 100% in Accessibility score.
Google is going to start mobile First Indexing from March 2021 so scores are important. If this continues then sure it will affect badly.
I’m using Mobile plugin theme only. FYI
Thanks
Giri
Hello !
We are sorry for the inconvenience !
Our developers are now focusing 100% on making sure that 2021 updates are helpful for the new plans that Google has. Starting from January this will be the main goal of each update that they are already working on.
Thank you !
Thank You Vlad.
Hope the issue will be fixed soon and will get performance related update as well.
Giri
I am also facing LCP and other issues. Earlier it was not there if I am not wrong.
Please fix asap.
Thanks!
@ Calin,
@Fikri Zaky is giving a method to fix this above, can i savely do this? If so, can you please show me where to add the text because i see the ‘/i>/a>’ tag two times. I know this will be gone after an update. When will this be permanently fixed on TagDiv side? Seems a pretty small issue. Thanks!
