On November 6, Microsoft added an option to the Windows 11 Insider preview builds that lets users skip future confirmation prompts for Sticky Keys and Filter Keys. It also covers the Sticky Keys prompt that appears when you press the Shift key five times. Sticky Keys is an accessibility feature that lets you press keys one after another instead of holding down a modifier such as Ctrl while pressing another key. To understand this change, it helps to distinguish between turning the assistive feature itself on or off and invoking it through a keyboard shortcut.
Confirmation dialogs can now be skipped in the future
With this change, users can choose from the Sticky Keys or Filter Keys confirmation dialog to stop the same prompt from appearing again. Microsoft's Beta release notes explain that users can set it directly from the dialog so that they are not asked in the future. What is new is that, instead of dealing with the prompt every time it appears, users can choose from the dialog itself to suppress it.
The change appears in the notes for both Windows 11 Insider Preview Beta Build 26320.9876, dated November 6, and Experimental Build 26340.9882. In the Experimental channel it is listed as one of the changes being rolled out gradually, so it may not reach every user right away, even on the same build. The wording "don't ask again" is a translation of Microsoft's English description; Microsoft has not published an official Japanese label or the layout of the on-screen dialog. What has been added is a setting available from the confirmation dialog, not a change to the assistive features themselves.
The difference between the Sticky Keys feature and its shortcut
Sticky Keys lets you enter, in sequence, key combinations that would normally be pressed at the same time. For example, you can perform a copy by pressing and releasing Ctrl and then pressing C, which has the same effect as Ctrl+C. According to Microsoft's API documentation on Sticky Keys, pressing a modifier key such as Shift, Ctrl, or Alt once keeps it in effect until the next non-modifier key is pressed or the mouse is clicked. Pressing the same modifier key twice locks it until it is pressed again.
Pressing Shift five times, on the other hand, is a shortcut for invoking the Sticky Keys feature. Whether the feature itself is enabled and whether it can be invoked via the shortcut are controlled separately. Based on Microsoft's API documentation and its guidelines for game developers, the main controls related to Sticky Keys can be summarized as follows.
| Control target | Example API definition | Role |
|---|---|---|
| Sticky Keys feature itself | SKF_STICKYKEYSON |
Controls whether Sticky Keys is enabled |
| Invocation shortcut | SKF_HOTKEYACTIVE |
Controls whether invoking the feature via the shortcut is enabled or disabled |
| Confirmation dialog display | SKF_CONFIRMHOTKEY |
A flag that controls the confirmation prompt; however, the documentation's description applies to Windows 95/98 and Windows 2000 |
As shown, the Windows API treats the behavior of the Sticky Keys feature and its invocation via shortcut as separate matters. Note, however, that Microsoft's documentation for SKF_CONFIRMHOTKEY, which controls the confirmation prompt, targets older versions of Windows. Microsoft has not disclosed which flag or setting the newly added option changes internally, so this table cannot be used to identify how the new confirmation dialog is implemented. In addition, the definitions listed here relate to Sticky Keys and do not necessarily apply as-is to Filter Keys.
Game developers are still responsible for restoring settings
The Sticky Keys shortcut can be triggered unintentionally during gameplay. Microsoft's documentation for game developers explains that in games that use the Shift key, the shortcut can activate and show the default confirmation dialog, which can minimize a full-screen game. However, this is not the result of measurements showing the same problem occurs in all current games.
The document also points out that accessibility features such as Sticky Keys are essential for some users and that the features themselves do not interfere with full-screen games. For that reason, it asks game developers not to change users' accessibility settings needlessly. Even when a game disables the shortcut, it recommends doing so only when the relevant assistive feature is turned off, and restoring the original settings when the game switches to windowed mode or exits.
Restoring settings matters because changes made through the API persist after the application closes. If a game exits with the shortcut still disabled, the unintended change to the user's settings may continue afterward. The option added to the confirmation dialog is for users to skip future prompts themselves, and its purpose differs from that of restoring settings a game has temporarily changed. The improved dialog therefore does not remove the need for game developers to manage settings properly.
Microsoft has not said when it will bring this change to the general release of Windows 11. Features introduced in Insider builds may have their specifications changed before public release, or may not ship at all. Going forward, the key questions are whether this option will be introduced to general users, and whether games and other applications can reliably restore any settings they change while preserving the accessibility features users need.