{"id":6890,"date":"2019-05-10T17:06:05","date_gmt":"2019-05-10T21:06:05","guid":{"rendered":"http:\/\/blogs.library.duke.edu\/bitstreams\/?p=6890"},"modified":"2019-05-10T17:06:05","modified_gmt":"2019-05-10T21:06:05","slug":"web-accessibility-values-and-vigilance","status":"publish","type":"post","link":"https:\/\/blogs.library.duke.edu\/bitstreams\/2019\/05\/10\/web-accessibility-values-and-vigilance\/","title":{"rendered":"Web Accessibility: Values and Vigilance"},"content":{"rendered":"

The Duke Libraries are committed to providing outstanding service based on respect and empathy for the diverse backgrounds and needs in our community<\/a>. Our guiding principles<\/a> make clear how critically important diversity and inclusion are to the library, and the extent to which we strive to break down barriers to scholarship.<\/p>\n

One of the biggest and most important barriers for us to tackle is the accessibility of our web content. Duke University\u2019s Web Accessibility site<\/a> sums it up well:<\/p>\n

Duke believes web content needs to be accessible to people with a wide range of abilities, including visual, auditory, physical, speech, cognitive, language, learning, and neurological abilities.<\/p><\/blockquote>\n

\"Screenshot<\/a>
The Duke Web Accessibility website is a tremendous resource for the Duke community.<\/figcaption><\/figure>\n

This belief is also consistent with the core values expressed by the American Library Association (ALA)<\/a>. A library’s website and online resources should be available in formats accessible to people of all ages and abilities.<\/p>\n

Web Content<\/h2>\n

As one of the largest research libraries in the U.S., we have a whole lot<\/em> of content on the web to consider.<\/p>\n

Our website<\/a> alone comprises over a thousand pages with more than fifty staff contributors. The library\u00a0catalog interface<\/a> displays records for over 13 million items at Duke and partner libraries<\/a>. Our various digital repositories and digital exhibits platforms host hundreds of thousands of interactive digital objects of different types, including images, A\/V, documents, datasets, and more. The list goes on.<\/p>\n

Any attempt to take a full inventory of the library\u2019s digital content reveals potentially several million web pages under the library\u2019s purview, and all that content is managed and rendered via a dizzying array of technology platforms. We have upwards of a hundred web applications with public-facing interfaces. We built some of these ourselves, some are community-developed (with local customizations), and others we have licensed from vendors. Some interfaces are new, some are old. And some are really<\/em> old, dating all the way back to the mid-90s.<\/p>\n

Ensuring that this content is equally accessible to everyone is important, and it is indeed a significant undertaking. We must also be vigilant<\/a>\u00a0to ensure that it stays accessible over time.<\/p>\n

With that as our context, I\u2019d like to highlight a few recent efforts in the library to improve the accessibility of our digital resources.<\/p>\n

Style Guide With Color Contrast Checks<\/h2>\n

In January 2019, we launched a new catalog<\/a>, replacing a decade-old platform and its outdated interface. As we began developing the front-end, we knew we wanted to be consistent, constrained, and intentional<\/em> in how we styled elements of the interface. We were especially focused on ensuring that any text in the UI had sufficient contrast with its background to be accessible to users with low vision or color-blindness<\/a>.<\/p>\n

We tried out a few existing “living style guide” frameworks<\/a>. But none of them proved to be a good fit, particularly for color contrast management. So we ended up taking a DIY approach and developed our own living style guide using Javascript and Ruby.<\/p>\n

\"Screenshot<\/a>
The library catalog’s living style guide dynamically checks for color contrast accessibility.<\/figcaption><\/figure>\n

Here’s how it works. In our templates we\u00a0specify the array of color variable names<\/a> for each category. Then we use client-side Javascript<\/a> to dynamically measure the hex & RGB values and the luminance of each color in the guide. From those figures, we return score labels for black and white contrast ratios, color-coded for WCAG 2.0 compliance<\/a>.<\/p>\n

This style guide is “living” in that it’s a real-time up-to-date reflection of how elements of the UI will appear when using particular color variable names and CSS classes. It helps to guide developers and other project team members to make good decisions about colors from our palette to stay in compliance with accessibility guidelines.<\/p>\n

Audiovisual Captions & Interactive Transcripts<\/h2>\n

In fall 2017, I wrote about an innovative, custom-developed feature<\/a> in our Digital Repository that renders interactive caption text for A\/V within and below our media player. At that time, however, none of our A\/V items making use of that feature were available to the public.\u00a0 In the months since then, we have debuted several captioned items<\/a>\u00a0for public access.<\/p>\n

We extended these features in 2018, including: 1) exporting captions on-the-fly as Text, PDF, or original WebVTT files, and 2) accommodating transcript files that originated as documents (PDF, Word)<\/p>\n

