| Name | Verifies UX Compliance during Consent Flow |
| Category | INFOSEC |
| Execution Method | Manual (CX) |
Description | In this particular test careful attention is paid to the consent workflow and the graphical attributes required to meet the CX guidelines released by the DSB. | | Preconditions | |
| Steps | - Access the Data Holder Consumer Dashboard and verify the dashboard landing page:
- Input User Identifier and verify
- WCAG compliant including vision impaired (i.e., “screen reader”) functionality
- The Data Recipient name is specified
- Input OTP received and verify:
- WCAG compliant including vision impaired (i.e., “screen reader”) functionality
- Select Accounts to enable sharing on verifying:
- Unavailable accounts outline reasons for not being available
- WCAG compliant including vision impaired (i.e., “screen reader”) functionality
- The Data Recipient name is specified again
- Verify summary of consent meets the following requirements:
- Scopes are described using the agreed Data Cluster wording
- Consent verification is a single page scrollable outline. Where possible verify that Data Clusters have expanders to improve overall readability.
- WCAG compliant including vision impaired (i.e., “screen reader”) functionality
- Displays a list of accounts which are being shared
- Does not add additional friction to the authorisation flow
- Displays a set of Data Clusters related to the request scopes
- Use of merged language is in use for presentation of combined detailed and basic scopes
- Display the duration of sharing and it’s start and finish time
- Display instructions with relation to how authorisation can be withdrawn and a specific statement that it can be withdrawn at any time. Preferably use the term “Stop Sharing” for this purpose.
- Complete consent flow
- Initiate a consent flow from the Data Recipient requesting all scopes with a zero value sharing duration (once-off)
- Input User Identifier and verify:
- WCAG compliant including vision impaired (i.e., “screen reader”) functionality
- The Data Recipient name is specified
- Input OTP received and verify:
- WCAG compliant including vision impaired (i.e., “screen reader”) functionality
- Select Accounts to enable sharing on verifying
- Unavailable accounts outline reasons for not being available
- WCAG compliant including vision impaired (i.e., “screen reader”) functionality
- The Data Recipient name is specified again
- Verify summary of consent meets the following requirements:
- Scopes are described using the agreed Data Cluster wording
- Consent verification is a single page scrollable outline. Where possible verify that Data Clusters have expanders to improve overall readability.
- WCAG compliant including vision impaired (i.e., “screen reader”) functionality
- Displays a list of accounts which are being shared
- Does not add additional friction to the authorisation flow
- Displays a set of Data Clusters related to the request scopes
- Use of merged language is in use for presentation of combined detailed and basic scopes
- Display “Your Data will be shared once” instead of a specific time value
- Display instructions with relation to how authorisation can be withdrawn and a specific statement that it can be withdrawn at any time. Preferably use the term “Stop Sharing” for this purpose.
|
| Inputs | - A client registration for the Software Product
|
| Expected Results | - Data Holder meets the CX guidelines
- Data Holder meets the accessibility guidelines
|