CX Guidelines

Read first CX Checklist attributes ◦ Area refers to the stage in the consumer journey, such as Pre-consent, Consent, Authenticate, Authorise, or Consent Management. ◦ Focus area refers to a specific theme in each stage (e.g. 01. User Identifier). ◦ Checklist ref contains a unique reference number for the item. ▪ The first values refer to the Area (e.g. 0DL.xx.xx for data language; 2AU.xx.xx for authentication). ▪ The second set values refer to the Focus area (e.g. xxx.01.xx). ▪ The last values refer to the annotation number used on the wireframe, where available (e.g. xxx.xx.02; wireframes are linked to in the Example column). ◦ Type refers to the source of the statement: Rules, Standards and Guidelines. ◦ Participant refers to the relevant CDR Participant for the item. ◦ Requirement level refers to the level of obligation. For the data standards, the key words MUST, MUST NOT, SHOULD, SHOULD NOT, and MAY are to be interpreted as described in RFC2119. CX Guidelines provide optional examples and recommendations; as such, a MAY is used to denote a CX Guideline for the purposes of this checklist regardless of the language used in the guideline statement. ◦ Statement refers to the relevant requirement or recommendation as articulated in the rules, standards, or guidelines. ◦ References points to the requirement itself, or its location; typically a rule, standard, or research. ◦ Example links to the relevant artefact, such as the CX Guideline page, which includes wireframes of example implementations, or a table in the case of data language standards. ◦ Version introduced refers to the version of the data standards that was current when the item was introduced to the CX Guidelines, starting from version 1.4.0. Items noted as introduced in 1.4.0 or earlier are requirements that exist in v1.4.0 of the CX Guidelines (PDF). ◦ Date introduced refers to the specific date the item was introduced to the CX Checklist, using August 2020 as a starting point (when v1.4.0 was introduced). The date will typically be the date of the version release, but some new items may not constitute a standards change (e.g. a revised wireframe or rules change) and as such may not align with standards versioning. ◦ Date modified refers to when an existing CX Checklist entry was updated, which is not necessarily the date the corresponding requirement (Rule, Standard or Guideline) was changed. ◦ Status refers to whether the item is active or has been retired from the CX Guidelines. An 'active' item is applicable and current. A 'retired' item may be labelled as such because it no longer applies, has been merged with another item, or has been removed from the CX Guidelines. A 'retired' item may still be a requirement. These statuses are used in the live CX Checklist and CSV to highlight changes between versions of the CX Guidelines.

Area	Focus area	Checklist ref	Type	Participant	Requirement level	Statement	Reference	Version introduced	Date introduced	Status
0AC. Accessibility	00. Accessibility	0AC.00.	CX Standard	Data HolderData Recipient	MUST	At a minimum, all CDR participants MUST seek to comply with accessibility guidelines throughout the Consent Model. These standards SHOULD be assessed, tested, and refined further by accessibility consultants directly involved in implementation.	Accessibility Standards, Accessibility	1.4.0 or earlier	12 August 2020 or earlier	Active
0AC. Accessibility	01. Content distinction	0AC.01.	CX Standard	Data HolderData Recipient	MUST	Data recipients and data holders MUST seek to have all aspects of the Consent Model comply with WCAG 1.4. This will make it easier to see and hear content, including separate foreground information from the background.	Accessibility Standards, Accessibility: Content distinction	1.4.0 or earlier	12 August 2020 or earlier	Active
0AC. Accessibility	02. Keyboard functionality	0AC.02.	CX Standard	Data HolderData Recipient	MUST	Data recipients and data holders MUST seek to have all aspects of the Consent Model comply with WCAG 2.1. This will make all functionality available from a keyboard.	Accessibility Standards, Accessibility: Keyboard functionality	1.4.0 or earlier	12 August 2020 or earlier	Active
0AC. Accessibility	03. Pointer interactions	0AC.03.	CX Standard	Data HolderData Recipient	MUST	Data recipients and data holders MUST seek to have all aspects of the Consent Model comply with WCAG 2.5. This will make it easier to operate functionality using various input devices.	Accessibility Standards, Accessibility: Pointer interactions	1.4.0 or earlier	12 August 2020 or earlier	Active
0AC. Accessibility	04. Reading experience	0AC.04.	CX Standard	Data HolderData Recipient	MUST	Data recipients and data holders MUST seek to have all aspects of the Consent Model comply with WCAG 3.1. This will make text content readable and understandable.	Accessibility Standards, Accessibility: Reading experiences	1.4.0 or earlier	12 August 2020 or earlier	Active
0AC. Accessibility	05. Input assistance	0AC.05.	CX Standard	Data HolderData Recipient	MUST	Data recipients and data holders MUST seek to have all aspects of the Consent Model comply with WCAG 3.3. This will help users avoid and correct mistakes.	Accessibility Standards, Accessibility: Input assistance	1.4.0 or earlier	12 August 2020 or earlier	Active