Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DSB Item - CX Guidelines #195

Open
CDR-CX-Stream opened this issue Nov 12, 2024 · 0 comments
Open

DSB Item - CX Guidelines #195

CDR-CX-Stream opened this issue Nov 12, 2024 · 0 comments
Assignees
Labels
maturity: ready for work Indicates the problem statement is well defined and work on a proposal can begin sector: all The item is cross-sector in nature and impacts the CDR regime more broadly

Comments

@CDR-CX-Stream
Copy link
Member

CDR-CX-Stream commented Nov 12, 2024

As per rule 4.10(1)(a)(ii), 4.20D(a)(ii), and 4.22(b), ADRs, CDR Representatives, and DHs must have regard to the DSB's Consumer Experience Guidelines when developing consent model designs.

The CX Guidelines demonstrate optional examples for how to implement key CDR requirements, including rules, standards, and privacy safeguards. These typically take the form of annotated wireframes and prototypes, but also include:

  • a CX Checklist, which provides a a complete list of items referenced in the CX Guidelines, to assist participants with implementation and compliance discovery
  • open source assets, which include version-controlled Figma files, complete with annotations, working prototypes, and focus order notes to assist with WCAG Success Criterion, along with a proof of concept coded prototype using a Single Page Application with React JS
  • CX metrics to aid participants with the measurement of consent quality, comprehension, and characteristics
  • other research related information to share insights relating to participant demographics and CDR behavioural archetypes

This quarter, the DSB will be progressing CX guidelines related to:

CX Guidelines are typically driven by rules and standards developments, but also based on community requests via the CDR zendesk or as a standards-maintenance change request.

@CDR-CX-Stream CDR-CX-Stream converted this from a draft issue Nov 12, 2024
@CDR-CX-Stream CDR-CX-Stream self-assigned this Nov 12, 2024
@CDR-CX-Stream CDR-CX-Stream added maturity: ready for work Indicates the problem statement is well defined and work on a proposal can begin sector: all The item is cross-sector in nature and impacts the CDR regime more broadly labels Nov 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
maturity: ready for work Indicates the problem statement is well defined and work on a proposal can begin sector: all The item is cross-sector in nature and impacts the CDR regime more broadly
Projects
Status: Oct-Dec 2024
Development

No branches or pull requests

1 participant