Error: The operation could not be completed because the selected object is not a transform node. – Accessibility Gap in Viewport 2.0

Direct answer

Broaden Viewport 2.0 selection validation so it accepts any DAG node, then resolves the selection to the transform parent or appropriate tool context before executing transform-oriented logic. Commands that genuinely require a transform node, such as parenting, constraints, or transform manipulation, should still reject non-transform inputs after that resolution step. Expose Accessibility options in a dedicated Preferences tab or section, and allow navigation shortcut remapping there with a default-restore option. These changes are version-dependent: Maya releases before 2024.2 may not include a standalone Accessibility tab, so the exact UI path must be confirmed for the installed version.

Likely explanation versus confirmed facts

Likely explanation: Viewport 2.0 selection validation checks for a transform node before running transform-oriented tools. Selecting a camera, shape, or light fails that check and surfaces the reported error.

Confirmed facts: Maya Preferences are organized by category tabs and store UI, display, and keyboard settings. Preference layout and accessibility APIs differ between releases. No live source or patch has been verified for this specific error.

Steps for this case

1. Update the selection validator to accept any DAG node instead of requiring a transform node up front.
2. Inside the tool handler, resolve the selected node to its transform parent when one exists; otherwise use the node's native context.
3. Keep transform-only operations restricted to transform nodes after resolution, so parenting and constraint workflows are unchanged.
4. Add an Accessibility tab or section to Preferences that groups high-contrast UI, screen-reader options, and navigation shortcuts.
5. Enable shortcut remapping inside Accessibility settings, with conflict checking against existing hotkeys and a default-restore button.

Missing diagnostic detail

Confirm the installed Maya version. Accessibility tab availability changes before and after 2024.2, and this determines whether you add a new tab or extend an existing section.

Verification

• Reproduce the error with a camera selected, then confirm the same operation succeeds with a transform selected.
• Open Preferences in the target Maya version and check whether an Accessibility tab exists or where high-contrast and keyboard settings currently live.
• Test modified selection validation on transform, shape, camera, and light selections to ensure existing transform workflows remain intact.
• Assign an alternative navigation shortcut and verify viewport camera movement responds to the new input.

Assumptions and uncertainty

This draft assumes standard Maya DAG behavior and Preferences organization. The 2024.2 Accessibility tab boundary is unverified and should be treated as a version assumption requiring review. Broadening validation too far can break operations that genuinely require transform nodes.