Thanks again, I worked with Claude to get this script I could drop in the child theme functions file, so I don’t have to copy any of the files to the child theme — lmk if you think it’s a problem. With the script and css below I got everything looking and working as it was, but now with “buttons”. After all that work, I’m wondering (and should’ve asked earlier): Do you even agree the sorting items as links were an accessibility issue? If it all looks good to you, feel free to close this thread.

/* JavaScript to convert sorting links to buttons */
add_action('wp_footer', 'child_masonry_links_to_buttons', 999);
function child_masonry_links_to_buttons() {
    ?>
    <script>
    jQuery(document).ready(function($) {
        // Convert all masonry sort links to buttons
        $('.av-masonry-sort a[data-filter]').each(function() {
            var $link = $(this);
            var $button = $('<button type="button"></button>')
                .attr('data-filter', $link.data('filter'))
                .attr('class', $link.attr('class'))
                .html($link.html());
            
            $link.replaceWith($button);
        });
        
        // Re-bind click events to buttons
        $('.av-masonry-sort').off('click', 'a').on('click', 'button', function() {
            var current = $(this),
                linktext = current.html(),
                selector = current.data('filter'),
                masonry = current.parents('.av-masonry').eq(0),
                container = masonry.find('.av-masonry-container').eq(0),
                links = masonry.find('.av-masonry-sort button'),
                activeCat = masonry.find('.av-current-sort-title');

            links.removeClass('active_sort');
            current.addClass('active_sort');
            container.attr('id', 'masonry_id_' + selector);

            if(activeCat.length) {
                activeCat.html(linktext);
            }

            // Trigger isotope filtering
            var filters = selector ? {filter: '.'+selector} : {};
            filters['layoutMode'] = 'packery';
            filters['packery'] = {gutter:0};
            filters['percentPosition'] = true;
            filters['itemSelector'] = "a.isotope-item, div.isotope-item";
            filters['originLeft'] = $('body').hasClass('rtl') ? false : true;

            container.isotope(filters);
            
            setTimeout(function() { $(window).trigger('debouncedresize'); }, 500);
            return false;
        });
    });
    </script>
    <?php
}

/* sorting menu styling accessible buttons */
.main_color .av-sort-by-term button {
    border: none;
    color: #fff;
    background: #0076a8;
    padding: 6px 15px 8px;
    text-transform: capitalize;
    font-size: 15px;
	margin: 3px 3px 0 0;
  	font-family: 'sarabun',Helvetica,Arial,sans-serif;
}
.main_color .av-sort-by-term button:hover {
    background: #b6bd00;
	transition: .25s;
}
.main_color .av-sort-by-term button.active_sort {
    color: #fff;
	background: #b6bd00;
}

Well, now the client deleted the dev site, so, you’re off the hook on this one ;). Thanks, anyway. Feel free to close this thread.

Thanks again, Ismael — I found that on line 32 and another, similar line on 213, but changing those didn’t seem to work. Then I found on('click', 'a', methods.masonry_filter) on line 279 — I changed that a to button and that seemed to complete the fix. Now I just have to style the buttons. And again, I’ll have to reinstate these changes if these files are updated in future theme updates, right?

OK, thanks again, Ismael! Feel free to close this thread.

