Make Asset Entity implement the Translatable-interface to allow multilingual asset meta data

[DanielBiegler]

Is your feature request related to a problem? Please describe.

International shops need to provide multilingual alt-attributes for images and other assets to better comply with web accessibility guidelines.

Describe the solution you'd like

Make Asset Entity implement the Translatable-interface to allow multilingual asset meta data.

That would allow users to add customfields of type localeString and localeText to their Assets.

Describe alternatives you've considered

None.

Additional context

Right now if you try to add a custom field of type localeString to the Asset entity you get blocked by the validation, see here.

That validation misses checking for type localeText but this gets caught during runtime, see here.

[timcv]

Would you consider adding a set of standard fields to the Asset entity in Vendure to help encourage WCAG compliance out of the box?

For example, in WordPress each media asset includes these fields by default:

• Alternative Text – Short description for screen readers (WCAG 1.1.1), typically rendered as the alt attribute on <img> or <area> elements.
• Title – Short label for the asset, often used as metadata or as the title attribute on <img> or <a> tags.
• Caption – Short piece of text displayed alongside the asset, often wrapped in a <figcaption> within a <figure>.
• Description – Longer explanation or context, which can be surfaced in various ways, e.g. as body text below the image or referenced via aria-describedby.

Having these as built-in (and translatable) fields could make it easier for developers and content editors to meet accessibility requirements without having to manually extend the schema for each project.

Would this be something you might consider as default fields for assets?

[timcv]

👋 @dlhck
Just wanted to check in, is this still planned for inclusion in the 3.5 release?

Thanks again for keeping accessibility improvements on the roadmap!