fixing path for annex-5

Author: paolo-de-rosa

docs/annexes/annex-5/annex-5.01-design-guide.md

@@ -136,14 +136,14 @@ appropriate feedback within a reasonable amount of time.
 When adding  or removing a document the application should let the user know
 whether the process was completed successfully of not.
 
-![Document Management example showing success and failure states](../../media/5.01/Figure_1_Document_Management_example.png)
+![Document Management example showing success and failure states](media/5.01/Figure_1_Document_Management_example.png)
 _Figure 1: Document Management example_
 
 ###### Interactive elements
 
 Interactive elements such as buttons must have a pressed and focused state.
 
-![Interactive Elements example showing button states](../../media/5.01/Figure_2_Interactive_Elements_example.png)
+![Interactive Elements example showing button states](media/5.01/Figure_2_Interactive_Elements_example.png)
 _Figure 2: Interactive Elements example_
 
 ---
@@ -163,23 +163,23 @@ conventions, making information appear in a natural and logical order.
 Documents should be (where possible) represented in the UI by what is familiar
 to the user instead of generic / ambiguous icons.
 
-![Document Presentation Example showing realistic document representations](../../media/5.01/Figure_3_Document_Presentation_Example.png)
+![Document Presentation Example showing realistic document representations](media/5.01/Figure_3_Document_Presentation_Example.png)
 _Figure 3: Document Presentation Example_
 
 ##### Labels
 
 Stay away from technical terms and jargon. Use labels that people use in their
 everyday life.
 
-![Labels example showing user-friendly terminology](../../media/5.01/Figure_4_Labels_example.png)
+![Labels example showing user-friendly terminology](media/5.01/Figure_4_Labels_example.png)
 _Figure 4: Labels example_
 
 ##### Icons
 
 People spend most of their time in other apps/websites. Use icons that are
 familiar and clear to them instead on ambiguous ones.
 
-![Icons Example showing clear vs ambiguous icons](../../media/5.01/Figure_5_Icons_Example.png)
+![Icons Example showing clear vs ambiguous icons](media/5.01/Figure_5_Icons_Example.png)
 _Figure 5: Icons Example_
 
 ---
@@ -201,7 +201,7 @@ perform actions
 
 - for instance, the freedom to undo or redo any accidental moves
 
-![Undo and Redo Example showing action reversibility](../../media/5.01/Figure_6_Undo_and_Redo_Example.png)
+![Undo and Redo Example showing action reversibility](media/5.01/Figure_6_Undo_and_Redo_Example.png)
 _Figure 6: Undo and Redo Example_
 
 ---
@@ -236,7 +236,7 @@ they commit to the action.
 
 For accidental actions such as miss-clicks
 
-![Confirmation Dialogue Example showing user verification before action](../../media/5.01/Figure_7_Confirmation_Dialogs_Example.png)
+![Confirmation Dialogue Example showing user verification before action](media/5.01/Figure_7_Confirmation_Dialogs_Example.png)
 _Figure 7: Confirmation Dialogues Example_
 
 ##### Flexible inputs
@@ -248,7 +248,7 @@ number can be entered in various ways by different people. The field can either
 format it accordingly on each own or provide a hint of the expected format
 instead of producing in-line errors or result in guesswork.
 
-![Flexible Inputs Example showing different input format acceptance](../../media/5.01/Figure_8_Flexible_Inputs_Example.png)
+![Flexible Inputs Example showing different input format acceptance](media/5.01/Figure_8_Flexible_Inputs_Example.png)
 _Figure 8: Flexible Inputs Example_
 
 ---
@@ -303,7 +303,7 @@ indicate the problem, and constructively suggest a solution.
 
 #### 2.9.1 Indicative examples
 
-![Error Messages Examples showing clear problem indications and solutions](../../media/5.01/Figure_9_Error_Messages_Examples.png)
+![Error Messages Examples showing clear problem indications and solutions](media/5.01/Figure_9_Error_Messages_Examples.png)
 _Figure 9: Error Messages Examples_
 
 ---
@@ -353,7 +353,7 @@ screen when they are easily reachable with the thumb when operating the phone
 with one hand. The top half should be used for displaying information,
 documents, QR codes etc.
 
