E-mail List Archives
Re: UI toasts, notifications and conforming to time limits (2.2.1)
From: glen walker
Date: Jul 11, 2018 1:07PM
- Next message: glen walker: "Re: 360 degree panoramic images"
- Previous message: Swift, Daniel P.: "360 degree panoramic images"
- Next message in Thread: Tim Harshbarger: "Re: [EXTERNAL] UI toasts, notifications and conforming to time limits (2.2.1)"
- Previous message in Thread: Jonathan Avila: "Re: UI toasts, notifications and conforming to time limits (2.2.1)"
- View all messages in this Thread
Matt, we also discussed this same timing question on slack recently (July
4th).
https://web-a11y.slack.com/archives/C042TSFGN/p1530688615000057
Eric posted the question and then I replied and then there were a couple
follow-ups. My personal opinion was that a toast message does not violate
2.2.1, provided the toast is being used for its intended purpose, but that
preference settings were a good idea (as Jonathan mentioned here). I also
mentioned having an "earcon" option for the toast.
The key phrase in the "Understanding" section (
https://www.w3.org/TR/UNDERSTANDING-WCAG20/time-limits-required-behaviors.html)
was:
"If Web functions are time-dependent, it will be difficult for some users
> to perform the required action before a time limit occurs."
>
There shouldn't be any "required actions" in the toast message. It's just
an informal, "by the way" type message, that if ignored, does not hurt
anything.
- Next message: glen walker: "Re: 360 degree panoramic images"
- Previous message: Swift, Daniel P.: "360 degree panoramic images"
- Next message in Thread: Tim Harshbarger: "Re: [EXTERNAL] UI toasts, notifications and conforming to time limits (2.2.1)"
- Previous message in Thread: Jonathan Avila: "Re: UI toasts, notifications and conforming to time limits (2.2.1)"
- View all messages in this Thread