- πΊπΈUnited States smustgrave
This came up as a daily BSI target.
Is the issue here that the alt text is not included in the embed code? Is that really a problem though?
When an author embeds image media in the wysiwyg editor, they can choose to:
If they accept the default alt text (because it is appropriate for the context) this isn't explicitly recorded; i.e. nothing is stored in the editor markup.
BUT if the default alt text stored with the media entity changes at a later date, then the new alt text propagates to the all existing embed instances which haven't overridden it.
The problem is that the original alt text may have been accepted because is was appropriate to the context, but the new alt text might not be. The upshot is that there may be unintended side effects, where content effectively changes it's meaning.
This is almost in the realm of accidental data loss.
When authors embed a media image, and accept the default ALT text from the media entity, explicitly store it in the <drupal-media alt="whatever"
markup.
TBD.
TBD.
TBD.
None?
Active
11.0 π₯
media system
It affects the ability of people with disabilities or special needs (such as blindness or color-blindness) to use Drupal.
Issue summaries save everyone time if they are kept up-to-date. See Update issue summary task instructions.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
This came up as a daily BSI target.
Is the issue here that the alt text is not included in the embed code? Is that really a problem though?