Thanks as always, Ismael — Claude gave me the following to change the code you referred to:

$sort_loop .= 	"<span class='text-sep {$term->slug}_sort_sep {$show_item}'>/</span>";
$sort_loop .= 	'<button type="button" data-filter="' . $term->slug . '_sort" class="'.$term->slug.'_sort_button ' . $show_item . '" >';
$sort_loop .=		'<span class="inner_sort_button">';
$sort_loop .=			'<span>' . esc_html( trim( $term->name ) ) . '</span>';
$sort_loop .=			"<small class='avia-term-count'> " . $term_count[ $term->term_id ] . ' </small>';
$sort_loop .=		'</span>';
$sort_loop .= 	'</button>';
				}
				$allowed_terms = json_encode( $allowed_terms );
$output .=	"<div class='av-sort-by-term {$hide} ' data-av-allowed-sort='{$allowed_terms}' >";
$output .=		'<button type="button" data-filter="all_sort" class="all_sort_button active_sort">' . $first_item_html . '</button>';
$output .=		$sort_loop;
$output .=	'</div>';

That seems to have changed the links to buttons, but it broke the sorting functionality (see https://abodedev.wpengine.com/communities/). Claude says “The issue is that the JavaScript handling the masonry sorting is still looking for tags. You need to find and update the JavaScript file that handles the masonry sorting functionality.” Does this all make sense to you and if so can you point me to the other file code I need to change? Thanks again so much!

Nice — thank you so much! This seemed to work for me: to just duplicate the event listener for mouseenter, change mouseenter to click, and comment out the event listener for mouseleave (see below). Do I have to minify the file and overwrite icon_circles.min.js? And do I have to re-implement this every time I update the theme, or is there a way to handle it through the child theme?

				logos.on( 'mouseenter', function()
				{
					logos.removeClass('active');
					logoText.removeClass('active');

					var logo = $(this).addClass('active');
					logo.next().addClass('active');
					container.addClass('active-container');
				});
                
                logos.on( 'click', function()
				{
					logos.removeClass('active');
					logoText.removeClass('active');

					var logo = $(this).addClass('active');
					logo.next().addClass('active');
					container.addClass('active-container');
				});

/*				container.on( 'mouseleave', function()
				{
					logos.removeClass('active');
					logoText.removeClass('active');
					container.removeClass('active-container');
				});*/

Thanks again, Guenni! I’m not sure this is the right solution for us — I’m going to talk with the accessibility consultants about our options — but I appreciate your thoroughness, as always, and will keep this in my back pocket!

Thanks so much, Ismael, but this doesn’t seem to be working for me as-is — I dropped it in at the top of the functions.php for the child theme (https://snipboard.io/G9XSTj.jpg), but I’m still seeing two “main” landmarks (one for the footer-page) on https://abodedev.wpengine.com/about/story/ for example. Any idea what I might be doing wrong?

Thanks, Ismael, and thanks, Guenni — but Guenni, doesn’t that description only come available to the user if they click through to watch the video on YouTube or Vimeo? If they’re just watching the embedded video on your/our site, they don’t get that description, right?

Thanks so much, Ismael — glad you’re on the trail. No need to keep the modification on the dev site — I’ve downloaded that file so I can post it to the live site, if I want to implement that temporary fix for the client. Thanks again and Happy New Year!

Sorry, I think wpengine support may have deactivated the temp login plugin when they were troubleshooting. It should be working now, but here’s an actual user just in case. They also said the max on the hosting is 512, so even if you up it to 1024 it limits it to 512. But I run a bunch of Enfold sites with them and never had a memory issue like this — we shouldn’t have to up it that high, right? Maybe you’re just trying to do that temporarily to troubleshoot? Regardless, it doesn’t sound like they can do that for us, but I can double-check if you want; lmk. Thanks again for sticking with this!

Thanks, Ismael — sure thing, details in the PC below — and lmk if you need me to reach out to wpengine support.

Thanks, Rikard, but I increased the memory to wp engine’s max of 512MB, ran another test, and the issue seems to persist. The only things I see in the log since doing that are what look like my two times clearing the wp engine cache (once after increasing the memory to 256 and once after bumping it up to 512 — see below or https://crcamericadev.wpenginepowered.com/wp-content/uploads/crcamericadev-logs-2025-12-16T19_28_03.csv). Any other ideas? I’m including the temp login again in the Private Content field, in case you want to poke around. Thanks again!

{
“installName”: “crcamericadev”,
“environment”: “DEV”,
“type”: “error”,
“date”: “2025-12-16T19:24:37.000Z”,
“severity”: “notice”,
“client”: “24.24.164.87:0”,
“message”: “wpe_cache_plugin:info: event=clear-all-cache, referer: https://crcamericadev.wpenginepowered.com/wp-admin/edit.php?post_type=page”,
“uuid”: “8b6d00fd-38e3-44d3-903b-9166dbc7f21a”
}

{
“installName”: “crcamericadev”,
“environment”: “DEV”,
“type”: “error”,
“date”: “2025-12-16T19:17:43.000Z”,
“severity”: “notice”,
“client”: “24.24.164.87:0”,
“message”: “wpe_cache_plugin:info: event=clear-all-cache, referer: https://crcamericadev.wpenginepowered.com/wp-admin/media-new.php”,
“uuid”: “a746b3bf-7e06-48bd-994c-ce6d04e249d2”
}

min-height! why didn’t I think of that?! ;).

Thanks again, Ismael — that worked for desktop but not the phone, for some reason — removing the first class seemed to make it work for both, and I only needed about half the height:

.tribe-events-c-subscribe-dropdown {
   min-height: 175px;
}

Thanks again, as always!

Hmm, just when I thought I finally had that stuff wired ;). OK, thanks anyway! Feel free to close the ticket.

Awesome — sorry to pick faves, but you’re the best, Ismael ;)

Ah, I see, ok, thanks. And what about the flipboxes on desktop, further down on the home page of https://tortoise-tracks.org/ — I don’t suppose there’s any way to make those accessible via the focus? I mean, I can see the focus is indeed cycling through the links in those, but I don’t supposed that’d be enough to meet the accessibility standards, eh? Should I open a separate post about that?

Thanks again for the detailed explanation. Looks like the css “content” property is pretty well supported — https://caniuse.com/mdn-css_properties_content — good enough for me, I think! :)

Perfect, awesome, thank you so much! I also added my own class to the columns and added some css to adjust the height to taller than the max 500px allowed in the options (just in case this helps anyone else):

.taller .avia-fold-unfold-section .av-fold-unfold-container.folded {
    max-height: 1000px !important;
}

Thanks again!