Ah, sorry — I see what you’re seeing when I use the inspector, but for some reason — no matter how much I clear the cache, use different browsers, private windows, etc. — if I view the page source I still see that 2nd “main” (https://snipboard.io/ZYdU26.jpg) — is it just that the page source somehow sticks in the cache in a way I don’t understand / know how to clear?

Got it — any other ideas for how to get this element to meet accessibility guidelines?

Thanks so much, Ismael — that seems helpful to at least get them to show the focus / get them in the tab index — I guess it’d be pretty tricky to get the content to show on-click, eh?

Hey Ismael, just checking back in to make sure someone’s still working on this.

Thanks, Ismael — the site is actually live with this issue at https://crcamerica.org/ — it’s a site that’s been managed by the client for many years and they just reached out to me with this issue. So, no need to move it to continue building — they just want to be able to edit the affected elements on the live site. Happy Holidays to you and the crew, too — lmk if you have other questions!

Thanks again, Ismael! Interesting — the temp login isn’t expired, but here’s another one in the PC, also good for a week. I spoke with wp engine support and they troubleshot for about a half hour but couldn’t solve it. They showed me how to look in the inspector > Network > trigger the error > click on the first admin-ajax.php > Response and note how there’s just a “1” (https://snipboard.io/RJ7US6.jpg) as opposed to the html that should show there — they suggested I pass that info on to you in hopes it might provide a clue. I also added another environment in the same account, to test a clean install of Enfold there, and there doesn’t seem to be an issue with that install; no errors on buttons, etc. / functioning normally, if that offers any clue / potential solution. Lmk if you have any other questions.

Ah, ok, here’s the real deal: https://snipboard.io/nyo9vp.jpg
And I had to move the dev site to a new url: https://devcrc.wpenginepowered.com/
And there’s a new temp login in the private content.
Thanks again!

Thanks, Ismael! It looks like wpengine has an error log in the user portal — I copy/pasted the JSONs for what looked like the most recent three errors below — does that give you the info you need? Here’s the full log, too, if it helps: https://crcamericadev.wpenginepowered.com/wp-content/uploads/crcamericadev-logs-2025-12-16T08_23_26.csv

{
“installName”: “crcamericadev”,
“environment”: “DEV”,
“type”: “error”,
“date”: “2025-12-16T07:00:46.000Z”,
“severity”: “notice”,
“client”: “49.149.68.94:0”,
“message”: “auditor:event=profile_update {\”user_id\”:8,\”blog_id\”:1,\”event\”:\”profile_update\”,\”current_user_id\”:8,\”remote_addr\”:\”49.149.68.94\”}, referer: https://crcamericadev.wpenginepowered.com/wp-admin/post.php?post=40933&action=edit”,
“uuid”: “363ffd3e-4ddf-4663-99f2-2087ff23cfb1”
}

{
“installName”: “crcamericadev”,
“environment”: “DEV”,
“type”: “error”,
“date”: “2025-12-16T07:00:44.000Z”,
“severity”: “notice”,
“client”: “49.149.68.94:0”,
“message”: “auditor:event=profile_update {\”user_id\”:8,\”blog_id\”:1,\”event\”:\”profile_update\”,\”current_user_id\”:8,\”remote_addr\”:\”49.149.68.94\”}, referer: https://crcamericadev.wpenginepowered.com/wp-admin/post.php?post=40933&action=edit”,
“uuid”: “b926ecae-71e8-4fb4-a782-11c298d2ca0d”
}

{
“installName”: “crcamericadev”,
“environment”: “DEV”,
“type”: “error”,
“date”: “2025-12-16T07:00:13.000Z”,
“severity”: “notice”,
“client”: “49.149.68.94:0”,
“message”: “auditor:event=wp_login {\”user_id\”:8,\”blog_id\”:1,\”event\”:\”wp_login\”,\”current_user_id\”:8,\”remote_addr\”:\”49.149.68.94\”}, referer: https://kriesi.at/”,
“uuid”: “2748a21e-c9f6-4b3d-a12c-ee78ab39909f”
}

Oops, duh!! Sorry, thanks! (love an easy fix! ;)

Ahh, thanks, Rikard — sorry, I had reviewed the setup section of that documentation, but I missed the troubleshooting section. I had tried enabling the Geocoding API, yesterday, and, while everything else seemed to be taking effect immediately yesterday, that didn’t seem to work. But today, prompted by reading the troubleshooting section, I tried enabling the Geocoding API again, and it immediately worked — with that on, the site connects to the API key; with Geocoding disabled, it does not. Any idea why this site seems to require that, while none of the other 5 Enfold sites seems to require it to connect to the key?

OK, thanks, Mike — will do re the feature request.