-![Layout diagram showing thumb reachable areas on mobile screen](../../media/5.01/Figure_10_Layout.png)
+![Layout diagram showing thumb reachable areas on mobile screen](media/5.01/Figure_10_Layout.png)
 _Figure 10: Layout_
 
 ---
@@ -371,7 +371,7 @@ a disability or a combination of disabilities that affect their motor movements
 and dexterity, as well as by the act of using a website while on the move, such
 as while walking or commuting.
 
-![Target Sizes diagram showing recommended touch target dimensions](../../media/5.01/Figure_11_Target_Sizes.png)
+![Target Sizes diagram showing recommended touch target dimensions](media/5.01/Figure_11_Target_Sizes.png)
 _Figure 11 : Target Sizes_
 
 ---
@@ -434,11 +434,11 @@ past or future tenses, use simple verb forms. This may not be applicable to all
 languages; the overall goal is to be as concise as possible without compromising
 clarity.
 
-![Example showing "Document added" text](../../media/5.01/Document_added.png)
+![Example showing "Document added" text](media/5.01/Document_added.png)
 
 Write in the present tense.
 
-![Example showing "Document has been added" text](../../media/5.01/Document_has_been_added.png)
+![Example showing "Document has been added" text](media/5.01/Document_has_been_added.png)
 
 Don't write in different variations of the present tense, such as the present
 perfect tense.
@@ -454,7 +454,7 @@ sentence with the goal.
 To add a document, click +
 ```
 
-![Example showing "To add a document, click +" text](../../media/5.01/To_add_a_document.png)
+![Example showing "To add a document, click +" text](media/5.01/To_add_a_document.png)
 
 Start a statement with the objective ("to add a document") and end it with the
 user action ("click + ").
@@ -463,7 +463,7 @@ user action ("click + ").
 Click + to add a document
 ```
 
-![Example showing "Click + to add a document" text](../../media/5.01/Click_to_add_a_document.png)
+![Example showing "Click + to add a document" text](media/5.01/Click_to_add_a_document.png)
 
 Don't state the action the user takes ("Click + ") before the objective ("to add
 a document").
@@ -479,7 +479,7 @@ the same phrase.
 Change your preferences in My Account
 ```
 
-![Example showing "Change your preferences in My Account" text](../../media/5.01/Change_your_preferences_in_My_Account.png)
+![Example showing "Change your preferences in My Account" text](media/5.01/Change_your_preferences_in_My_Account.png)
 
 Don't refer to the user in both the second person and the first person within
 the same phrase.
@@ -488,7 +488,7 @@ the same phrase.
 Change your preferences in Account
 ```
 
-![Example showing "Change your preferences in Account" text](../../media/5.01/Change_your_preferences_in_Account.png)
+![Example showing "Change your preferences in Account" text](media/5.01/Change_your_preferences_in_Account.png)
 
 ---
 

docs/annexes/annex-5/annex-5.02-design-guide-data-sharing-scenarios.md

@@ -36,15 +36,15 @@ on a mobile device, requesting access to a Relying Party's service (i.e. app
 or browser) and authorizes by using the EUDI Wallet app, which is also installed
 on the same device.
 
-![Login interface showing EUDI Wallet login button on mobile device](../../media/5.02/Login_with_EUDI_wallet.png)
+![Login interface showing EUDI Wallet login button on mobile device](media/5.02/Login_with_EUDI_wallet.png)
 
 In contrast, in the 'remote cross-device' flow, the EUDI Wallet user consumes
 information from a Relying Party service on another device than the EUDI Wallet
 device, e.g. user visits the relying party's service on their web browser on a
 PC and uses the EUDI Wallet app to scan a QR Code on a login page in order to
 get access to a service provided by the Relying Party.
 
-![Login screen with EUDI Wallet login option on desktop browser](../../media/5.02/Login_with_EUDI_wallet2.png)
+![Login screen with EUDI Wallet login option on desktop browser](media/5.02/Login_with_EUDI_wallet2.png)
 
 In relation to the 'proximity' flows, both flows are related to scenarios where
 the EUDI Wallet User is physically close to a Relying Party, the user does not
@@ -56,7 +56,7 @@ human acting as a Relying Party (who may operate a device of their own). In the
 unsupervised flow, the EUDI Wallet presents verifiable attributes to a machine
 without human supervision.
 
