Modify shortcodes

do you have entered this snippet to your child-theme functions.php ?

from docu: Link

From within your child theme, you may want to add or edit an Advanced Layout Builder element. To do so, first add the following function to your child theme’s functions.php: …
Now add a new folder in your child theme directory called shortcodes. If you copy an element from enfold>config-templatebuilder>avia-shortcodes to this folder it will replace the one in the parent and be used instead. You can also add new ones using the other shortcode elements as examples.

function avia_include_shortcode_template($paths){
  $template_url = get_stylesheet_directory();
      array_unshift($paths, $template_url.'/shortcodes/');
  return $paths;
}
add_filter('avia_load_shortcodes', 'avia_include_shortcode_template', 15, 1);

and just put the edited alb element directly to that subfolder : shortcodes

Where do you load your jQuery ( see options page of enfold : Performance – “Load jQuery In Your Footer”
if you do load it in the footer maybe a priority to that add_action solves the problem:

replace that one line to

add_action('wp_footer', 'ava_custom_script', 999);

Edit: PS forget it – i see that the code above has an additional dot – remove that dot after av_font_icon :

function ava_custom_script() { 
?>
<script>
	(function($){
		$(document).ready(function() {
			$('#top .av_font_icon a').removeAttr('aria-hidden');
		});	
	}(jQuery));
</script>
<?php
}
add_action('wp_footer', 'ava_custom_script');

priority (999) may not be necessary – only if you load your jQuery in the footer.

everything is said on the answer here: https://kriesi.at/support/topic/modify-shortcodes/#post-1412054

One thing to note is that the name of the function (ava_custom_script) is often used on the forum here – so I prefer to choose a meaningful name; one that immediately says what is being achieved.
Also, the child theme functions.php will resent a repeated occurrence of the function name – and report an error. Function names must be unique.

function remove_aria_hidden_attribute() { 
?>
<script>
	(function($){
		$(document).ready(function() {
			$('#top .av_font_icon a').removeAttr('aria-hidden');
		});	
	}(jQuery));
</script>
<?php
}
add_action('wp_footer', 'remove_aria_hidden_attribute');

Contrary to my opinion that these settlements make sense, I tried to find a solution. Now, unfortunately, I have to throw in the towel. No idea how I could turn this off.
Adding aria-hidden=”true” to the icon hides the icon character from being included in the accessible name.
This is part of WAI-ARIA roles and i do not know why Google has a problem with it.

However, the mistake is that they contain focusable descendants.
i read something about giving to those decendents an attribute: tabindex=”-1″