E-mail List Archives

Search E-mail List Archives for

Number of posts in this thread: 8 (In chronological order)

From: Brian Lovely
Date: Thu, Dec 12 2019 10:13AM
Subject: Duration of Success message
No previous message | Next message →

I have a flow where a user performs a task, the view changes to a success
message, then the browser is redirected to the home page. I'm trying to
find if WCAG 2.1 addresses a minimum duration for that success message.

Does anyone know if this kind of thing is addressed in WCAG 2.1?

--
*Brian Lovely*
Capital One Digital Accessibility
804.389.1064




The information contained in this e-mail is confidential and/or proprietary to Capital One and/or its affiliates and may only be used solely in performance of work or services for Capital One. The information transmitted herewith is intended only for use by the individual or entity to which it is addressed. If the reader of this message is not the intended recipient, you are hereby notified that any review, retransmission, dissemination, distribution, copying or other use of, or taking of any action in reliance upon this information is strictly prohibited. If you have received this communication in error, please contact the sender and delete the material from your computer.

From: Sandy Feldman
Date: Thu, Dec 12 2019 10:25AM
Subject: Re: Duration of Success message
← Previous message | Next message →

Brian,

Would it be ok to have a "dismiss" link? A "yeah, that's great, let's go
home" instead of an automatic redirect?

--
Sandy
sandyfeldman.com


On 2019-12-12 12:13 p.m., Brian Lovely via WebAIM-Forum wrote:
> I have a flow where a user performs a task, the view changes to a success
> message, then the browser is redirected to the home page. I'm trying to
> find if WCAG 2.1 addresses a minimum duration for that success message.
>
> Does anyone know if this kind of thing is addressed in WCAG 2.1?
>

From: Sandy Feldman
Date: Thu, Dec 12 2019 10:27AM
Subject: Re: Duration of Success message
← Previous message | Next message →

https://www.w3.org/WAI/WCAG21/quickref/?showtechniques=413#status-messages

does this help?

Sandy

On 2019-12-12 12:13 p.m., Brian Lovely via WebAIM-Forum wrote:
> I have a flow where a user performs a task, the view changes to a success
> message, then the browser is redirected to the home page. I'm trying to
> find if WCAG 2.1 addresses a minimum duration for that success message.
>
> Does anyone know if this kind of thing is addressed in WCAG 2.1?
>

From: Steve Green
Date: Thu, Dec 12 2019 11:05AM
Subject: Re: Duration of Success message
← Previous message | Next message →

I would say this is a clear failure of SC2.2 (enough time)

https://www.w3.org/WAI/WCAG21/quickref/?showtechniques=221#enough-time

I don't know how the redirection is implemented in your case, but three likely methods (meta redirect, meta refresh and server-side techniques) are explicitly described in failures F40, F411 and F58.

https://www.w3.org/WAI/WCAG21/Techniques/failures/F40.html
https://www.w3.org/WAI/WCAG21/Techniques/failures/F41.html
https://www.w3.org/WAI/WCAG21/Techniques/failures/F58.html

Steve Green
Managing Director
Test Partners Ltd

From: Brian Lovely
Date: Thu, Dec 12 2019 11:12AM
Subject: Re: [External Sender] Duration of Success message
← Previous message | Next message →

Yeah, I was originally think of this in terms of providing sufficient time
to read and process, but I think it best that they provide the user with a
button to acknowledge the success message and then direct the browser to
the homepage. ...the upshot being that once the user is successful there's
nothing more to be done in this area.

On Thu, Dec 12, 2019 at 1:05 PM Steve Green < = EMAIL ADDRESS REMOVED = >
wrote:

