Verifiable Credentials Data Model 1.0

2017-08-16: ACTION-2141 Léonie to review. ACTION-2142 Gottfried to review.
2017-08-30: Gottfried reports now issues modulo some non-a11y stuff he could file separately.
2017-09-04: Léonie reports no concerns.
2018-07-20: Wide review request sent to WAI-IG, pointing to Verifiable Credentials Data Model 1.0 which appears to be an editors' draft of this under a different name. Janina to contact and sort out.
2018-07-23: Tzviya interested in reviewing.
2018-07-25: ACTION-2175 Tzviya to review.
2018-07-30: draft comments.
2018-08-01: Discussed in 1 Aug 2018 APA meeting. Will send a CfC to forward those comments as APA comments.
2018-08-15: Comments sent.
2019-09-05: Has gone to PR.
2019-10-02: Looking into what happened to our comments, they appear not to monitor their comments list. MC to raise to PLH.
2019-10-09: They did port issues to GitHub and appear to have addressed. We need to check if we're satisfied with how.
2020-01-08: Discussion in APA, APA to prepare use cases, over to RQTF.
2022-06-15: Declaring review complete.

Review by Gottfried 2017-08-30

The Verifiable Claims Data Model and Representations draft 03 August 2017 does not contain any requirements or recommendations on the user interface, nor does the related Verifiable Claims Use Cases Note 08 June 2017. Therefore, there is no reason for raising accessibility concerns.

On an internal discussion, I see two points worth considering here, but none of them is critical enough to raise a flag.

If verifiable claims contain information about a person’s health status of disability, this information needs to be protected on a highest level for privacy and security. Note that privacy and security considerations are already covered in sections 5 and 6 of the Verifiable Claims Data Model and Representations draft 03 August 2017.
On a first sight, one could hope that the ecosystem for verifiable claims could be also used for a controlled distribution of personal preference profiles identifying user interface needs and preferences of individual users. However, the ecosystem presented in Verifiable Claims Data Model and Representations draft 03 August 2017 is informal (not normative), and does only contain components that help to verify data - not to store and manage the data. For personal preference profiles, the verification is usually not important – since the user does not gain privileges over other users by claiming to need a a specific set of preferences. There is one exception, though: If the user can get access to electronic texts that would otherwise be protected by copyright – due to their visual impairment. But this use case can be implemented by the Verifiable Claims Data Model and Representations draft 03 August 2017 without the need for a personal preference profile.