Replies: 1 comment 4 replies
-
We deployed a change that have fixed this issue for you. Could you try again? |
Beta Was this translation helpful? Give feedback.
4 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Apologies if this is a weird question but we've been having issues with an accessibility scanning tool we use to audit our page which is reporting multiple WCAG2.1 failures related to multiple page header
<title>
elements in a single page with invalid characters in them, specifically, the tool is registering multiple empty<title></title>
tags as the output of the scan.After looking into this, we noticed that the only common thing with all pages that report this issue is that they all play embedded Vimeo videos. We noticed by looking through the source that these embeds also include some type of debugger tool that is running and manipulating various svg
<title>
elements that eventually are completely removed from the DOM. We think that the scan tool is incorrectly registering multiple svg title tags in their initial empty loaded state as page header elements. Does this make sense? I have no idea what else could be causing this. 😩😪Beta Was this translation helpful? Give feedback.
All reactions