{"id":5413,"date":"2026-05-21T14:46:02","date_gmt":"2026-05-21T14:46:02","guid":{"rendered":"https:\/\/blog.oclc.org\/next\/?p=5413"},"modified":"2026-05-21T14:46:02","modified_gmt":"2026-05-21T14:46:02","slug":"making-accessibility-metadata-work-at-scale","status":"publish","type":"post","link":"https:\/\/blog.oclc.org\/next\/making-accessibility-metadata-work-at-scale\/","title":{"rendered":"Making accessibility metadata work at scale"},"content":{"rendered":"

\"Illustration<\/a><\/p>\n

Digital content is evolving quickly, and so are expectations for inclusive access. Libraries are being asked to deliver e-books, audiobooks, and streaming media in ways that work for everyone. But there\u2019s a practical challenge underneath those expectations: accessibility features are only discoverable if the metadata describing them is structured, consistent, and able to travel intact across the full metadata ecosystem.<\/p>\n

Over the past two years, particularly as the European Accessibility Act (EAA) has increased attention on accessibility requirements for digital content, we\u2019ve focused on a clear goal: making accessibility metadata reliable, standards-based, and scalable across WorldCat and the systems that feed it.<\/p>\n

Here\u2019s what that looks like in practice.<\/p>\n

<\/p>\n

Note: This post is informational and not legal advice. Libraries and organizations should consult appropriate legal guidance regarding accessibility requirements.<\/em><\/p>\n

Accessibility metadata is a shared responsibility<\/h2>\n

For electronic resources, accessibility metadata typically originates upstream with publishers and producers who know how a file was created and what features it supports. From there, the information moves through multiple systems and partners: publishers, distributors and aggregators, platforms and vendors, library discovery environments, and shared cataloging ecosystems.<\/p>\n

The EAA has reinforced what many already understood: every part of the metadata workflow plays a role in keeping accessibility information flowing. If that information drops out at any stage, or arrives in inconsistent forms, libraries and users pay the price through additional work and reduced discoverability.<\/p>\n

Establishing standards that bridge publishing and libraries<\/h2>\n

A major part of our work has focused on helping accessibility metadata move between publishing systems and library-standard metadata structures without losing meaning along the way.<\/p>\n

MARC 341 and 532: core carriers for accessibility metadata<\/strong><\/p>\n

In library metadata, accessibility information is most directly represented in:<\/p>\n

    \n
  • MARC 341 (Accessibility Content)<\/li>\n
  • MARC 532 (Accessibility Note)<\/li>\n<\/ul>\n

    These fields have existed for years but historically saw limited use. As accessibility expectations have increased, especially for digital content, these fields have become essential infrastructure for consistent discovery and access.<\/p>\n

    A key milestone: adding ONIX vocabulary support to MARC 341<\/strong><\/p>\n

    In December 2024, we worked with the Library of Congress to add ONIX accessibility vocabulary support to MARC 341.<\/p>\n

    This matters because:<\/p>\n

      \n
    • ONIX is the publishing industry\u2019s primary metadata format.<\/li>\n
    • ONIX includes a rich accessibility vocabulary.<\/li>\n
    • Supporting ONIX vocabulary in MARC 341 creates a standards-based bridge that helps accessibility metadata move more consistently from publisher feeds into library systems.<\/li>\n<\/ul>\n

      This is an important example of cooperative metadata work in practice. Publishers and libraries often describe resources using different metadata standards. Aligning those standards helps accessibility metadata remain interoperable across systems and improves how users discover accessible content.<\/p>\n

      Carrying accessibility metadata forward in WorldCat<\/h2>\n

      WorldCat is not static. Records are continuously added, matched, deduplicated, enriched, and merged. For accessibility metadata to remain useful, it must persist throughout that full lifecycle.<\/p>\n

      We mapped and validated how accessibility metadata moves through WorldCat ingest and processing workflows so that when records merge, accessibility metadata carries forward into the resulting record. That means if one record contains strong descriptive metadata and another contains accessibility details, the merged result can preserve both, reducing rework and improving discovery.<\/p>\n

      Scaling implementation through workflows and enrichment<\/h2>\n

      Standards only matter if they can be implemented consistently across partners, formats, and systems.<\/p>\n

      ONIX-to-MARC crosswalk enhancements<\/strong><\/p>\n

      Our teams expanded ONIX-to-MARC crosswalk workflows to include accessibility metadata.<\/p>\n

      One challenge is that publishers often describe EPUB and PDF formats separately in ONIX because accessibility features may differ by format, while libraries frequently prefer a single provider-neutral e-book record.<\/p>\n

      To support both needs, we established repeatable rules to:<\/p>\n

        \n
      • map ONIX accessibility elements into appropriate MARC fields,<\/li>\n
      • identify related product records,<\/li>\n
      • consolidate records appropriately,<\/li>\n
      • preserve meaningful format distinctions so accessibility features remain accurate and usable.<\/li>\n<\/ul>\n

        Enriching records at scale using existing metadata signals<\/strong><\/p>\n

        Not all accessibility-relevant information arrives neatly structured. Our Metadata Quality teams defined criteria to identify records where accessibility characteristics were already present elsewhere in the metadata and could be safely expressed in MARC 341.<\/p>\n

        Recently, that work enabled enrichment of approximately 1.2 million records, contributing to significant growth in accessibility metadata across WorldCat.<\/p>\n

        What this means for libraries and users<\/h2>\n

        This work improves outcomes that matter to libraries:<\/p>\n

          \n
        • more reliable discovery of accessible content,<\/li>\n
        • less local remediation work for catalogers,<\/li>\n
        • more consistent metadata across vendors and platforms,<\/li>\n
        • better user experiences for people trying to identify resources that meet their accessibility needs.<\/li>\n<\/ul>\n

          It also reinforces OCLC\u2019s role across the metadata ecosystem. We do not simply receive metadata. We help establish the standards that make metadata interoperable, and we operationalize those standards at global scale.<\/p>\n

          Ultimately, stronger accessibility metadata helps libraries create discovery experiences that are more inclusive, more reliable, and more usable for the communities they serve.<\/p>\n","protected":false},"excerpt":{"rendered":"

          Digital content is evolving quickly, and so are expectations for inclusive access. Libraries are being asked to deliver e-books, audiobooks, and streaming media in ways that work for everyone. But there\u2019s a practical challenge underneath those expectations: accessibility features are only discoverable if the metadata describing them is structured, consistent, and able to travel intact […]<\/p>\n","protected":false},"author":155,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[176,148,177],"tags":[178,6,7,179,48],"class_list":["post-5413","post","type-post","status-publish","format-standard","hentry","category-accessibility","category-metadata","category-standards","tag-accessibility","tag-cataloging","tag-metadata","tag-standards","tag-worldcat"],"yoast_head":"\nMaking accessibility metadata work at scale<\/title>\n<meta name=\"description\" content=\"Digital content is evolving quickly, and so are expectations for inclusive access.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/blog.oclc.org\/next\/making-accessibility-metadata-work-at-scale\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Making accessibility metadata work at scale | OCLC\" \/>\n<meta property=\"og:description\" content=\"Digital content is evolving quickly, and so are expectations for inclusive access.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/blog.oclc.org\/next\/making-accessibility-metadata-work-at-scale\/\" \/>\n<meta property=\"og:site_name\" content=\"OCLC Next\" \/>\n<meta property=\"article:published_time\" content=\"2026-05-21T14:46:02+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/blog.oclc.org\/next\/wp-content\/uploads\/2026\/05\/218005-Next-blog_1200x628.png\" \/>\n\t<meta property=\"og:image:width\" content=\"1200\" \/>\n\t<meta property=\"og:image:height\" content=\"628\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"Jay Holloway\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Jay Holloway\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"4 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/blog.oclc.org\\\/next\\\/making-accessibility-metadata-work-at-scale\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/blog.oclc.org\\\/next\\\/making-accessibility-metadata-work-at-scale\\\/\"},\"author\":{\"name\":\"Jay Holloway\",\"@id\":\"https:\\\/\\\/blog.oclc.org\\\/next\\\/#\\\/schema\\\/person\\\/5f28207770389da8ed8d04b2ab6b778f\"},\"headline\":\"Making accessibility metadata work at scale\",\"datePublished\":\"2026-05-21T14:46:02+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/blog.oclc.org\\\/next\\\/making-accessibility-metadata-work-at-scale\\\/\"},\"wordCount\":775,\"image\":{\"@id\":\"https:\\\/\\\/blog.oclc.org\\\/next\\\/making-accessibility-metadata-work-at-scale\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/blog.oclc.org\\\/next\\\/wp-content\\\/uploads\\\/2026\\\/05\\\/218005_Next-blog_1160x370.png\",\"keywords\":[\"Accessibility\",\"Cataloging\",\"Metadata\",\"Standards\",\"WorldCat\"],\"articleSection\":[\"Accessibility\",\"Metadata\",\"Standards\"],\"inLanguage\":\"en-US\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/blog.oclc.org\\\/next\\\/making-accessibility-metadata-work-at-scale\\\/\",\"url\":\"https:\\\/\\\/blog.oclc.org\\\/next\\\/making-accessibility-metadata-work-at-scale\\\/\",\"name\":\"Making accessibility metadata work at scale\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/blog.oclc.org\\\/next\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/blog.oclc.org\\\/next\\\/making-accessibility-metadata-work-at-scale\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/blog.oclc.org\\\/next\\\/making-accessibility-metadata-work-at-scale\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/blog.oclc.org\\\/next\\\/wp-content\\\/uploads\\\/2026\\\/05\\\/218005_Next-blog_1160x370.png\",\"datePublished\":\"2026-05-21T14:46:02+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/blog.oclc.org\\\/next\\\/#\\\/schema\\\/person\\\/5f28207770389da8ed8d04b2ab6b778f\"},\"description\":\"Digital content is evolving quickly, and so are expectations for inclusive access.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/blog.oclc.org\\\/next\\\/making-accessibility-metadata-work-at-scale\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/blog.oclc.org\\\/next\\\/making-accessibility-metadata-work-at-scale\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/blog.oclc.org\\\/next\\\/making-accessibility-metadata-work-at-scale\\\/#primaryimage\",\"url\":\"https:\\\/\\\/blog.oclc.org\\\/next\\\/wp-content\\\/uploads\\\/2026\\\/05\\\/218005_Next-blog_1160x370.png\",\"contentUrl\":\"https:\\\/\\\/blog.oclc.org\\\/next\\\/wp-content\\\/uploads\\\/2026\\\/05\\\/218005_Next-blog_1160x370.png\",\"width\":1160,\"height\":370,\"caption\":\"Illustration for accessibility\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/blog.oclc.org\\\/next\\\/making-accessibility-metadata-work-at-scale\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/blog.oclc.org\\\/next\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Making accessibility metadata work at scale\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/blog.oclc.org\\\/next\\\/#website\",\"url\":\"https:\\\/\\\/blog.oclc.org\\\/next\\\/\",\"name\":\"OCLC Next\",\"description\":\"Next provides insight and information about the work being done by and for libraries all over the world.\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/blog.oclc.org\\\/next\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/blog.oclc.org\\\/next\\\/#\\\/schema\\\/person\\\/5f28207770389da8ed8d04b2ab6b778f\",\"name\":\"Jay Holloway\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/blog.oclc.org\\\/next\\\/wp-content\\\/uploads\\\/2026\\\/05\\\/Holloway-Jay_150x150.jpg\",\"url\":\"https:\\\/\\\/blog.oclc.org\\\/next\\\/wp-content\\\/uploads\\\/2026\\\/05\\\/Holloway-Jay_150x150.jpg\",\"contentUrl\":\"https:\\\/\\\/blog.oclc.org\\\/next\\\/wp-content\\\/uploads\\\/2026\\\/05\\\/Holloway-Jay_150x150.jpg\",\"caption\":\"Jay Holloway\"},\"description\":\"Executive Director, Delivery Services, Global Product Management Jay is Executive Director, Delivery Services, Global Product Management at OCLC, where he leads product strategy for services that help libraries connect users with the resources and services they need. His work focuses on making library discovery and fulfillment more intuitive, more connected, and better aligned with how people search, learn, and work today. Jay partners with libraries, product teams, and technology colleagues to shape experiences across discovery, resource sharing, and emerging AI-enabled services\u2014helping OCLC support libraries as they meet changing expectations related to access, convenience, and trust.\",\"sameAs\":[\"http:\\\/\\\/www.oclc.org\\\/blog\\\/main\\\/\"],\"url\":\"https:\\\/\\\/blog.oclc.org\\\/next\\\/author\\\/jay-holloway\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Making accessibility metadata work at scale","description":"Digital content is evolving quickly, and so are expectations for inclusive access.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/blog.oclc.org\/next\/making-accessibility-metadata-work-at-scale\/","og_locale":"en_US","og_type":"article","og_title":"Making accessibility metadata work at scale | OCLC","og_description":"Digital content is evolving quickly, and so are expectations for inclusive access.","og_url":"https:\/\/blog.oclc.org\/next\/making-accessibility-metadata-work-at-scale\/","og_site_name":"OCLC Next","article_published_time":"2026-05-21T14:46:02+00:00","og_image":[{"width":1200,"height":628,"url":"https:\/\/blog.oclc.org\/next\/wp-content\/uploads\/2026\/05\/218005-Next-blog_1200x628.png","type":"image\/png"}],"author":"Jay Holloway","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Jay Holloway","Est. reading time":"4 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/blog.oclc.org\/next\/making-accessibility-metadata-work-at-scale\/#article","isPartOf":{"@id":"https:\/\/blog.oclc.org\/next\/making-accessibility-metadata-work-at-scale\/"},"author":{"name":"Jay Holloway","@id":"https:\/\/blog.oclc.org\/next\/#\/schema\/person\/5f28207770389da8ed8d04b2ab6b778f"},"headline":"Making accessibility metadata work at scale","datePublished":"2026-05-21T14:46:02+00:00","mainEntityOfPage":{"@id":"https:\/\/blog.oclc.org\/next\/making-accessibility-metadata-work-at-scale\/"},"wordCount":775,"image":{"@id":"https:\/\/blog.oclc.org\/next\/making-accessibility-metadata-work-at-scale\/#primaryimage"},"thumbnailUrl":"https:\/\/blog.oclc.org\/next\/wp-content\/uploads\/2026\/05\/218005_Next-blog_1160x370.png","keywords":["Accessibility","Cataloging","Metadata","Standards","WorldCat"],"articleSection":["Accessibility","Metadata","Standards"],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/blog.oclc.org\/next\/making-accessibility-metadata-work-at-scale\/","url":"https:\/\/blog.oclc.org\/next\/making-accessibility-metadata-work-at-scale\/","name":"Making accessibility metadata work at scale","isPartOf":{"@id":"https:\/\/blog.oclc.org\/next\/#website"},"primaryImageOfPage":{"@id":"https:\/\/blog.oclc.org\/next\/making-accessibility-metadata-work-at-scale\/#primaryimage"},"image":{"@id":"https:\/\/blog.oclc.org\/next\/making-accessibility-metadata-work-at-scale\/#primaryimage"},"thumbnailUrl":"https:\/\/blog.oclc.org\/next\/wp-content\/uploads\/2026\/05\/218005_Next-blog_1160x370.png","datePublished":"2026-05-21T14:46:02+00:00","author":{"@id":"https:\/\/blog.oclc.org\/next\/#\/schema\/person\/5f28207770389da8ed8d04b2ab6b778f"},"description":"Digital content is evolving quickly, and so are expectations for inclusive access.","breadcrumb":{"@id":"https:\/\/blog.oclc.org\/next\/making-accessibility-metadata-work-at-scale\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/blog.oclc.org\/next\/making-accessibility-metadata-work-at-scale\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/blog.oclc.org\/next\/making-accessibility-metadata-work-at-scale\/#primaryimage","url":"https:\/\/blog.oclc.org\/next\/wp-content\/uploads\/2026\/05\/218005_Next-blog_1160x370.png","contentUrl":"https:\/\/blog.oclc.org\/next\/wp-content\/uploads\/2026\/05\/218005_Next-blog_1160x370.png","width":1160,"height":370,"caption":"Illustration for accessibility"},{"@type":"BreadcrumbList","@id":"https:\/\/blog.oclc.org\/next\/making-accessibility-metadata-work-at-scale\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/blog.oclc.org\/next\/"},{"@type":"ListItem","position":2,"name":"Making accessibility metadata work at scale"}]},{"@type":"WebSite","@id":"https:\/\/blog.oclc.org\/next\/#website","url":"https:\/\/blog.oclc.org\/next\/","name":"OCLC Next","description":"Next provides insight and information about the work being done by and for libraries all over the world.","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/blog.oclc.org\/next\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/blog.oclc.org\/next\/#\/schema\/person\/5f28207770389da8ed8d04b2ab6b778f","name":"Jay Holloway","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/blog.oclc.org\/next\/wp-content\/uploads\/2026\/05\/Holloway-Jay_150x150.jpg","url":"https:\/\/blog.oclc.org\/next\/wp-content\/uploads\/2026\/05\/Holloway-Jay_150x150.jpg","contentUrl":"https:\/\/blog.oclc.org\/next\/wp-content\/uploads\/2026\/05\/Holloway-Jay_150x150.jpg","caption":"Jay Holloway"},"description":"Executive Director, Delivery Services, Global Product Management Jay is Executive Director, Delivery Services, Global Product Management at OCLC, where he leads product strategy for services that help libraries connect users with the resources and services they need. His work focuses on making library discovery and fulfillment more intuitive, more connected, and better aligned with how people search, learn, and work today. Jay partners with libraries, product teams, and technology colleagues to shape experiences across discovery, resource sharing, and emerging AI-enabled services\u2014helping OCLC support libraries as they meet changing expectations related to access, convenience, and trust.","sameAs":["http:\/\/www.oclc.org\/blog\/main\/"],"url":"https:\/\/blog.oclc.org\/next\/author\/jay-holloway\/"}]}},"_links":{"self":[{"href":"https:\/\/blog.oclc.org\/next\/wp-json\/wp\/v2\/posts\/5413","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.oclc.org\/next\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.oclc.org\/next\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.oclc.org\/next\/wp-json\/wp\/v2\/users\/155"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.oclc.org\/next\/wp-json\/wp\/v2\/comments?post=5413"}],"version-history":[{"count":5,"href":"https:\/\/blog.oclc.org\/next\/wp-json\/wp\/v2\/posts\/5413\/revisions"}],"predecessor-version":[{"id":5427,"href":"https:\/\/blog.oclc.org\/next\/wp-json\/wp\/v2\/posts\/5413\/revisions\/5427"}],"wp:attachment":[{"href":"https:\/\/blog.oclc.org\/next\/wp-json\/wp\/v2\/media?parent=5413"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.oclc.org\/next\/wp-json\/wp\/v2\/categories?post=5413"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.oclc.org\/next\/wp-json\/wp\/v2\/tags?post=5413"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}