Begin of the insertion**As a** screen reader user and/or keyboard-only userEnd of the insertion Begin of the deletion **As** a \[enter role of user\]End of the deletion
**I want to** Begin of the insertionperceive and operate flash messages (including reading, navigating, and dismissing them)End of the insertion Begin of the deletion \[enter objective\]End of the deletion
**so that** Begin of the insertionimportant feedback is accessible and I’m not blocked or confused while completing my task.End of the insertion Begin of the deletion \[enter desired result\]End of the deletion

**Acceptance criteria**

Begin of the insertion**1\. Screen reader announcement of dynamic messages:**

**WCAG 4.1.3 — Status Messages**

End of the insertion * Begin of the insertionFlash messages that appear dynamically are announced automatically by assistive technologies.

* Non-critical messages use a polite announcement pattern.

* Error or urgent messages use an assertive announcement pattern.End of the insertion Begin of the deletion <br>End of the deletion


Begin of the insertion**2\. Keyboard accessibility for controls inside messages**End of the insertion Begin of the deletion **Technical notes**End of the deletion

Begin of the insertion**WCAG 2.1.1 — Keyboard**
**WCAG 2.1.2 — No Keyboard Trap**
**WCAG 2.4.3 — Focus Order**

End of the insertion * Begin of the insertionAny interactive element inside a flash message (close button, action link, etc.) is reachable by keyboard.

* Controls can be activated using standard keyboard interaction.

* Focus order remains logical.

* Dismissing the message does not trap or unexpectedly move focus.End of the insertion Begin of the deletion <br>End of the deletion


Begin of the insertion**3\. Focus behavior must not disrupt the user**End of the insertion Begin of the deletion **Permissions and visibility considerations**End of the deletion

Begin of the insertion**WCAG 3.2.1 — On Focus**
**WCAG 2.4.3 — Focus Order**

End of the insertion * Begin of the insertionFlash messages do not automatically steal focus unless required for a blocking error.End of the insertion Begin of the deletion _To whom is this feature visible?_End of the deletion

* Begin of the insertionClosing a flash message returns focus to a sensible location.


**4\. Timing and auto-dismiss accessibility**

**WCAG 2.2.1 — Timing Adjustable**

* If flash messages auto-dismiss:

* Users have enough time to read them.

* Dismiss timers pause while focused or interacted with.

* Critical informationEnd of the insertion Begin of the deletion _WhenEnd of the deletion is Begin of the deletion itEnd of the deletion not Begin of the insertionremoved before it can be perceived.End of the insertion Begin of the deletion visible?_End of the deletion


Begin of the insertion**5\. Minimum contrast for message text and controls**End of the insertion Begin of the deletion **Translation considerations**End of the deletion

Begin of the insertion**WCAG 1.4.3 — Contrast (Minimum)**

End of the insertion * Begin of the insertionText inside flash messages meets minimum contrast requirements.

* Icons conveying meaning also meet contrast requirements where applicable.


**6\. Accessible names for controls**

**WCAG 4.1.2 — Name, Role, Value**

* Close buttonsEnd of the insertion Begin of the deletion _Key termsEnd of the deletion and Begin of the insertionaction controls have clear, accessible names.End of the insertion Begin of the deletion phrases in the key languages_&nbsp;End of the deletion


Begin of the insertion**Technical notes**End of the insertion Begin of the deletion **Out of scope**End of the deletion

* Begin of the insertionImplement live regions:

* polite announcements for informational/success messages

* assertive announcements for errors

* Ensure:

* no `display:none` or `aria-hidden` on active message containers

* interactive elements are real buttons/linksEnd of the insertion Begin of the deletion <br>End of the deletion