In content implemented using markup languages, status messages can be programmatically determined through role or properties such that they can be presented to the user by assistive technologies without receiving focus.
Ensure status messages are available to assistive technologies without receiving focus.
Informs users of important changes without interrupting their workflow.
Not understanding what are status messages. According to WCAG definitions, status messages are a change of content that is not a change of context, and that provides information to the user on the success or results of an action, on the waiting state of an application on the progress of a process, or on the existence of errors.
Using role="alert" or aria-live "assertive" on content which is not important and time-sensitive.
Providing status messages that are not read to screen readers.
Test with a screen reader to determine if status messages are delivered to the user.
You can use aria-live with the pop-up style status messages to communicate the messages to assistive technologies. Avoid using "assertive" value unless the message is crucial.