VSCodium Accessibility Help Dialog ↔ Screen Reader Focus Management: Is the dialog announced as a modal?

The Accessibility Help dialog in VSCodium is intended to provide a modal overlay listing keyboard shortcuts. However, the DOM hierarchy often omits a role="dialog" attribute on the root element, causing screen readers to treat it as a generic container. Additionally, aria-modal="true" is frequently absent, allowing navigation to the underlying editor while the dialog remains open. Focus management also appears inconsistent; the editor sometimes retains focus rather than shifting to the dialog’s first interactive control.

These inconsistencies persist across multiple VSCodium builds derived from the same VS Code codebase, and the behavior varies between screen readers such as NVDA, JAWS, and VoiceOver. The goal is to determine whether the dialog is properly announced as a modal and whether focus is trapped within it.

Specific questions:

• Does the Accessibility Help dialog root element carry a role="dialog" attribute in the current VSCodium release?
• Is aria-modal="true" set on the dialog container?
• When the dialog is open, does keyboard focus remain trapped inside the dialog until it is dismissed?