Accessibility Self-Review for VC JSON Schema

[decentralgabe]

The following is an Accessibility Self-Review for VC JSON Schema, namely the following specification:

• VC JSON Schema

The specification listed above is a method to define a JSON Schema for static validation of a verifiable credential. A JSON Schema and its validation are intended to be machine-readable, though they are also constructed and used by human beings.

JSON Schemas, by design, are not intended to be internationalizable, since they are used for strict static validation of data. An implementer may choose to translate a JSON Schema, or make it available in a variety of languages; however, these would be considered distinct JSON Schemas. When packaging VC JSON Schemas as verifiable credentials, implementers are encouraged to follow the guidance listed in the VC Data Model.

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 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 NOT provide internationalization support
• 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

[decentralgabe]

review kicked off w3c/a11y-request#64

[decentralgabe]

Closed and passed w3c/a11y-request#64 (comment)