accessibility: blog posts component

it would appear to be part of config-templatebuilder\avia-shortcodes\postslider.php that the Blog Posts actually renders the item with, not blog.php.
$output .= $thumbnail ? "<a href='{$link}' data-rel='slide-".avia_post_slider::$slide."' class='slide-image' title=''>{$thumbnail}</a>" : '';

it’s the $thumbnail part we need to change in this instance to remove the alt

the correct method seems to be passing false to the alt parameter in the third argument
$thumbnail = get_the_post_thumbnail( $the_id, $image_size, array( 'alt' => false ));

we don’t really want to edit core theme files and I imagine this solution would normally be preferable, using a regex

add_filter( 'post_thumbnail_html', 'remove_thumbnail_alt', 10, 5 );
function remove_thumbnail_alt( $html, $post_id, $post_thumbnail_id, $size, $attr ) {
    $html = preg_replace( '/(alt)=\"(.*?)\"\s/', "", $html );
    return $html;
}

however I’m not sure we can run this function for only the blog posts entries

if we need to add a conditional to the core postslider.php file output to remove the alt if a title is available in the pod text, we need to make it a conditional on these render types
title, excerpt_read_more, title_read_more

therefore for now I’ve added a patch to postslider.php

// patch: remove alt on image if there is a title output on the pod
// $thumbnail  = get_the_post_thumbnail( $the_id, $image_size );
$hasTitle = in_array($contents, ['title', 'excerpt', 'excerpt_read_more', 'title_read_more']);
$thumbnail  = get_the_post_thumbnail( $the_id, $image_size, ($hasTitle ? array('alt' => false) : null));

again we’d rather not edit core theme files, but I see no other solution really using filters/hooks

Hi.

It’s the “Blog Posts” component. This appears to use postslider.php, however when I copy it to my child theme with the same path it does not seem to pick up the new code

please can you confirm that placing it at
my-child-theme\config-templatebuilder\avia-shortcodes\postslider.php
should allow me to change it there?

I’m not sure why it didn’t work if that’s the case, unless it’s a caching issue

Thanks
Joe

thanks that works for me!

Our workaround will do for now thanks so the topic can be closed, but please be aware of the accessibility issues with the theme .