> I would say this is a clear failure of SC2.2 (enough time)
>
>
> https://urldefense.com/v3/__https://www.w3.org/WAI/WCAG21/quickref/?showtechniques=221*enough-time__;Iw!!EFVe01R3CjU!LvID26p2zQblRju82i1Z_ZBW5ewiYeXYYPZly5iHJv5BDJc8qtHX7k9ZLPb5QkOg5hUtLQ$
>
> I don't know how the redirection is implemented in your case, but three
> likely methods (meta redirect, meta refresh and server-side techniques) are
> explicitly described in failures F40, F411 and F58.
>
>
> https://urldefense.com/v3/__https://www.w3.org/WAI/WCAG21/Techniques/failures/F40.html__;!!EFVe01R3CjU!LvID26p2zQblRju82i1Z_ZBW5ewiYeXYYPZly5iHJv5BDJc8qtHX7k9ZLPb5QkNpPcoT7g$
>
> https://urldefense.com/v3/__https://www.w3.org/WAI/WCAG21/Techniques/failures/F41.html__;!!EFVe01R3CjU!LvID26p2zQblRju82i1Z_ZBW5ewiYeXYYPZly5iHJv5BDJc8qtHX7k9ZLPb5QkO2bkwC9Q$
>
> https://urldefense.com/v3/__https://www.w3.org/WAI/WCAG21/Techniques/failures/F58.html__;!!EFVe01R3CjU!LvID26p2zQblRju82i1Z_ZBW5ewiYeXYYPZly5iHJv5BDJc8qtHX7k9ZLPb5QkMpDqLejQ$
>
> Steve Green
> Managing Director
> Test Partners Ltd
>
>
>

From: Mark Magennis
Date: Fri, Dec 13 2019 2:52AM
Subject: Re: [EXTERNAL] Duration of Success message
← Previous message | Next message →

From: WebAIM-Forum < = EMAIL ADDRESS REMOVED = > On Behalf Of Steve Green

> I would say this is a clear failure of SC2.2 (enough time)

Note that 2.2 isn't an SC. It's a section of SC's. So it can't be passed or failed.

One of the SC's in that section is SC 2.2.1 Timing Adjustable and I wonder whether it fails that. It says "For each time limit that is set by the content". Is this a time limit that is set by the content? There are exceptions for real-time events and essential time limits but I doubt that either of them apply here.

If this SC is failed, then remediating it requires you to either allow the user to turn off or adjust the time limit before encountering it, or issue a warning that it is about to expire and give the user the option of extending it. I can't imagine either of these solutions being acceptable in the situation described.

One to think more about.

Mark

Mark Magennis
Skillsoft | mobile: +353 87 60 60 162
Accessibility Specialist

From: Brian Lovely
Date: Fri, Dec 13 2019 6:58AM
Subject: Re: [External Sender][EXTERNAL]Duration of Success message
← Previous message | Next message →

As I understand it, when a user gets to the point where this redirect
occurs, there isn't anything else they can do in the section/session, which
is why it is currently auto-redirecting. I'm just wanting the success
message to remain long enough for a user to perceive and process that they
successfully completed their task. Waiting to redirect until the user
activates a button or link seems to be a reasonable solution.




The information contained in this e-mail is confidential and/or proprietary to Capital One and/or its affiliates and may only be used solely in performance of work or services for Capital One. The information transmitted herewith is intended only for use by the individual or entity to which it is addressed. If the reader of this message is not the intended recipient, you are hereby notified that any review, retransmission, dissemination, distribution, copying or other use of, or taking of any action in reliance upon this information is strictly prohibited. If you have received this communication in error, please contact the sender and delete the material from your computer.

From: Patrick H. Lauke
Date: Fri, Dec 13 2019 9:29AM
Subject: Re: [EXTERNAL]Duration of Success message
← Previous message | No next message

On 13/12/2019 09:52, Mark Magennis wrote:

> One of the SC's in that section is SC 2.2.1 Timing Adjustable and I wonder whether it fails that. It says "For each time limit that is set by the content". Is this a time limit that is set by the content? There are exceptions for real-time events and essential time limits but I doubt that either of them apply here.

Possibly of interest: wider question about notifications/toasts and
2.2.1 https://github.com/w3c/wcag/issues/976

> If this SC is failed, then remediating it requires you to either allow the user to turn off or adjust the time limit before encountering it, or issue a warning that it is about to expire and give the user the option of extending it. I can't imagine either of these solutions being acceptable in the situation described.

Alternatively, in this situation - though it would be quite a change -
the notification could happen *after* the reload/redirect, when the
homepage is displayed.

Or - simply not having the automatic redirect, but making the
notification show something the success message and a "Back to homepage"
link that they have to actively follow.

P
--
Patrick H. Lauke

www.splintered.co.uk | https://github.com/patrickhlauke
http://flickr.com/photos/redux/ | http://redux.deviantart.com
twitter: @patrick_h_lauke | skype: patrick_h_lauke