Re: A11y checkist

On 04/05/2022 14:16, Pierre-Antoine Champin wrote:
> Hi all,
>
> I had a look at the self-review accessibility checklist [1], and two 
> related sentences caught my attention :
>
> > In the [case of literals], DCAT reuses the internationalization 
> solution provided by RDF.
>
> > DCAT assumes such underpinning data model and format standard 
> [(RDF)] deals with the accessibility issues.
>
> However, there was some discussion some time ago, in the JSON-LD WG, 
> on whether RDF language-tagged literals sufficiently address this kind 
> of problem. In particular, these literals do not provide any standard 
> mean to encode the directionality of the text, which in some cases can 
> be a problem. Some possible evolutions of RDF were discussed [2] to 
> address this issue, but there was not enough momentum or agreement to 
> make them standard. JSON-LD itself resorted to two non-normative 
> options [3].
Oops, I am now noticing that this is indeed hinted in the I18N review 
checklist (https://github.com/w3c/dxwg/issues/1504). Sorry for the noise.
>
> Maybe that is something that DCAT could/should hint to?
>
> > Does the technology provide internationalization support? No
>
> I was also surprised of this. DCAT can be used to provide titles, 
> keywords... in multiple languages, as illustrated in many examples in 
> the spec. I would call this "internationalization support"...
>
>   best
>
>
> [1] https://github.com/w3c/dxwg/issues/1506

> [2] https://w3c.github.io/rdf-dir-literal/

> [3] https://www.w3.org/TR/json-ld11-api/#dom-jsonldoptions-rdfdirection

>