\"Screenshot<\/a>
WebVTT caption files for A\/V are rendered as interactive HTML transcripts and can be exported into text or PDF.<\/figcaption><\/figure>\n

Two of my talented colleagues have shared more about our A\/V accessibility efforts at conferences over the past year. Noah Huffman presented at ARCHIVES*RECORDS<\/a> (Joint Annual Meeting of CoSA, NAGARA, and SAA) in Aug 2018. And\u00a0Molly Bragg presented at Digital Library Federation (DLF) Forum<\/a>\u00a0(slides<\/a>) in Nov 2018.<\/p>\n

Institutional Repository Accessibility<\/h2>\n
We have documented our work over 2018 revitalizing DSpace at Duke<\/a>, and then subsequently developing\u00a0a new set of innovative features<\/a>\u00a0that highlight Duke researchers and the impact of their work. This spring, we took a closer look at our new UI’s accessibility following Duke’s helpful guide<\/a>.<\/div>\n
<\/div>\n
In the course of this assessment, we were able to identify (and then fix!<\/em>) several accessibility issues in DukeSpace. I’ll share two strategies in particular from the guide that proved to be really effective. I highly recommend using them frequently.<\/div>\n

The Keyboard Test<\/h3>\n
How easy is it to navigate your site using only your keyboard? Can you get where you want to go using TAB, ENTER, SPACE, UP, and DOWN?\u00a0 Is it clear which element of the page current has the focus?<\/div>\n
<\/div>\n
\n
\"Screenshot
A “Skip to main content” feature in DukeSpace improves navigation via keyboard or assistive devices.<\/figcaption><\/figure>\n<\/div>\n
This test illuminated several problems. But with a few modest tweaks to our UI markup, we were able to add semantic markers to designate page sections<\/a>\u00a0and a skip to main content<\/a> link, making the content much more navigable for users with keyboards and assistive devices alike.<\/div>\n

A Browser Extension<\/h3>\n
If you\u2019re a developer like me, chances are you already spend a lot of time using your browser\u2019s Developer Tools pane to look under the hood of web pages, reverse-engineer UIs, mess with styles and markup, or troubleshoot problems.<\/div>\n
<\/div>\n
The Deque Systems aXe Chrome Extension<\/a>\u00a0(also available for Firefox<\/a>) integrates seamlessly into existing Dev Tools. It’s a remarkably useful tool to have in your toolset to help quickly find and fix accessibility issues. Its interface is clear and easy to understand. It finds and succinctly describes accessibility problems, and even tells you how to fix them in your code.<\/div>\n
<\/div>\n
\n
\"\"
An image from the Deque aXe Chrome extension site showing the tool in action.<\/figcaption><\/figure>\n<\/div>\n
<\/div>\n
With aXe testing, we quickly learned we had some major issues to fix. The biggest problems revealed were missing form labels and page landmarks, and low contrast on color pairings. Again, these were not hard to fix since the tool explained what to do, and where.<\/div>\n
<\/div>\n
Turning away from DSpace for a moment, see this example article published on a popular academic journal’s website<\/a>. Note how it fares with an automated aXe accessibility test (197 violations of various types found).\u00a0 And if you were using a keyboard, you’d have to press Tab over 100 times in order to download a PDF of the article.<\/div>\n
\n
\"Screenshot<\/a>
UI for a published journal article in a publisher’s website after running the aXe accessibility test. Violations found: 197.<\/figcaption><\/figure>\n<\/div>\n
<\/div>\n

