!--a11y-->
Context
Programming 
In the previous section, the different context structures have been defined and partly connected to each other using context mapping. In addition, individual UI element properties have been bound to corresponding value attributes, which are defined in the controller contexts of the views.
This declarative part of the development process is followed by the initialization of the individual context structures and the customizing of the context contents for the different state changes that occur at runtime.
The section Context Programming is divided into three separate chapters:
...
1. Reading of question-answer texts and their storage in the quiz controller context: Contrary to the value attributes that- by default - are contained in the context at runtime, the individual node elements must be instantiated by the source code and be bound to the corresponding value node. The question-answer texts used in the quiz application are read from resource bundles.
2. Initializing top level value attributes: The previously defined top level value attributes are initialized in this section.
3. Context state changes and actions: After initializing the context structures, they have the initial state. If events occur at the application runtime that should cause state changes within the context structures, these events must be described in the corresponding event handlers.
UI elements bound to actions should be activated or deactivated without using data binding. In the quiz application, the event onAction of the button ShowAnswerButton is bound to the action ShowAnswerPressed. The activation or deactivation of the corresponding action objects in the view controller automatically changes the state of the button ShowAnswerButton on the user interface (activated, deactivated).
Start initializing the different context
structures within the Quiz component. In the first step, the quiz
texts are read from the resource bundles and are stored in the component
context.
