Schema.org A11Y reference in Webography

[LaZay]

trafficstars

The A.1 Informative references section is lacking the link to Schema.org Accessibility Properties for Discoverability Vocabulary.

It is highly important to correctly source this standard, as Schema.org web site does not provide the list of ALL accessibility properties it has defined. Many people think there is one property = "accessibilityFeature", which is not the case. There are 6 accessiblity properties in Schema:

1. accessMode
2. accessModeSufficient
3. accessibilityControl
4. accessibilityHazard
5. accessibilityFeature
6. accessibilityAPI

With N values for EACH. Futhermore, authorized values for each property have changed location in the pages. They are no more directly provided for each property's page. They are hidden behind this sentence now: "Values should be drawn from the approved vocabulary"

Only the Schema.org Accessibility Properties for Discoverability Vocabulary provides the full picture about the way Schema handles accessibility metadata (i.e. properties, and values).

[danbri]

What would like us to do about this at Schema.org?

I can easily update the link to https://www.w3.org/2021/a11y-discov-vocab/latest/ but it seems you’re suggesting we should update the per-property documentation too?

[mattgarrish]

I don't see there's anything to change in schema.org in this issue @danbri. We don't want to maintain all the values in the schema.org pages for the properties, and all the links correctly go across to the latest version of the vocabulary (we updated that not too long back).

These issues are just about the informative crosswalk. There isn't a reference to the vocabulary in s. 2 of that page, so the properties and values are listed without reference to where they are defined. That page hasn't been updated since we ported it from the old wiki, I don't believe.

I'm tagging them with the crosswalk label for whenever @clapierre and @madeleinerothberg have time to return to the document.

[clapierre]

We believe this has been recently addressed please reopen with additional information if this is still and outstanding issue.