Now, let’s look at the open access copy of that same article that resides in our DukeSpace site.<\/a> With our spring 2019 DukeSpace accessibility revisions in place, when we run an aXe test, we see zero accessibility violations<\/em>. Our interface is also now easily navigated without a mouse.<\/p>\n

\"Screenshot<\/a>
Open access copy of an article in DukeSpace: No accessibility violations found.<\/figcaption><\/figure>\n

Here’s another example of an open access article in DukeSpace<\/a> vs. its published counterpart in the website of a popular journal (PNAS)<\/a>.\u00a0 While the publisher’s site markup addresses many common accessibility issues, it still shows seven violations in aXe. And perhaps most concerning is that it’s completely unnavigable via a keyboard: the stylesheets have removed all focus styles from displaying.<\/p>\n

Concluding Thoughts<\/h2>\n

Libraries are increasingly becoming champions for open access to scholarly research<\/a>. The overlap in aims between the open access movement and web accessibility in general is quite striking. It all boils down to removing barriers and making access to information as inclusive as possible.<\/p>\n

Our open access repository UIs may never be able to match all the feature-rich bells and whistles present in many academic journal websites. But accessibility, well, that’s right up our alley. We can and should do better. It’s all about being true to our values, collaborating with our community of peers, and being vigilant in prioritizing the work.<\/p>\n

Look for many more accessibility improvements throughout many of the library’s digital resources as the year progresses.<\/p>\n

\n

Brief explanatory note about the A11Y++ image in this post: A11Y is a numeronym — shorthand for the word “accessibility”<\/a> and conveniently also visually resembling the word “ally.” The “++” is an increment operator<\/a> in many programming languages, adding one to a variable.\u00a0<\/em><\/p>\n","protected":false},"excerpt":{"rendered":"

