Re: new version of 2.2.7 - interruptions - based on comments from Andrew and Jake.

A definition for Interruptions is critical. I did comment that it shouldn’t be “unnecessary interruptions” because it can be handled with the exception to evaluate whether it is essential or not, but we still need to be clear about what constitutes an interruption. My comment #2 about change of content stands.

As it is right now, this will prohibit use of features that would be regarded as interruptions but might be very useful to people such a chat support area for a site that appears when a user is struggling to find something and a live agent can offer suggestions. Some people will desperately need that type of support, some people will find it distracting – is it practical to ask each site to have user preferences for users to visit and disable these, even if the user isn’t logged in? Is it practical to ask each user to seek out a settings area for every site they visit on the off chance that the site will have such interrupting elements?

Without a definition, I am certain that web site owners will take considerable latitude in their definition of what is essential to “usage or meaning of the content”. Certainly an assistance window with chat support would be regarded by an ecommerce store as essential to usage.

Also, in the note it uses “changes of context” but that isn’t part of the SC.


Andrew Kirkpatrick
Group Product Manager, Accessibility

From: "" <>
Date: Tuesday, December 19, 2017 at 07:45
To: WCAG <>
Cc: Jason J White <>, Michael Gower <>, Abma <>, Andrew Kirkpatrick <>
Subject: new version of 2.2.7 - interruptions - based on comments from Andrew and Jake.

Hi Folks
I put two versions up at<> so we can compare them side by side.  The second version incorporates Jakes direction and Andrews comments however I think it also addresses the reasons for the new version (Jason and Mikes comments as well as the online issues) and Andrews comments

Are there still outstanding issues?

All the best

Lisa Seeman

LinkedIn<>, Twitter<>

Received on Tuesday, 19 December 2017 14:46:05 UTC