implementation
Implement in your agent
# Implement Inline alert in your agent ## Objective Implement Inline alert for this verified behavior: A persistent message placed next to the content or task it explains, with urgency chosen from the actual update. ## Prerequisites - Inspect the repository, design system, and existing tests first. - Preserve unrelated changes and keep the file scope bounded. - Confirm that Inline alert matches the need before writing code. ## Required behavior - The message remains in context until the condition changes or the user deliberately dismisses it. - A live region announces new status only when the update is important and not already focused. ## States to cover - Upload ready — Upload ready - Upload size error — Upload size error ## Accessibility - The primary control or named region for Inline alert has a stable accessible name from visible text or an explicit programmatic label; placeholder text and tooltips are not names. - The message does not steal focus on routine updates; failed submission may focus a summary or first invalid control deliberately. - It remains until the condition resolves; a close control exists only when hiding the message cannot conceal an unresolved risk. - Tab reaches recovery actions in document order - Enter activates the named recovery action ## Non-goals - A short low-risk confirmation needs no persistence - The condition applies to the entire page or site ## Acceptance criteria - The message sits beside the affected task - Text states the problem and a recovery path - Urgency determines the live role - The message persists while the condition remains
sha256:001b9ce2f83ea6db73ac899163d10ae755aac0a1c7f45db68e12e9d6167cd720