Accessibility issues with core embed block's handling of Flickr and TikTok

[markcmorantt]

There is an accessibility error with the embed iFrame for Flickr and TikTok. Specifically, that the iFrame is missing a title, with no "title" attribute, or the "title" attribute being empty. Site Improve is requesting that the frame provide an attribute titie="", and to add a description of the content in the title.

There is also an "Link without a text alternative" message for the <a data-rapid="flickr"... > link, stating that "links should always have a text alternative". In order for a link to be readable by screen reader users links must all contain either plain text, or in the case of a linked image, alt text describing where the link goes. If the linked image contains text, a good general rule is to make the alt text the same, or similar to the text in the image.

The same issue goes with the inline (iframe) frame, that does not include a text altnerative.

All three of these issues will lower page accessibility for those using screen readers.

Thanks for your help.

[markcmorantt]

Another related note is that the blocks mentioned are not navigable by keyboard, which is causing another accessibility warning with Site Improve.

I'm unable to add other attachments for the Tiktok issue screen shots, but they are essentially the same as the one shown in these attachments.

Also, apologies if my formatting for this ticket is completely wrong. I don't have a lot of experience submitting tickets to WordPress so I'm sure there are a lot of issues with how I'm posting this up. Apologies for any confusion.

[markcmorantt]

Replying to sabernhardt:
Thank you!

[joedolson]

We're not able to do anything at all about the content within the iframe; that's provided by the media provider, in this case Flickr. However, we should be able to add a title attribute to the iframe itself, so that the container is labeled for screen readers.

We'll probably want to do something similar to what we did for the YouTube oEmbed: https://core.trac.wordpress.org/attachment/ticket/40245/40245.3.diff

[joedolson]

I've done some exploration of this, and have not been able to reproduce this issue. Can you provide specific step-by-step methods to reproduce this?

Specific examples to embed and the steps followed to embed them on the page would be very helpful.

[oglekler]

Because we don't have steps to reproduce the issue, there is no activity in the ticket, and we have 11 days until RC1, I am moving this ticket into the next milestone for further investigation.

[audrasjb]

As per today's bug scrub, we decided to move this ticket to Future Release to give it more time to get a patch.

[joedolson]

Since we were unable to replicate the issue as described, and we have no option to fix issues inside the embed itself, we're closing this issue as worksforme. If you're still experiencing this issue and can provide steps to replicate consistently, please feel free to comment or reopen.