The Duke Libraries are committed to providing outstanding service based on respect and empathy for the diverse backgrounds and needs in our community. Our guiding principles make clear how critically important diversity and inclusion are to the library, and the extent to which we strive to break down barriers to scholarship. One of the biggest … Continue reading Web Accessibility: Values and Vigilance<\/span> →<\/span><\/a><\/p>\n","protected":false},"author":103,"featured_media":6891,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[45,96,12,38],"tags":[],"class_list":["post-6890","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-digital-collections","category-duke-digital-repository","category-tech","category-user-experience"],"yoast_head":"\nWeb Accessibility: Values and Vigilance - Bitstreams: The Digital Collections Blog<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/blogs.library.duke.edu\/bitstreams\/2019\/05\/10\/web-accessibility-values-and-vigilance\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Web Accessibility: Values and Vigilance - Bitstreams: The Digital Collections Blog\" \/>\n<meta property=\"og:description\" content=\"The Duke Libraries are committed to providing outstanding service based on respect and empathy for the diverse backgrounds and needs in our community. Our guiding principles make clear how critically important diversity and inclusion are to the library, and the extent to which we strive to break down barriers to scholarship. One of the biggest … Continue reading Web Accessibility: Values and Vigilance →\" \/>\n<meta property=\"og:url\" content=\"https:\/\/blogs.library.duke.edu\/bitstreams\/2019\/05\/10\/web-accessibility-values-and-vigilance\/\" \/>\n<meta property=\"og:site_name\" content=\"Bitstreams: The Digital Collections Blog\" \/>\n<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/dukedigitalcoll\" \/>\n<meta property=\"article:published_time\" content=\"2019-05-10T21:06:05+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/blogs.library.duke.edu\/bitstreams\/files\/2019\/05\/a11y.png\" \/>\n\t<meta property=\"og:image:width\" content=\"2840\" \/>\n\t<meta property=\"og:image:height\" content=\"1488\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"Sean Aery\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@dukedigitalcoll\" \/>\n<meta name=\"twitter:site\" content=\"@dukedigitalcoll\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Sean Aery\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"8 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/blogs.library.duke.edu\\\/bitstreams\\\/2019\\\/05\\\/10\\\/web-accessibility-values-and-vigilance\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/blogs.library.duke.edu\\\/bitstreams\\\/2019\\\/05\\\/10\\\/web-accessibility-values-and-vigilance\\\/\"},\"author\":{\"name\":\"Sean Aery\",\"@id\":\"https:\\\/\\\/blogs.library.duke.edu\\\/bitstreams\\\/#\\\/schema\\\/person\\\/b1cdd20f3c85d271cfb87386a1dd28fe\"},\"headline\":\"Web Accessibility: Values and Vigilance\",\"datePublished\":\"2019-05-10T21:06:05+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/blogs.library.duke.edu\\\/bitstreams\\\/2019\\\/05\\\/10\\\/web-accessibility-values-and-vigilance\\\/\"},\"wordCount\":1575,\"commentCount\":0,\"image\":{\"@id\":\"https:\\\/\\\/blogs.library.duke.edu\\\/bitstreams\\\/2019\\\/05\\\/10\\\/web-accessibility-values-and-vigilance\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/blogs.library.duke.edu\\\/bitstreams\\\/files\\\/2019\\\/05\\\/a11y.png\",\"articleSection\":[\"Digital Collections\",\"Duke Digital Repository\",\"Technology\",\"User Experience\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/blogs.library.duke.edu\\\/bitstreams\\\/2019\\\/05\\\/10\\\/web-accessibility-values-and-vigilance\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/blogs.library.duke.edu\\\/bitstreams\\\/2019\\\/05\\\/10\\\/web-accessibility-values-and-vigilance\\\/\",\"url\":\"https:\\\/\\\/blogs.library.duke.edu\\\/bitstreams\\\/2019\\\/05\\\/10\\\/web-accessibility-values-and-vigilance\\\/\",\"name\":\"Web Accessibility: Values and Vigilance - Bitstreams: The Digital Collections Blog\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/blogs.library.duke.edu\\\/bitstreams\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/blogs.library.duke.edu\\\/bitstreams\\\/2019\\\/05\\\/10\\\/web-accessibility-values-and-vigilance\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/blogs.library.duke.edu\\\/bitstreams\\\/2019\\\/05\\\/10\\\/web-accessibility-values-and-vigilance\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/blogs.library.duke.edu\\\/bitstreams\\\/files\\\/2019\\\/05\\\/a11y.png\",\"datePublished\":\"2019-05-10T21:06:05+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/blogs.library.duke.edu\\\/bitstreams\\\/#\\\/schema\\\/person\\\/b1cdd20f3c85d271cfb87386a1dd28fe\"},\"breadcrumb\":{\"@id\":\"https:\\\/\\\/blogs.library.duke.edu\\\/bitstreams\\\/2019\\\/05\\\/10\\\/web-accessibility-values-and-vigilance\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/blogs.library.duke.edu\\\/bitstreams\\\/2019\\\/05\\\/10\\\/web-accessibility-values-and-vigilance\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/blogs.library.duke.edu\\\/bitstreams\\\/2019\\\/05\\\/10\\\/web-accessibility-values-and-vigilance\\\/#primaryimage\",\"url\":\"https:\\\/\\\/blogs.library.duke.edu\\\/bitstreams\\\/files\\\/2019\\\/05\\\/a11y.png\",\"contentUrl\":\"https:\\\/\\\/blogs.library.duke.edu\\\/bitstreams\\\/files\\\/2019\\\/05\\\/a11y.png\",\"width\":2840,\"height\":1488},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/blogs.library.duke.edu\\\/bitstreams\\\/2019\\\/05\\\/10\\\/web-accessibility-values-and-vigilance\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/blogs.library.duke.edu\\\/bitstreams\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Web Accessibility: Values and Vigilance\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/blogs.library.duke.edu\\\/bitstreams\\\/#website\",\"url\":\"https:\\\/\\\/blogs.library.duke.edu\\\/bitstreams\\\/\",\"name\":\"Bitstreams: The Digital Collections Blog\",\"description\":\"Notes from the Duke University Libraries Digital Projects Team\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/blogs.library.duke.edu\\\/bitstreams\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/blogs.library.duke.edu\\\/bitstreams\\\/#\\\/schema\\\/person\\\/b1cdd20f3c85d271cfb87386a1dd28fe\",\"name\":\"Sean Aery\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/de490821e24542e00ba40994017cf2414ed2510c15138b471561acc5fdff47f6?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/de490821e24542e00ba40994017cf2414ed2510c15138b471561acc5fdff47f6?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/de490821e24542e00ba40994017cf2414ed2510c15138b471561acc5fdff47f6?s=96&d=mm&r=g\",\"caption\":\"Sean Aery\"},\"url\":\"https:\\\/\\\/blogs.library.duke.edu\\\/bitstreams\\\/author\\\/seanaeryduke-edu\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Web Accessibility: Values and Vigilance - Bitstreams: The Digital Collections Blog","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:\/\/blogs.library.duke.edu\/bitstreams\/2019\/05\/10\/web-accessibility-values-and-vigilance\/","og_locale":"en_US","og_type":"article","og_title":"Web Accessibility: Values and Vigilance - Bitstreams: The Digital Collections Blog","og_description":"The Duke Libraries are committed to providing outstanding service based on respect and empathy for the diverse backgrounds and needs in our community. Our guiding principles make clear how critically important diversity and inclusion are to the library, and the extent to which we strive to break down barriers to scholarship. One of the biggest … Continue reading Web Accessibility: Values and Vigilance →","og_url":"https:\/\/blogs.library.duke.edu\/bitstreams\/2019\/05\/10\/web-accessibility-values-and-vigilance\/","og_site_name":"Bitstreams: The Digital Collections Blog","article_publisher":"https:\/\/www.facebook.com\/dukedigitalcoll","article_published_time":"2019-05-10T21:06:05+00:00","og_image":[{"width":2840,"height":1488,"url":"https:\/\/blogs.library.duke.edu\/bitstreams\/files\/2019\/05\/a11y.png","type":"image\/png"}],"author":"Sean Aery","twitter_card":"summary_large_image","twitter_creator":"@dukedigitalcoll","twitter_site":"@dukedigitalcoll","twitter_misc":{"Written by":"Sean Aery","Est. reading time":"8 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/blogs.library.duke.edu\/bitstreams\/2019\/05\/10\/web-accessibility-values-and-vigilance\/#article","isPartOf":{"@id":"https:\/\/blogs.library.duke.edu\/bitstreams\/2019\/05\/10\/web-accessibility-values-and-vigilance\/"},"author":{"name":"Sean Aery","@id":"https:\/\/blogs.library.duke.edu\/bitstreams\/#\/schema\/person\/b1cdd20f3c85d271cfb87386a1dd28fe"},"headline":"Web Accessibility: Values and Vigilance","datePublished":"2019-05-10T21:06:05+00:00","mainEntityOfPage":{"@id":"https:\/\/blogs.library.duke.edu\/bitstreams\/2019\/05\/10\/web-accessibility-values-and-vigilance\/"},"wordCount":1575,"commentCount":0,"image":{"@id":"https:\/\/blogs.library.duke.edu\/bitstreams\/2019\/05\/10\/web-accessibility-values-and-vigilance\/#primaryimage"},"thumbnailUrl":"https:\/\/blogs.library.duke.edu\/bitstreams\/files\/2019\/05\/a11y.png","articleSection":["Digital Collections","Duke Digital Repository","Technology","User Experience"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/blogs.library.duke.edu\/bitstreams\/2019\/05\/10\/web-accessibility-values-and-vigilance\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/blogs.library.duke.edu\/bitstreams\/2019\/05\/10\/web-accessibility-values-and-vigilance\/","url":"https:\/\/blogs.library.duke.edu\/bitstreams\/2019\/05\/10\/web-accessibility-values-and-vigilance\/","name":"Web Accessibility: Values and Vigilance - Bitstreams: The Digital Collections Blog","isPartOf":{"@id":"https:\/\/blogs.library.duke.edu\/bitstreams\/#website"},"primaryImageOfPage":{"@id":"https:\/\/blogs.library.duke.edu\/bitstreams\/2019\/05\/10\/web-accessibility-values-and-vigilance\/#primaryimage"},"image":{"@id":"https:\/\/blogs.library.duke.edu\/bitstreams\/2019\/05\/10\/web-accessibility-values-and-vigilance\/#primaryimage"},"thumbnailUrl":"https:\/\/blogs.library.duke.edu\/bitstreams\/files\/2019\/05\/a11y.png","datePublished":"2019-05-10T21:06:05+00:00","author":{"@id":"https:\/\/blogs.library.duke.edu\/bitstreams\/#\/schema\/person\/b1cdd20f3c85d271cfb87386a1dd28fe"},"breadcrumb":{"@id":"https:\/\/blogs.library.duke.edu\/bitstreams\/2019\/05\/10\/web-accessibility-values-and-vigilance\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/blogs.library.duke.edu\/bitstreams\/2019\/05\/10\/web-accessibility-values-and-vigilance\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/blogs.library.duke.edu\/bitstreams\/2019\/05\/10\/web-accessibility-values-and-vigilance\/#primaryimage","url":"https:\/\/blogs.library.duke.edu\/bitstreams\/files\/2019\/05\/a11y.png","contentUrl":"https:\/\/blogs.library.duke.edu\/bitstreams\/files\/2019\/05\/a11y.png","width":2840,"height":1488},{"@type":"BreadcrumbList","@id":"https:\/\/blogs.library.duke.edu\/bitstreams\/2019\/05\/10\/web-accessibility-values-and-vigilance\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/blogs.library.duke.edu\/bitstreams\/"},{"@type":"ListItem","position":2,"name":"Web Accessibility: Values and Vigilance"}]},{"@type":"WebSite","@id":"https:\/\/blogs.library.duke.edu\/bitstreams\/#website","url":"https:\/\/blogs.library.duke.edu\/bitstreams\/","name":"Bitstreams: The Digital Collections Blog","description":"Notes from the Duke University Libraries Digital Projects Team","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/blogs.library.duke.edu\/bitstreams\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/blogs.library.duke.edu\/bitstreams\/#\/schema\/person\/b1cdd20f3c85d271cfb87386a1dd28fe","name":"Sean Aery","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/de490821e24542e00ba40994017cf2414ed2510c15138b471561acc5fdff47f6?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/de490821e24542e00ba40994017cf2414ed2510c15138b471561acc5fdff47f6?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/de490821e24542e00ba40994017cf2414ed2510c15138b471561acc5fdff47f6?s=96&d=mm&r=g","caption":"Sean Aery"},"url":"https:\/\/blogs.library.duke.edu\/bitstreams\/author\/seanaeryduke-edu\/"}]}},"_links":{"self":[{"href":"https:\/\/blogs.library.duke.edu\/bitstreams\/wp-json\/wp\/v2\/posts\/6890","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blogs.library.duke.edu\/bitstreams\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blogs.library.duke.edu\/bitstreams\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blogs.library.duke.edu\/bitstreams\/wp-json\/wp\/v2\/users\/103"}],"replies":[{"embeddable":true,"href":"https:\/\/blogs.library.duke.edu\/bitstreams\/wp-json\/wp\/v2\/comments?post=6890"}],"version-history":[{"count":9,"href":"https:\/\/blogs.library.duke.edu\/bitstreams\/wp-json\/wp\/v2\/posts\/6890\/revisions"}],"predecessor-version":[{"id":6907,"href":"https:\/\/blogs.library.duke.edu\/bitstreams\/wp-json\/wp\/v2\/posts\/6890\/revisions\/6907"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blogs.library.duke.edu\/bitstreams\/wp-json\/wp\/v2\/media\/6891"}],"wp:attachment":[{"href":"https:\/\/blogs.library.duke.edu\/bitstreams\/wp-json\/wp\/v2\/media?parent=6890"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blogs.library.duke.edu\/bitstreams\/wp-json\/wp\/v2\/categories?post=6890"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blogs.library.duke.edu\/bitstreams\/wp-json\/wp\/v2\/tags?post=6890"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}