rdf12-semantics 2025-11-25 > 2025-12-23

[ktk]

In the issue title above add the document name followed by the date of this request, then the date of your proposed deadline for comments.

• name of spec to be reviewed: RDF 1.2 Semantics

• shortname: rdf12-semantics

• URL of spec: https://www.w3.org/TR/2025/WD-rdf12-semantics-20251111/

• What and when is your next expected transition? In ~4 Weeks

• What has changed since any previous review?

  • introduction of triple term in the abstract data model
  • introduction of base direction in literals
  • introduction of version announcement in concrete syntaxes

• Please point to the results of your own self-review: Response to the A11y checklist for the RDF specifications rdf-star-wg#182

• Where and how to file issues arising?: https://github.com/w3c/rdf-semantics/

• Pointer to any explainer for the spec?: https://www.w3.org/TR/rdf12-primer/

Other comments:

[pchampin]

@matatk , if I read a11y-tracking#278 correctly, you found no issue. Is it OK if we close this issue then?

[domel]

In the specification, there are text fragments placed inside a <table> element even though they are not truly tabular data (e.g., they are definitions or other narrative content). While this remains “legal” / valid HTML, it may still be considered suboptimal from an accessibility (a11y) perspective, because <table> introduces a specific semantic meaning into the accessibility tree.

[matatk]

@pchampin sorry for my slow reply; I thought we had closed these issues - from a spec perspective, as you noted, we did not find accessibility issues.

To the point @domel made (thank you) there are some accessibility challenges for reading the spec; the <table> issue as mentioned, and there are some diagrams that do not have sufficient textual equivalents. We would like to help at least by pointing you to advice on those issues. We could do this by filing a couple of issues in the spec's repo, if you like?

Note: those issues would be non-blocking for the purposes of TR.

[pchampin]

We could do this by filing a couple of issues in the spec's repo, if you like?

Yes please! There was a lot of internal discussions on these, but lack of a11y expertise to settle them. So any guidance will be greatly appreciated :)

Note: those issues would be non-blocking for the purposes of TR.

Therefore closing this. Thanks again.