Re: A question about immediate feedback

Toast notifications are not a contravention of 2.2.1 Timing Adjustable
where they are for notification only and require no action.

The key point of 2.2.1 is to allow users sufficient time to perform actions
and input material. As the material below the SC bullets says:

"This success criterion helps ensure that users can complete tasks without
unexpected changes in content or context that are a result of a time limit."

<dialog> modals, shown using showModal(), are relatively easy to style and
have wide cross browser support for retaining the tab focus in the modal
and allow Escape to close the modal.

My feeling here is that a toast notification is the preferred UX and
accessible option. Don't overcomplicate it.

On Thu, Jun 26, 2025 at 5:06 PM Brooks Newton <brooksallennewton@gmail.com>
wrote:

> Hi Mark,
>
> I documented toasts and similar design patterns that automatically
> disappear as a WCAG violations almost seven years ago to the day.
>
> Alert Dialog Example: Is disappearing toaster alert WCAG compliant? #756
> <https://github.com/w3c/aria-practices/issues/756>
> The more you know!
>
> Brooks
>
> On Thu, Jun 26, 2025 at 3:43 AM Mark Magennis <Mark.Magennis@skillsoft.com>
> wrote:
>
>> Adam Cooper said:  "It should be onscreen for as long as you believe it
>> is necessary for everybody to consume its content and then disappear."
>>
>>
>>
>> Adam, I would have thought that automatically disappearing toast
>> notifications are a violation of 2.2.1 Timing Adjustable. Unless they
>> disappear when they are no longer valid or one of the other mechanisms
>> (turn off, adjust, extend) are implemented.
>>
>> Interested to hear your view on this.
>>
>> Mark
>>
>