Synonyms: Updates, change of context

See also: Animations, time limits, navigation sequence, modal dialog

Changes of context are:

  • Changing to another program,
  • Changing of the view port (e.g. switching to another application window),
  • Changes to the keyboard focus,
  • Changing the content that changes the meaning of the page.

Changes of context expected and required during operation include:

  • Enabling a link: Opening a new screen,
  • Enabling a Help link: Open Help, possibly in another application (e.g. in a browser or PDF reader),
  • Enabling an internal page link: Scrolling to the linked location and changing the keyboard focus,
  • Enabling a Submit button: Opening a new screen,
  • Enabling a Delete button: Removing the element to be deleted, possibly changing the keyboard focus if necessary (as the delete button has been disabled or removed),
  • Enabling the Logout button: Logout from the application,
  • Enabling a Menu button: Opening the menu and focusing of the first menu item,
  • Enabling a button to open a modal dialog: Opening the dialog and focusing of the first element in the dialog,
  • Page scrolling: change of the visible area,
  • Navigation with the keyboard (e.g. with the tab key): Change of the keyboard focus, possible change of the visible area (if the focused element is not situated in the visible area),
  • Navigating through a radio button group in which there are associated form fields behind each radio button which can only be operated depending on the radio button: The form elements are enabled when the radio button is selected, the other form elements are disabled.
  • Navigation through a group of tab panels: The corresponding tab is shown (alternatively, only after the enabling of the tab panel).

Examples of unexpected changes of context which must be avoided or announced:

  • Enabling of a check box within a form: Showing additional form fields that are visually located in the navigation sequence before the check box,
  • Text input in an input field: Deleting of entries already made in other fields because the entries in this field and the other fields are mutually exclusive,
  • Text input in an input field: After reaching the maximum number of characters, the focus is placed in the following input field,

Examples of unexpected changes of context which have to be avoided or announced:

  • Enabling a link: Opening a new screen in another application,
  • Enabling of a tab panel: The displayed tab or an element in it receives the focus.

Examples of unexpected changes of context which must be avoided:

  • Navigation through a group of radio buttons: Opening a new screen,
  • Navigation through a table: Opening a modal dialog,
  • Fully filled out form: Submitting the form,
  • Focusing of a Submit button: Submitting the form,
  • Focusing of the Delete button: Removing the element to be deleted.
No.PropertyDescriptionClassificationReference
75Use of the keyboard, use of pointing deviceDuring the focusing of an element, no change of context may occur.MustEN 301 549:
9.3.2.1, 11.3.2.1
76Use of the keyboard, use of pointing deviceWhen a form element changes its value, no unexpected change of context may occur.

Note 1: Unexpected changes of context are changes of context that do not conform to the default behavior of the element and have not been previously announced.

Note 2: If unexpected changes of context prevent the use of the keyboard (e.g. due to a loss of focus during use), these are not permitted, even if they are announced in advance.

MustEN 301 549:
9.3.2.2, 11.3.2.2
77Use of the keyboard, use of pointing deviceChanges of context should only occur if the users have initiated them. Alternatively, the user should be able to disable the changes of context.ShouldWCAG 2.1: 3.2.5 (AAA)
78UpdatesIt must be possible to disable or adjust automatic changes of context that do not take place after 20 hours (seee time limits and animations).MustEN 301 549:
9.2.2.1, 11.2.2.1, 9.2.2.2, 11.2.2.2
79UpdatesIt should be possible to avoid or disable automatic changes of context.

Note: This does not apply to emergency messages.

ShouldWCAG 2.1:
2.2.3 (AAA),
2.2.4 (AAA)
No.PropertyDescriptionClassificationReference
80UpdateStatus messages must be marked so that they are output by the assistive technology without receiving the focus.MustEN 301 549:
9.4.1.3, 11.4.1.3.1

Information about this article

You are welcome to send feedback by email about our handout!