Accessibility: VoiceOver announces aria-keyshortcuts Meta/Alt instead of Command/Option on macOS

[Petr Duda (petdud)]

I reported this upstream in Chromium:

https://issues.chromium.org/issues/556516042

On macOS, when web content uses valid WAI-ARIA keyboard shortcuts such as:

<button aria-keyshortcuts="Meta+Shift+M">Test</button>
<button aria-keyshortcuts="Alt+Shift+M">Test 2</button>

VoiceOver announces:

• Meta Shift M
• Alt Shift M

instead of the platform-appropriate Apple terminology:

• Command Shift M
• Option Shift M

The application markup is correct. WAI-ARIA uses platform-neutral modifier names such as Meta and Alt, so authors should not replace these with Command or Option in aria-keyshortcuts.

The platform-specific translation should happen when the shortcut is exposed through the macOS accessibility API.

WebKit has identified the equivalent issue and is implementing a fix here:

• WebKit bug: https://bugs.webkit.org/show_bug.cgi?id=323089
• WebKit PR: VoiceOver announces aria-keyshortcuts Meta/Alt literally instead of Command/Option on macOS WebKit/WebKit#73012

The Chromium issue is here:

• Chromium: https://issues.chromium.org/issues/556516042

Since WebView2 is Chromium-based, I am posting this here so the WebView2 team can help clarify:

1. Whether WebView2 on macOS is affected by the same Chromium accessibility behavior.
2. Whether the upstream Chromium fix will automatically flow into WebView2.
3. Which WebView2 Runtime/version is expected to contain the fix once it lands upstream.
4. Whether Microsoft applications using WebView2 on macOS need any additional integration work.

This affects VoiceOver users because Apple keyboards use the terms Command and Option, not Meta and Alt.

If useful, I can also provide a minimal reproduction page for testing with VoiceOver.