Updated @May 1, 2024
About CX checklist
The CX Checklist is a complete list of items referenced in the CX Guidelines, including relevant rules, privacy safeguards, and data standards (CX and technical). This list has been created for the purposes of assisting implementation and compliance, but should not be seen as a complete list of CDR Participant obligations. CDR Participants should also refer to the CDR Rules, data standards, and privacy guidelines for a complete view of obligations. See something wrong? Let us know at cx@consumerdatastandards.gov.au
‣
Read first CX Checklist attributesArearefers to the stage in the consumer journey, such as Pre-consent, Consent, Authenticate, Authorise, or Consent Management.Focus arearefers to a specific theme in each stage (e.g. 01. User Identifier).Checklist refcontains 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
Examplecolumn). Typerefers to the source of the statement: Rules, Standards and Guidelines.Participantrefers to the relevant CDR Participant for the item.Requirement levelrefers 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.Statementrefers to the relevant requirement or recommendation as articulated in the rules, standards, or guidelines.Referencespoints to the requirement itself, or its location; typically a rule, standard, or research.Examplelinks 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 introducedrefers 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 introducedrefers 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 modifiedrefers to when an existing CX Checklist entry was updated, which is not necessarily the date the corresponding requirement (Rule, Standard or Guideline) was changed.Statusrefers 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.
Download CX checklist files
Note: The CX checklist may appear different depending on the program used. Please use the program's features or adjust cells so that all content is displayed.
Download CX Checklist
| Item | File | Date released | Version introduced |
|---|---|---|---|
May 1, 2024 | 1.30.0 |
For past versions, refer to .Change log
CX Checklist (web version)
This checklist is updated on an ongoing basis
The web version was last updated @May 1, 2024. For more details, view .Change log
| Area | Focus area | Checklist ref | Type | Participant | Requirement level | Statement | Reference | Example | Version introduced | Date introduced | Date modified | Status |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
0AC. 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. | 1.4.0 or earlier | 12 August 2020 or earlier | Active | ||||
0AC. Accessibility | 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. | 1.4.0 or earlier | 12 August 2020 or earlier | Active | ||||
0AC. Accessibility | 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. | 1.4.0 or earlier | 12 August 2020 or earlier | Active | ||||
0AC. Accessibility | 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. | 1.4.0 or earlier | 12 August 2020 or earlier | Active | ||||
0AC. Accessibility | 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. | 1.4.0 or earlier | 12 August 2020 or earlier | Active | ||||
0AC. Accessibility | 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. | 1.4.0 or earlier | 12 August 2020 or earlier | Active |