I want to suggest a better behavior for this control that would help it stay 508 compliant. When I use the RadTabControl in my applications, and a user attempts to change the tab using just the keyboard, this control behaves in a way that is not typical. For starters, the RadTabItem’s default IsTabStop value is “false”. Second, even when we set the IsTabStop to “true”, the focus is automatically changed from the Tabs to the first control in the tab being activated. This is not a typical behavior as seen in the stock TabControl that Microsoft wrote (or any other Tab control to speak of). Finally there is the matter of the AutomationPeer (as in there is none for either the RadTabControl or RadTabItem). This presents an issue for customers like me who are required to make our products accessible.
- Rashad Rivera