E-mail List Archives
Thread: Query on Auto Page redirect issue
Number of posts in this thread: 3 (In chronological order)
From: Ramakrishnan Subramanian
Date: Thu, May 26 2022 6:57AM
Subject: Query on Auto Page redirect issue
No previous message | Next message →
Dear members,
I would need your guidance on the following scenario whether it would
fail WCAG requirement? If so, what would be the recommendation?
We have a success screen that is displayed after the user completes
filling of a form with first 3 steps successfully. It is redirected to
the home page automatically after 10 seconds.
The content in that page is
1. Header (with the Logo skip to main content link and the navigation
menus) repeated in all the pages on the website.
2. Main content (with the heading followed by the success message with
couple of lines of text. And a go to home page link). Note: Even if
the user does not activate this link, he/she would be redirected to
the same home page after 10 sec.
3. Footer (with a bunch of links) again repeated in all the pages on
the website.
It appears that this content may fail under 2.2.2 timing adjustable.
But since there is not much content here and user input is not
expected can it be exempted If we provide the success message in aria
alert role and set the visual focus immediately on the main heading
after the page load.
or,
If the user is provided enough time to read this content and
understand, can this be exempted? If so, how much time would be
sufficient?
Apart from "timing adjustable" which SC does this possibly fail?
--
Thanks and Regards
Ramakrishnan
From: Patrick H. Lauke
Date: Thu, May 26 2022 7:28AM
Subject: Re: Query on Auto Page redirect issue
← Previous message | Next message →
On 26/05/2022 13:57, Ramakrishnan Subramanian wrote:
> It appears that this content may fail under 2.2.2 timing adjustable.
> But since there is not much content here and user input is not
> expected can it be exempted If we provide the success message in aria
> alert role and set the visual focus immediately on the main heading
> after the page load.
> or,
> If the user is provided enough time to read this content and
> understand, can this be exempted? If so, how much time would be
> sufficient?
2.2.1 Timing Adjustable doesn't really offer an exemption/escape clause
for "there's only a little bit of content", so this will fail even if
you believe the timeout/redirect time is sufficient for a user to read
the page before it happens, I'm afraid.
P
--
Patrick H. Lauke
https://www.splintered.co.uk/ | https://github.com/patrickhlauke
https://flickr.com/photos/redux/ | https://www.deviantart.com/redux
twitter: @patrick_h_lauke | skype: patrick_h_lauke
From: glen walker
Date: Thu, May 26 2022 8:29AM
Subject: Re: Query on Auto Page redirect issue
← Previous message | No next message
If you literally want the exemption and to answer "how much time would be
sufficient?", then the last bullet point in the criterion says 20 hours.
I've never seen a page with a 20 hour limit but you asked what would be
required.
Your scenario almost sounds like a "toast message", which, in and of
themselves, have lots of UX/accessibility issues. But you also have a
redirect after the toast message which makes it fall under the 2.2.1
guideline.
To satisfy 2.2.1, you can implement the third bullet point to warn the user
before the redirect happens. One possibility might be when your success
page comes up, you have a timer on the page that says the user will be
redirected after XX seconds. That's the "warning". (The timer would have
to be conveyed to the screen reader user via aria-live). The XX seconds
would have to be at least 20 seconds as per the criterion's third bullet
point rather than the 10 seconds in your original question.
You could have a button that says "redirect now" (or something worded a bit
better) so that they don't have to wait the full 20 seconds and another
button for "pause redirect", which lets the user stop the redirect until
they're done reading, at which point they could click on the "redirect now"
button.
Doing so puts the redirection timing solely in the user's hands, which is
what you want. If they don't select either of the buttons, the page will
redirect automatically in 20 seconds.
(Note that "redirect" is kind of a technical term so you probably don't
want that as the label of the aforementioned buttons. Since the
redirection goes to the home page, one of the buttons could be "Go to
homepage now", which is the "redirect now" mentioned earlier. The other
button could be "Pause the timer" (if the timer is obvious on the page on
what it'll do when the timer reaches 0). Definitely consult with your
designer or content specialist.)