Keyboard‑only operation limits in Blender’s keymap and operator system

Goal: Determine whether Blender’s documented keymap and operator system enables complete keyboard‑only interaction across all interface elements in a given release.

Constraints: The manual does not provide a definitive enumeration of keyboard‑accessible versus mouse‑only controls; context‑sensitive regions, color pickers, drag‑to‑adjust fields, and 3D view navigation rely on modal operators that may not expose standard keyboard shortcuts. Additionally, Blender’s custom UI toolkit limits native assistive‑technology integration, making screen‑reader verification version‑dependent.

Questions: Which specific UI components lack a documented keyboard shortcut in Blender 4.0? How can users verify keyboard accessibility for a given operator without relying on mouse‑only workflows? Is there a stable reference in the manual that lists all mouse‑only gaps for assistive‑technology planning?