DCAT 3 is an RDF vocabulary designed to facilitate interoperability between data catalogs published on the Web. It defines the metadata schema and provides examples for its use. Overall, it seems that the precautions to ensure accessibility are on the technological stack on which DCAT is developed rather than DCAT per se.
Does the technology allow visual rendering of content?
No. The DCAT 3 does not provide this.
Navigation order could be considered when browsing dataset series and versioned resources. However, the specification does not deal with visual rendering, so this question does not apply.
Does the technology provide author control over color?
No. The DCAT 3 does not provide this.
Does the technology provide features to accept user input?
No. The DCAT 3 does not provide this.
Does the technology provide user interaction features?
No. The DCAT 3does not provide this.
Does the technology define document semantics?
DCAT does not rely on a notion of page; it specifies metadata of different kinds of resources ( e.g., catalogs, datasets, data services)
Authors can indicate content language for content blocks such as RDF literals and DCAT resources.
In the former case, DCAT reuses the internationalization solution provided by RDF. In the latter case, DCAT specifies the language of catalogs or resources via dcterm:language, a metadata term provided by Dublin Core.
Does the technology provide time-based visual media?
No. The DCAT 3 does not provide this.
Does the technology provide audio?
No. The DCAT 3 does not provide this.
Does the technology provide time limits?
No. The DCAT 3 does not provide this.
Does the technology provide text content?
Somehow. However, the text is embedded in a specific data model and format (e.g., RDF, JSON-LD). DCAT assumes such underpinning data model and format standard deals with the accessibility issues.
Does the technology create objects that don't have an inherent text representation?
No. The DCAT 3 does not provide this.
Does the technology provide content fallback mechanisms, whether text or other formats?
No. The DCAT 3 does not provide this.
Does the technology provide visual graphics?
No. The DCAT 3 does not provide this.
Does the technology provide internationalization support?
Somehow. The #1504 discusses the Internationalization capability inherited by the models in which DCAT can be expressed (e.g., RDF, JSON-LD).
Does the technology define accessible alternative features?
No. The DCAT 3 does not provide this.
Does the technology provide content directly for end-users?
No. The DCAT 3 does not provide this. DCAT is a metadata model to ease the interoperability of catalogs. It does not define any presentation of the metadata.
Does the technology define an API?
No. The DCAT 3 does not provide this.
Does the technology define a transmission protocol?
No. The DCAT 3 does not provide this.
This is a self-review accessibility checklist based on https://w3c.github.io/apa/fast/checklist.html for the W3C DCAT 3 specification:
DCAT 3 is an RDF vocabulary designed to facilitate interoperability between data catalogs published on the Web. It defines the metadata schema and provides examples for its use. Overall, it seems that the precautions to ensure accessibility are on the technological stack on which DCAT is developed rather than DCAT per se.
Does the technology allow visual rendering of content?
No. The DCAT 3 does not provide this. Navigation order could be considered when browsing dataset series and versioned resources. However, the specification does not deal with visual rendering, so this question does not apply.
Does the technology provide author control over color?
No. The DCAT 3 does not provide this.
Does the technology provide features to accept user input?
No. The DCAT 3 does not provide this.
Does the technology provide user interaction features?
No. The DCAT 3does not provide this.
Does the technology define document semantics?
DCAT does not rely on a notion of page; it specifies metadata of different kinds of resources ( e.g., catalogs, datasets, data services) Authors can indicate content language for content blocks such as RDF literals and DCAT resources. In the former case, DCAT reuses the internationalization solution provided by RDF. In the latter case, DCAT specifies the language of catalogs or resources via
dcterm:language, a metadata term provided by Dublin Core.Does the technology provide time-based visual media?
No. The DCAT 3 does not provide this.
Does the technology provide audio?
No. The DCAT 3 does not provide this.
Does the technology provide time limits?
No. The DCAT 3 does not provide this.
Does the technology provide text content?
Somehow. However, the text is embedded in a specific data model and format (e.g., RDF, JSON-LD). DCAT assumes such underpinning data model and format standard deals with the accessibility issues.
Does the technology create objects that don't have an inherent text representation?
No. The DCAT 3 does not provide this.
Does the technology provide content fallback mechanisms, whether text or other formats?
No. The DCAT 3 does not provide this.
Does the technology provide visual graphics?
No. The DCAT 3 does not provide this.
Does the technology provide internationalization support?
Somehow. The #1504 discusses the Internationalization capability inherited by the models in which DCAT can be expressed (e.g., RDF, JSON-LD).
Does the technology define accessible alternative features?
No. The DCAT 3 does not provide this.
Does the technology provide content directly for end-users?
No. The DCAT 3 does not provide this. DCAT is a metadata model to ease the interoperability of catalogs. It does not define any presentation of the metadata.
Does the technology define an API?
No. The DCAT 3 does not provide this.
Does the technology define a transmission protocol?
No. The DCAT 3 does not provide this.