E-mail List Archives
Thread: WCAG 2.2.2 and repetition over time.
Number of posts in this thread: 4 (In chronological order)
From: Kia
Date: Thu, May 01 2025 2:53AM
Subject: WCAG 2.2.2 and repetition over time.
No previous message | Next message →
Hi all,
I'm working with an app that uses a blinking dot to indicate a new notification. The blinking is intended to draw attention, and it lasts for 4 seconds, then stops. After a pause of 30 seconds, it blinks again for another 4 seconds — and this cycle repeats.
My questions are:
Would such a pattern (blinking <5s, repeating every 30s) be considered compliant with WCAG 2.2.2? What if the pause was longer?
If it's technically compliant, could it still be considered a bad practice from an accessibility perspective?
Are there any known best practices or real-world examples for handling this kind of intermittent attention-drawing animation?
Kind regards,
Kia
__________
Kia Neumann
Tilgængelighedskonsulent, Sensus ApS.
Specialister i tilgængelighed
Tel +45 48 22 10 03
Mobil +45 61 78 32 30
Mail: = EMAIL ADDRESS REMOVED = – Web: https://www.sensus.dk
From: Steve Green
Date: Thu, May 01 2025 3:18AM
Subject: Re: WCAG 2.2.2 and repetition over time.
← Previous message | Next message →
In my view, this is non-conformant and increasing the pause wouldn't help.
Steve Green
Managing Director
Test Partners Ltd
From: Mark Magennis
Date: Thu, May 01 2025 3:30AM
Subject: Re: WCAG 2.2.2 and repetition over time.
← Previous message | Next message →
I guess it depends on how you interpret the word "lasts" in the sentence "For any moving, blinking or scrolling information that (1) starts automatically, (2) lasts more than five seconds, and (3) is presented in parallel with other content...". If it happens again, does this mean it's "lasting" since it happened before.
Aside from arguments in WCAG court, your question of whether this can be considered bad practice depends on how you judge the importance of this frequent reminder against the fact that it will be sufficiently distracting to make it difficult for some users to concentrate on reading or interacting with other content.
Speaking personally, I find animation, blinking content, reminder pop-ups etc. horribly distracting and I don't have any diagnosed attention deficit or other disorder, so I can only imaging how bad it might be for some other users. So to support this approach I think you would need a very strong argument for how important it is to repeatedly remind users.
Mark
From: WebAIM-Forum < = EMAIL ADDRESS REMOVED = > on behalf of Kia via WebAIM-Forum < = EMAIL ADDRESS REMOVED = >
Sent: Thursday 1 May 2025 09:53
To: = EMAIL ADDRESS REMOVED = < = EMAIL ADDRESS REMOVED = >
Cc: Kia < = EMAIL ADDRESS REMOVED = >
Subject: [EXTERNAL] [WebAIM] WCAG 2.2.2 and repetition over time.
Hi all,
I'm working with an app that uses a blinking dot to indicate a new notification. The blinking is intended to draw attention, and it lasts for 4 seconds, then stops. After a pause of 30 seconds, it blinks again for another 4 seconds — and this cycle repeats.
My questions are:
Would such a pattern (blinking <5s, repeating every 30s) be considered compliant with WCAG 2.2.2? What if the pause was longer?
If it's technically compliant, could it still be considered a bad practice from an accessibility perspective?
Are there any known best practices or real-world examples for handling this kind of intermittent attention-drawing animation?
Kind regards,
Kia
__________
Kia Neumann
Tilgængelighedskonsulent, Sensus ApS.
Specialister i tilgængelighed
Tel +45 48 22 10 03
Mobil +45 61 78 32 30
Mail: = EMAIL ADDRESS REMOVED = – Web: https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.sensus.dk%2F&data=05%7C02%7Cmark.magennis%40skillsoft.com%7C77b7c8f4863149a6ae1a08dd888da7b3%7C50361608aa23494da2332fd14d6a03f4%7C0%7C0%7C638816864171055320%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=BOSBL95tfMSpsT6kRMSj2HIgRkxL6PlbxGq4ubwbNnU%3D&reserved=0<https://www.sensus.dk/>
From: EMB Creative
Date: Thu, May 01 2025 5:05AM
Subject: Re: WCAG 2.2.2 and repetition over time.
← Previous message | No next message
You would still need information for blind users, look into aria-live to
communicate an update in content.
I was under the impression it's best to have an option to turn off
animations altogether.
Seems like the standard is a static symbol.
Cheers,
Emily
* Emily Burns*
UX | UI Design & Development
On Thu, May 1, 2025, 4:53 AM Kia via WebAIM-Forum <
= EMAIL ADDRESS REMOVED = > wrote:
> Hi all,
>
> I'm working with an app that uses a blinking dot to indicate a new
> notification. The blinking is intended to draw attention, and it lasts for
> 4 seconds, then stops. After a pause of 30 seconds, it blinks again for
> another 4 seconds — and this cycle repeats.
>
> My questions are:
> Would such a pattern (blinking <5s, repeating every 30s) be considered
> compliant with WCAG 2.2.2? What if the pause was longer?
> If it's technically compliant, could it still be considered a bad practice
> from an accessibility perspective?
> Are there any known best practices or real-world examples for handling
> this kind of intermittent attention-drawing animation?
>
>
>
>
> Kind regards,
>
> Kia
>
>
>
> __________
>
> Kia Neumann
>
> Tilgængelighedskonsulent, Sensus ApS.
>
> Specialister i tilgængelighed
>
> Tel +45 48 22 10 03
>
> Mobil +45 61 78 32 30
>
> Mail: = EMAIL ADDRESS REMOVED = – Web: https://www.sensus.dk
>
>
>
>
>
>
>