Ensure an element's role supports its ARIA attributes (.ytmVideoInfoVideoTitle): A11y_ code.visualstudio.com_Name Role Value

[kupatkar99]

GitHub Tags:

#A11yTCS; #A11yMAS; #A11ySev2; #DesktopWeb; #ChromiumEdge; #Win11; #Visual Studio Code Services; #E2E_Visual Studio Code Services_Web_Jan26; #WCAG4.1.2; #Name Role Value; #WCP; #P1_WCP; #aria-allowed-attr; #a11ydb-aria-attr-restricted

Repro Steps:

Launch the URL: https://code.visualstudio.com/blogs/2024/12/18/free-github-copilot>Observe the issue.

Issue:

Ensure an element's role supports its ARIA attributes (aria-allowed-attr - https://accessibilityinsights.io/info-examples/web/aria-allowed-attr)

Target application:

Announcing a free GitHub Copilot for VS Code - https://code.visualstudio.com/blogs/2024/12/18/free-github-copilot

Element path:

iframe;.ytmVideoInfoVideoTitle

Snippet:

MongoDB for VS Code - MongoDB Developer Tools

How to fix:

Fix all of the following:
ARIA attribute is not allowed: aria-level="2"

Environment: Microsoft Edge version 151.0.0.0

====

This accessibility issue was found using Accessibility Insights for Web 2.46.0 (axe-core 4.10.2), a tool that helps find and fix accessibility issues. Get more information & download this tool at http://aka.ms/AccessibilityInsights.

Environment Details:

Application Name: code.visualstudio.com
URL: https://code.visualstudio.com/blogs/2024/12/18/free-github-copilot
Chromium Edge: Version 151.0.4129.72 (Official build) (64-bit)
OS: Windows 11 Enterprise Insider Preview 24H2

Attachment:

[Shivang9983]

Hi! kupatkar99
I'd like to investigate this accessibility issue.

I’ll first verify whether the aria-level="2" violation is still reproducible and whether .ytmVideoInfoVideoTitle is coming from the embedded YouTube iframe or from the VS Code page itself.

If the element is inside the third-party YouTube iframe, I’ll confirm whether there is an actionable fix on the VS Code side rather than making a change that cannot affect the iframe DOM.

If there is a fix we can make on the VS Code side, I’d be happy to work on it and open a PR.

[ntrogh]

kupatkar99 I can't reproduce this error with Accessibility Insights. Could you reverify if you're still getting this issue?

[Shivang9983]

Nick Trogh (@ntrogh)
I'd like to investigate this accessibility issue.