Add dedicated accessibility fields
Add fields to document the accessibility of individual research assets. This information can help Esploro managers track accessibility compliance for items and set expectations for users who may want to access items. At minimum, one field with controlled vocabulary terms and another for free-text entries would be helpful. See Cornell eCommons for sample controlled vocabulary terms addressing accessibility features and accessibility hazards: https://guides.library.cornell.edu/ecommons/batchmetadata#s-lib-ctab-19527879-4 We need our repositories to be in compliance with WCAG guidance and better mechanisms for tracking accessibility are paramount.
Talea Anderson
shared this idea
AdminTami Ezra
(Admin, Ex Libris)
responded
Removing the "accepted" status so that institution can continue voting as agreed with the PWG.
-
Anita Euving
commented
We would love to have Accessibility Content (341 field, controlled) and Accessibility Note (532 field, free text) added to Alma and Alma Analytics as search options/criteria. It would be very helpful in identifying records that include (or do not include) these fields. Libraries need to be in compliance with the new WCAG 2.1 AA standards in 2026 or 2027. Even though accessible MARC fields are not included in the ruling, it would be a useful and helpful addition that will help our users, since the fields can also be used to create accessibility facets in Primo.