-![Share information screen showing QR and NFC sharing options](../../media/5.02/Share_information.png)
+![Share information screen showing QR and NFC sharing options](media/5.02/Share_information.png)
 
 ---
 
@@ -86,7 +86,7 @@ analysed in this Design Guide. These are:
 - Password
 - OTP
 
-![Multiple authentication method screens showing PIN, pattern, biometrics, password and OTP options](../../media/5.02/Identification_methods.png)
+![Multiple authentication method screens showing PIN, pattern, biometrics, password and OTP options](media/5.02/Identification_methods.png)
 
 It shall be clarified that different levels of security shall be required per
 use case, e.g. sharing a user's 'Person Identification Data' is associated with
@@ -119,7 +119,7 @@ The criteria used for the rating are:
 authentication process
 - **Accessibility**: Adherence to accessibility standards/specificities
 
-![Radar chart comparing different authentication methods across multiple criteria](../../media/5.02/Authentication_means.png)
+![Radar chart comparing different authentication methods across multiple criteria](media/5.02/Authentication_means.png)
 
 > **_NOTE:_** _Ratings have been based on a desk study and not actual first-hand
 testing._
@@ -241,7 +241,7 @@ party and how you become one.
 The EUDI Wallet aims to promote user confidence and foster a sense of control
 and privacy, thereby enhancing the overall adoption and utility of the app.
 
-![Data sharing screens showing mandatory and optional information requests from Relying Party](../../media/5.02/RP_requests_info.png)
+![Data sharing screens showing mandatory and optional information requests from Relying Party](media/5.02/RP_requests_info.png)
 
 ---
 
@@ -315,7 +315,7 @@ Handling/Display of error messages in different scenarios.
   When the user attempts to log in to the app, expects to receive feedback
   indicating the success or failure of their login attempt.
 
-  ![Login error screen showing incorrect password message](../../media/5.02/Erroneous_user_credentials.png)
+  ![Login error screen showing incorrect password message](media/5.02/Erroneous_user_credentials.png)
   _The user gets an error message indicating that his credentials were wrong:_
 
 - **5.2 Multiple failed attempts to login or present information**
@@ -332,7 +332,7 @@ Handling/Display of error messages in different scenarios.
   factors attempting to gain unauthorized access by repeatedly guessing passwords
   or usernames.
 
-  ![Login screen showing too many attempts error with timer](../../media/5.02/Erroneous_user_credentials2.png)
+  ![Login screen showing too many attempts error with timer](media/5.02/Erroneous_user_credentials2.png)
 
   _The user gets an error message indicating that they must try again later:_
 
@@ -343,7 +343,7 @@ Handling/Display of error messages in different scenarios.
   screen, indicating that the document could not be verified because it is
   expired or revoked.
 
-  ![Error message showing additional documents required](../../media/5.02/Error.png)
+  ![Error message showing additional documents required](media/5.02/Error.png)
 
   _The user gets a message indicating the status of the document:_
 
@@ -354,7 +354,7 @@ Handling/Display of error messages in different scenarios.
   how to renew or update the document, directing the user to the appropriate
   authorities, or providing relevant instructions.
 
-  ![Warning notification about document expiration with renewal option](../../media/5.02/Warning.png)
+  ![Warning notification about document expiration with renewal option](media/5.02/Warning.png)
 
   _The user gets a message indicating that the document expires shortly:_
 
@@ -370,7 +370,7 @@ not be verified (Maybe address safety)**
   -a physical person or a digital service- and it turns out that the third party
   is not valid or is a fraud, they must get an alert warning message.
 
-  ![Alert warning about untrusted relying party with security options](../../media/5.02/Alert.png)
+  ![Alert warning about untrusted relying party with security options](media/5.02/Alert.png)
 
   _The user gets a message indicating that they must not share information with
   that party. The options are to report it, to close the app, or to search for
@@ -383,7 +383,7 @@ not be verified (Maybe address safety)**
   document is not present in the user's app, an error message is displayed,
   notifying the user that the document is not stored in their app.
 
-  ![Error message showing missing ID card document with add document option](../../media/5.02/Error2.png)
+  ![Error message showing missing ID card document with add document option](media/5.02/Error2.png)
 
   _The error message then suggests adding the document from the available
   documents list._