How can I display an inline notification that users can dismiss by keyboard?

Make the × a real, focusable button with an accessible name such as “Dismiss notification.” Don’t make users guess what the symbol means. Keep the button in the keyboard sequence, and make its focus visible; Microsoft’s Windows-app guidance recommends keyboard-reachable controls, predictable order, and a visible focus indicator for focusable custom controls [S3].

Also check what happens after the button is activated. Removing the notice removes the focused control too, so decide deliberately where focus should go rather than assuming the browser or framework will choose a useful place. The right choice depends on how the notice appeared and what remains on the page.

First distinguish an inline notice that appears as part of the page from a popup that temporarily overlays or interrupts it. The Microsoft guidance is specifically for WinUI Popup controls, not a universal rule for web notices. For that WinUI control, Microsoft describes moving focus into a popup when it opens and returning focus to the prior element when it closes; it also describes Escape dismissal when light-dismiss behavior is enabled [S1].

For your own inline notice, choose behavior based on whether users need to act on it immediately. Avoid moving focus unexpectedly just because a message appeared. Escape can be an additional dismissal option if that suits the interaction, but don’t make it the only option: keep the named button available. Treat these as design choices to test for your platform, not as web requirements established by the WinUI guidance.

There may be no opener to return to. Before removing the notice, identify a useful destination that remains in the interface—for example, the control the user was working with, if it still exists. If dismissal is the only action in the notice, moving focus to an arbitrary location can disorient people; test whether the chosen destination makes the next step clear. Microsoft recommends returning focus to the element that opened a WinUI popup, but its guidance does not define the destination for a general inline notice with no opener [S1].

A simple review scenario: a page displays a notice above a form while focus is in the form. The user presses Tab until “Dismiss notification” receives visible focus, activates it, and continues at the form control that still makes sense. This is an example to evaluate, not a guaranteed behavior or a universal focus rule.

Use this checklist while reviewing the actual interface:

1. Give the dismissal control a clear accessible name; don’t rely on an × alone. Microsoft also calls for accessible names on interactive elements in its WinUI popup guidance [S1].
2. Verify keyboard users can reach the control in a predictable order and can see which control has focus [S3].
3. Test activation with the keys appropriate to your platform and control. For WinUI, a focused Button is activated with Enter; Space also invokes its action outside text-entry mode [S2]. Don’t assume that WinUI description defines every web implementation.
4. After dismissal, verify focus remains on a useful surviving element. If a control opened a WinUI Popup, Microsoft’s documented pattern returns focus to that opener [S1].
5. If offering Escape, test it as an extra dismissal route and confirm users can still find the visible button; the cited Escape behavior is for the documented WinUI popup scenario [S1].

Record the notice type, its opener (if any), the dismissal control’s name, the expected focus destination, and the keys tested. The cited material does not establish a universal web standard for inline-notice announcement, focus placement, or dismissal behavior, so verify your implementation in its intended environment.