Scope notification.acceptPrimaryAction keybinding to screen reader users

[Copilot]

Description

cmd+shift+A was claimed by both notification.acceptPrimaryAction and agents.openVSCodeWindow, causing accidental (and dangerous) acceptance of notification primary actions.

This scopes notification.acceptPrimaryAction to screen reader users — its original audience — freeing the binding for agents.openVSCodeWindow everyone else.

• notificationsCommands.ts: gate the keybinding behind CONTEXT_ACCESSIBILITY_MODE_ENABLED, AND-combined with the existing focus/toast-visibility conditions:

when: ContextKeyExpr.and(
    CONTEXT_ACCESSIBILITY_MODE_ENABLED,
    ContextKeyExpr.or(NotificationFocusedContext, NotificationsToastsVisibleContext)
),

The command remains available via the Command Palette for all users; only the keybinding is now conditional on accessibility mode.

[Copilot]

Pull request overview

This PR resolves a keybinding conflict by restricting notification.acceptPrimaryAction (Cmd/Ctrl+Shift+A) to screen reader optimized mode (accessibilityModeEnabled), freeing the shortcut for agents.openVSCodeWindow for non-screen-reader users.

Changes:

• Gate notification.acceptPrimaryAction keybinding behind CONTEXT_ACCESSIBILITY_MODE_ENABLED while preserving existing notification focus/toast visibility conditions.
• Add the required accessibility context key import in the notifications commands registration file.

Show a summary per file

File	Description
src/vs/workbench/browser/parts/notifications/notificationsCommands.ts	Scopes the notification.acceptPrimaryAction keybinding to accessibilityModeEnabled to avoid Cmd/Ctrl+Shift+A collisions for most users.

Copilot's findings

• Files reviewed: 1/1 changed files
• Comments generated: 1