add :accessibilityStatement either to BIBO or DCTerms

[kcoyle]

No usable property was found.

This is needed to inform potential users of accessibility features.
Recommendation:

• Add accessibilityStatement either to BIBO or DCTerms.

[tombaker]

With what definition? I'm looking at the definition of the class RightsStatement

A statement about the intellectual property rights (IPR) held in or over a resource, a legal document giving official permission to do something with a resource, or a statement about access rights.

Something like this?

[kcoyle]

I'm not sure that we made the distinction between "accessible = you have the rights" vs "accessible = can be used with a screen reader." There was a discussion in February that seems to have concluded that we should leave this ambiguous. I'll see if I can find more.

[niklasl]

Possibly relevant: https://schema.org/accessibilityFeature (and https://schema.org/accessibilityHazard).

Note also that in the Swedish union library catalogue (Libris), we are planning to use (and/or define) IRIs for the terms in the a11y vocabulary, for improved usage and application support (by having labels and meanings of each term in different languages; and possible broader implications, including coordination with media/carrier types). This is an argument for allowing both text values and IRIs for this property.

[aisaac]

The SRAP doc mentions that accessibility here aligns with MARC element 532, which seems to be about accessibility not in the sense of access rights: https://www.loc.gov/marc/bibliographic/bd532.html
Which seems appropriate to me, and deserving its own element if it's not elsewhere. It would be good though, if the element name could make it clear that is is different from what dcterms:rights/dcterms:RightsStatement support!

[osma]

This was definitely intended to represent accessibility in the WCAG sense, for example adequate contrast and screen reader support.

If the Statement suffix has problematic connotations, I think we could rename it to something different. For example accessibilitySummary would align with MARC 532 subfield $a, which is called "Summary of accessibility" and defined as

Text describing accessibility features, hazards, and deficiencies as well as technical details relating to accessibility features.

[kcoyle]

resourceAccessibility?

[annakasprzik]

accessibilityInformation? accessibilityInfo?

[annakasprzik]

accessibilityNote?

[osma]

Note: We didn't discuss in today's review meeting whether this property should go to BIBO or DCTerms. Personally, I think this would be a good fit for DCTerms because it's very general. Anyway, we need to make a decision on this as well (unless changing DCTerms is strictly off-limits...)

[kallimathios]

Language and framing from the IFLA Accessibility Metadata & Accessible Formats in Working Group may be helpful: https://docs.google.com/document/d/1IrGR0vQeKIfEhltJj4TSvy4-1DNSncH6pfH87sXrEY8/edit?tab=t.0

Also referenced:

• https://www.loc.gov/marc/bibliographic/bd532.html
• https://commission.europa.eu/strategy-and-policy/policies/justice-and-fundamental-rights/disability/union-equality-strategy-rights-persons-disabilities-2021-2030/european-accessibility-act_en
• https://www.levelaccess.com/compliance-overview/european-accessibility-act-eaa/

Suggested definition: information about the accessibility of a resource