[timings and interruptions subgroup] midpoint check-in

Hi, all

As the weekly AG meeting isn’t happening this week, the Timings And Interruptions subgroup is sending its midpoint check-in via email.

We have we worked through the user needs, possible tests, and possible assertions, which are listed in the following table. Please note that these are high-level and are to generate feedback from the group—please let us know if you think we've missed anything.

Definition of an assertion: An assertion is a declaration that a process was followed instead of a result was tested.
User Need
Tests
Users can know that content has changed or updated, regardless of update speed (i.e. when timing is too fast,  the user knows that the content has changed. (State change indication (update speed)) (time blindness?)(coga/visual perception)
Possible structured test
When content changes or updates…

  1.  Decide on importance for the user
  2.  Decide on the urgency for the user
  3.  Note the detail and timing of the communication to the user (if any)
  4.  Cross-check that result meets with the expectation
…or something.
Possible Assertion
User Testing and AT testing / heuristic evals?
Users can control how and when they are notified about updates.
Possible structured test
Inspect interface to determine if there is any way for the user to control notifications through settings or additional features.

Or

Are roles used and used correctly? (aka users can adjust controls using AT to adjust)?

Possible Assertion
User Testing and AT testing/ heuristic evals?

  *   Assertions would handle granularity, flexibility and verbosity

Example from Google Docs (Go to tools, turn on “screen reader support”, Go to Accessibility menu, and select “Show Live Edits”
Users can have adequate time to complete task before timeout (coga/motor)
(This includes reading and understanding content)
Possible structured guided test
For the task at hand:

  *   Is there anything that works as a timeout?
  *   If there is a timeout, is it for a security risk or inherently part of the experience (timeout on auction or game)?
  *   Is the timeout configurable?
     *   How discoverable?
     *   How configurable?
  *   If there is a timeout, is the user notified before they start?
  *   Is data retained after timeout?
  *   How to decide on "adequate"?
  *   Alternative mechanism available that has no timeout?

Possible Assertion
User is able to complete task before interrupted by a timeout.
Users can reduce distractions while in a task view (i.e. pop up blocking. Interfering animations) (coga/visual perception)

  *   Users are made aware of emergencies and other urgent/important information
Possible structured test

  *   Identify if there are distractions.
  *   Then locate settings or test if user agents are able to turn them off, change the presentation, and / or adjust the timing.

Open question:  Should W3C provide guidance on what is deemed critical and/or an emergency?

Possible Assertion
User is able to complete a task with a level of distractions that meets their needs.
Users are not deceived regarding urgency or need to respond, or forced calls to action
Possible structured test

  *   A user is not presented timing information during a task that is untrue, invalid, or inaccurate.

Possible Assertion

  *   Usability testing shows that users correctly understand the urgency (or lack thereof) in a task.

Open question:  Should W3C provide guidance on what is deemed critical and/or an emergency?
Users can save state of a form or input process/view
Possible structured test

  *   User is able to save the state of a form or input task.
  *   User is able to load the saved state of a process without loss of information or progress.

Possible Assertion
None
Ability to save interruptions to review at a future time.
Possible structured test

  *   A mechanism exists to allow a user to preserve and review prior interruptions and notifications

Possible Assertion
Users can interact with a site interface without stress or pressure to perform (excluding specific performative testing)(coga)(time blindness?) unless required or essential
Possible structured test

  *   Known methods of applying stress or pressure are utilized by the site
  *   The interface requires stress and pressure, or stress and pressure are essential

Possible Assertion

  *   User testing demonstrated that users were able to interact without stress or pressure, unless required or essential
Users can interact with content without being overwhelmed or getting lost in unrelated content
Possible structured test
None

Possible Assertion

  *   User testing demonstrated that users were able to interact without being overwhelmed, or getting lost in unrelated content
Customization features are discoverable and accessible
Possible structured test

  *   Customization features exist and are accessible

Possible Assertion
Usability testing shows that users are able to discover the customization features.

For the remaining four weeks, we will continue to work on goal of writing an exploratory version of the guideline and outcomes for timing and interruptions guideline.

Thanks

Francis