Accessibility Self-Review for VC Data Integrity (and vc-di-eddsa and vc-di-ecdsa)

[msporny]

The following is an Accessibility Self-Review for VC Data Integrity (and vc-di-eddsa and vc-di-ecdsa), namely the following specifications:

• Verifiable Credential Data Integrity
• Data Integrity EdDSA Cryptosuites v1.0
• Data Integrity ECDSA Cryptosuites v1.0

The three specifications listed above are cryptographic message securing mechanisms and thus do not contain text, visuals, audio, or haptic data that will be experienced directly by a human being. The one exception for this is possibly software developers, who might encounter error messages when using software libraries that implement the specification above. The errors have specific codes, which are internationalizable, but whose internationalization characteristics are up to each implementer.

We believe that these specifications, in general, do not create accessibility concerns, but are curious to know if we have overlooked some aspect of how these technologies will be used that will create accessibility issues.

The following self-review question categories were analyzed and resulted in the following answers:

• The technology DO NOT allow for visual rendering of content
• The technology DO NOT provide author control over color
• The technologies DO NOT provide features to accept user input
• The technologies DO NOT provide user interaction features
• The technologies DO NOT define document semantics
• The technologies DO NOT provide time-based visual media
• The technologies DO NOT provide audio
• The technologies DO NOT allow time limits
• The technologies DO NOT allow text content
• The technologies DO NOT create objects that don't have an inherent text representation
• The technologies DO NOT provide content fallback mechanisms, whether text or other formats
• The technologies DO NOT provide visual graphics
• The technologies DO provide internationalization support
  • Accessibility features can be internationalized to the same degree as other features
    • Specifically, the created date for a proof is expressed using XML Schema 1.1 where the date can be localized and made accessible given the nature of XML Schema 1.1 date time values.
• The technologies DO NOT define accessible alternative features
• The technologies DO NOT provide content directly for end-users
• The technologies DO NOT define an API
• The technologies DO NOT define a transmission protocol

[msporny]

The Accessibility review for this specification is complete, no changes were requested: w3c/a11y-request#61 (comment)

Closing.