I would like to clarify that this feature request does not appear to address the issue that led us here.

The issue is not that focus moves directly to the first segment when the user presses Tab. The issue is that there is currently no supported public notification when keyboard focus enters the RadSegmentedControl.

Consider the following scenario:

1. The first segment is already the CurrentItem.
2. The first segment is already the SelectedItem.
3. The user presses Tab and keyboard focus enters the control.

In this case, focus has clearly moved from outside the control to inside the control, but:

• CurrentItem does not change.
• SelectedItem does not change.
• No CurrentItem notification occurs.
• No SelectionChanged event occurs.
• Focused, Unfocused, or IsFocused notifications are not raised at the RadSegmentedControl level.

The missing capability is a supported mechanism for consumers to detect that keyboard focus entered the control.

Even if the control itself receives focus before the individual segments, applications still need a public notification such as:

• Focused / Unfocused
• IsFocused property change notifications
• A dedicated focus-enter event
• Another supported control-level focus notification API

This has uses beyond accessibility, including keyboard interaction workflows, visual state management, validation, focus tracking, and general application logic.

If this feature request is intended only to change the tab-navigation behavior so the entire control receives focus before the first segment, then the original problem remains unresolved. A separate feature request would still be needed to expose a supported control-level focus notification when keyboard focus enters RadSegmentedControl.