Split button isn't getting activated with caps+enter.

[YuliKl]

Describe the bug

Steps to reproduce the bug

Steps to reproduce the behavior:

1. Launch XAML Controls Gallery.
2. Activate Split button from All controls page.
3. Navigate to "Font color" split button present in the page and press caps+enter to activate it.

Expected behavior

The primary activation command with the narrator to activate a button is caps+enter. Hence a split button should get activated with caps+enter.

Actual behavior

The split button isn't getting activated with caps+enter.

Screenshots

Observation: Toggle split button gets activated with caps+enter successfully.

User Impact: Visually impaired users will be affected as a basic command to activate split button isn't working

Version Info

Gallery version (found on Settings page):

App Version: 1.2.9.0

Windows 10 version:

• Insider Build (xxxxx)
• May 2019 Update (18362)
• October 2018 Update (17763)
• April 2018 Update (17134)
• Fall Creators Update (16299)
• Creators Update (15063)
• Anniversary Update (14393)

Device form factor:

• Desktop
• Mobile
• Xbox
• Surface Hub
• IoT

Additional context

Copied from internal bug

[marcelwgn]

Using narrator, hitting caps+enter does trigger the click method of the button.

However there seems to be now way to open the flyout of a (Toggle)SplitButton using keyboard shortcuts (at least not without adding one). Thanks to @jevansaks for the clarification.
I think this is a spec-issue as there also is an issue over at WinUI regarding the buttons behaviour with touch.

Update: There is an issue over at WinUI addressing the tabbing behavior of the SplitButton.

[marcelwgn]

Upon further investigation, I noticed that the SplitButton does trigger the correct events, the "Clicked" effect is just not visually present.

I noticed that the SplitButton is not really intuitive to use (user has to select text before pressing the button makes a difference).
@YuliKl Should we modify the example to be a bit more intuitive to use?

[YuliKl]

While I'm definitely open to ideas about how to change this sample, this may just be a bug that we need to resolve as "Won't Fix".

[YuliKl]

Closing as I don't think we have any ideas for how to correct this problem.