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

what is we say " non essential interruptions"we can then combine the defintions




A mechanism is available to postpone or suppress non-essential interruptions unless are part of the workflow or are initiated by the user or involve an emergency.


Note: Error, success, and warning messages; timeout notifications; changes of context that are part of the workflow sequence;  suggestions about the users intent such as  as autofill and auto-correct; and live updates when the purpose of the content is monitoring are considered essential.


 interruptions:  Secondary information, pop-ups, overlays or changes of context that are not part of the workflow sequence or for fulfilling the key purpose of the content.

All the best

Lisa Seeman

LinkedIn, Twitter





---- On Tue, 19 Dec 2017 17:46:28 +0200 Andrew Kirkpatrick<akirkpat@adobe.com> wrote ---- 

      Yes, WCAG 2.0 does use “interruptions” but that is a AAA item, so didn’t have the same expectations with regard to testability as an A or AA SC does.
 [Jason] Actually, it does have the same expectations regarding testability. (This requirement of reliable verification applies to all success criteria, irrespective of level.) However, Andrew can still argue that the existing requirement inherited from 2.0 isn’t as reliably testable as it ought to be, due to lack of clarity in what constitutes an “interruption”. Of course, any definition that we now provide could also affect the interpretation of 2.2.4.
  
 Jason, you’re right, I misspoke, but I do believe that 2.2.4 didn’t receive the same level of scrutiny and as a result 2.2.4 isn’t as testable as it should be.
 AWK
 
 

Received on Tuesday, 19 December 2017 16:01:47 UTC