Elements with an ARIA [role] that require children and List items () are not

And I would have a totally different issue which occurred after updating to this newest version of your theme. After minifying everything I get the Lighthouse message in cosole: Uncaught TypeError: Cannot read properties of undefined (reading ‘register’)
at avia-footer-scripts-4619b90d68aa84bacc54710dbd11c254—646ab7de6a4c4.js?ver=1684715613:21:73885
at avia-footer-scripts-4619b90d68aa84bacc54710dbd11c254—646ab7de6a4c4.js?ver=1684715613:21:73966

and if I click on it to show where the problem is exactly I get the following:
aviaJS.aviaPlugins.register(avia_js_shortcodes.aviaFoldUnfoldSection, ‘.avia-fold-unfold-section’)

I opened another thread about it but it was of no help.
I copy the URL of that thread maybe you can work something out.

I am also writing an admin login into the private area because in the previous thread you asked for that so that you can check.

Many many thanks for your help,

Thank you again for your help?

P.S: I am attaching a screenshot of the Lighthouse result.

• This reply was modified 1 year, 6 months ago by davidv126. Reason: Attached a screenshot

So with chatgpt I could temporary fix the uncaught typeerror with the following js

(function() {
  function aviaFoldUnfoldSection(element) {
    var sectionElement = document.querySelector(element);

    sectionElement.addEventListener('click', function() {
      if (sectionElement.style.display === 'none') {
        sectionElement.style.display = 'block';
      } else {
        sectionElement.style.display = 'none';
      }
    });

    // Additional code for the functionality of the plugin
    // ...

    // Return any necessary values or objects (if needed)
  }

  if (typeof aviaJS !== 'undefined' && aviaJS.aviaPlugins) {
    aviaJS.aviaPlugins.register(aviaFoldUnfoldSection, '.avia-fold-unfold-section');
  } else {
    console.error('aviaJS or aviaPlugins is undefined');
  }
})();

I also had to add to the functions.php of the child theme the following:

function enqueue_custom_scripts() {
  wp_enqueue_script('avia-fold-unfold-section', get_template_directory_uri() . '/js/avia-fold-unfold-section.js', array('jquery'), '1.0', true);
}
add_action('wp_enqueue_scripts', 'enqueue_custom_scripts');

But it works if the javascripts are minified within theme settings performance. After merging I am back to square 1. So it is at least a fast fix till I get the normal one in order for my site to be at least usable.

The section.php however didn’t work. I copied it to my child theme changed the line but the lighthouse errors are still there.
Can you please provide me with a fix, as well?
https://yourimageshare.com/ib/eEpwX1XA5f

Last but not least if somebody has an idea how to remove inline CSS don’t hold it back.
I am attaching a screenshot:
https://yourimageshare.com/ib/lzyCFyG4MG

Hopefully that is all and thank you in advance.

So this one would be a solution to which? I asked 3 different questions and none has been solved so far.
Thank you for your answer

So I guess this is the topic about the lighthouse errors the list items and the focusable descendants and unfortunately this section.php could not fix my issue.

I guess this should be the one thread about the menu items.

Thanks again

Yes and the accessibility issues with Lighthouse but you wrote that this section.php would fix both however it did not.

:’I believe this is the solution for both.

Best regards,
Mike’

Thanks and sorry but my webmaster left me here without even a word so I gotta do it for myself.

Actually I am very grateful for this as the error is gone.

So thanks again on this one.

However you didn’t come across those focusable descendants because in the home page the slider is 100% so you don’t get there unless you scroll down but it occurs at all the other pages.

I am copying here the issue (error message) and down in the private section I will attach a couple of URLs:

Focusable descendents within an [aria-hidden=”true”] element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how aria-hidden affects focusable elements.

The URLs found below all come up with the same error.
A huge thank you for this as well since it was a huge help
And if you happen to come up with any fast and practical solution just like you did, I’d appreciate that.

THanks and thanks again

Thank you for your answer,

I believe those ones are not the one implemented in my footer, since I have put the following in the footer:
[av_font_icon icon='ue8f4' font='entypo-fontello' style='' caption='' size='40px' position='left' color='' link='manually,https://www.facebook.com/'username'/' linktarget='_blank' animation='' id='' custom_class='' av_uid='av-dce4o' admin_preview_bg=''][/av_font_icon][av_font_icon icon='ue909' font='entypo-fontello' style='' caption='' size='40px' position='left' color='' link='manually,https://www.instagram.com/'username'/' linktarget='_blank' animation='' id='' custom_class='' av_uid='av-8vgx4' admin_preview_bg=''][/av_font_icon]

Well of course I am not an expert at any of this but I have a feeling it is connected to something else about which I am sending a screenshot.

https://yourimageshare.com/ib/V0CGL0nt3d

Of course I am not sure the only thing I am guessing that is they are below the scroll-down-link