iFrame plugins must have an accessible name

[jaimewhi]

The Vimeo and YouTube iFrame plug ins do not have an accessible name, which is causing accessibility issues during our audits. We have multiple teams with varied degree of development skill, so custom HTML to correct each time we use these is not feasible. I submitted a support request and they recommended submitting a support ticket.
I don't see this item on the existing tickets. Screen reader users rely on the frame title to describe the content and it can be difficult or confusing for users if the accessible name is missing.

[joedolson]

The core YouTube and Vimeo embeds already have title attributes attached to their iFrames. Can you provide more detail about exactly how you're adding these video embeds?

Screenshots are very helpful for knowing more about how you're adding these to your site.

[jaimewhi]

Sure. It is on a public-facing site, ​https://computing.usc.edu/

Using the axe DevTools you can see the USC Frontiers of Computing iFrame does not have an accessible name.

[joedolson]

Yes, I believe that you're seeing that, and I can verify that it is missing on your site - what I'm asking is what your method is for adding the video to the page, and whether it matches what I'm testing (which is the default oembed behavior, by dropping a link to the vimeo URL in a paragraph block.)

Do you get the same result if you add the same video to a new blank page?

If you have a staging environment, do you have the same results after disabling all plugins and switching to a default theme?

[jaimewhi]

Apologies. The video was added using the Vimeo Embed Block, not directly uploaded to the site. We tried to use the Video Embed Block and the Embed Block, but both automatically switched to the Vimeo Embed Block upon entering the URL because it detected a Vimeo video.

[sabernhardt]

I think the problem might relate to your video's privacy settings, whether Vimeo does not give the title for embedding or they give it in a different way that WordPress does not recognize.

• When I insert https://vimeo.com/76979871, I get a Vimeo Embed block, and its iframe element has a title attribute with the video title (on the front end): "The New Vimeo Player (You Know, For Videos)"
• When I insert your Vimeo video into my local installation, I get an error message: "Because of its privacy settings, this video cannot be played here."

[joedolson]

Based on the reporter's feedback and @sabernhardt's comments, this seems to be specific to privacy settings.

It seems like the Vimeo oEmbed endpoint is giving different information for different parts of the embed API if the video has privacy controls.

We should explore this further to determine whether we can get that data for private videos. If we can, then it makes sense to fix the issue; but if it's just not available, then we may need to close it or report upstream to Vimeo, if that's relevant.

[rollybueno]

Looks like the video on ​https://computing.usc.edu/ is now using <video> markup instead of iframe so I can't take a look at it as of this writing. Out of curiosity, I signed up to Vimeo and upload a test video there and set it in the following privacy level:

Setting the video to private:

Setting the video Embed to "nowhere":

I can still embed the video in Vimeo block and its been able to pull the title correctly. I think we can ask for more testing on different contributors to confirm.

[joedolson]

I tried every variation on permissions with Vimeo that I could come up with, and all versions of embedding that video exposed the title of the video in the iframe. That even includes the password protected video; which doesn't expose the video's name visibly, but still includes it in the iframe.

Given that we can't reproduce this issue, and the original sample is no longer using this method of embedding, I'm not sure it's reasonable to hold it open.

If you can provide a reliable way to reproduce this, @jaimewhi, we can always reopen and explore further. Right now, it seems that this is working as it's expected to.