The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: dhananjaykuber <dhananjaykuber@git.wordpress.org>
Co-authored-by: carolinan <poena@git.wordpress.org>
Co-authored-by: fabiankaegy <fabiankaegy@git.wordpress.org>
Co-authored-by: huubl <huubl@git.wordpress.org>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

Hi @carolinan

I have updated the label and also tried to resolve the test using npm run fixtures:regenerate. Still 2 cases are failing and in E2E check its shows Timeout exceeded.

To be honest, I struggle a bit with this feature here 🤔

The issue that worries me is that the featured image block is almost never used in isolation on a single post. Instead the block gets used on single templates and inside query loops. So in both of these scenarios we are not talking about a single featured image for a specific block but rather the generalized concept of a featured image inside a template.

Any setting you apply to the featured image block will be applied to all posts / all featured images.

Knowing that I'm a little worried that the feature will get enabled by folks who want to set it for a single image only. But in doing so they have now removed the alt text from all featured images everywhere.

I know why there is no alt text option for the block, but the lack of an option to enter a custom alt text also makes this option feel awkward.

Any setting you apply to the featured image block will be applied to all posts / all featured images.

Yes this is the case with styling options like borders. Users who are not aware of it may find it unexpected the first time they are using it, but will then learn.
But the difference is that

• A styling option is immediately visually apparent for sighted users, and the alt text is not at all apparent.
• A missing alt text has much greater impact than a style, so a mistake with the alt text is much more severe.

Would it help if the current alt text was visible in the sidebar but not editable?
Would it help to place it in the advanced section? If not, I would perhaps recommend keeping it as a separate plugin.

Would changing the help text depending on the context be a solution? For example:

Default / Post Editor:
"Use empty alt text (decorative image)."
→ Simple and clear guidance for individual image use cases.

When child of Query Loop:
"Use empty alt text (decorative image). Please note: this sets all featured images in this loop to decorative."
→ Warns users of the bulk effect.

Template Editor:
"Use empty alt text (decorative image). This will affect all uses of this template. Ensure that all featured images used here should be decorative."
→ Reinforces the importance of intent at the template level.