CINXE.COM

Accessibility Statement - Sherpa Services

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" lang="en-gb"> <!--<![endif]--> <head> <!-- Global site tag (gtag.js) - Google Analytics --> <script async="async" src="https://www.googletagmanager.com/gtag/js?id=UA-3477654-9">// <!-- No script --></script> <script> window.dataLayer = window.dataLayer || []; function gtag(){dataLayer.push(arguments);} gtag('js', new Date()); gtag('config', 'UA-3477654-9'); </script> <meta charset="utf-8" /> <meta http-equiv="X-UA-Compatible" content="IE=edge" /> <meta content="width=device-width,initial-scale=1.0" name="viewport" /> <!-- The above 3 meta tags must come first in the head; any other head content must come after these tags. --> <meta content="on" http-equiv="cleartype" /> <!--[if IE]><![endif]--> <!--[if lte IE 8]> <link rel="stylesheet" href="/ux.jisc.2.0.0/css/ux.jisc-2.0.0.style-oldie.min.css" media="all"> <script src="//cdnjs.cloudflare.com/ajax/libs/html5shiv/3.7.2/html5shiv.min.js"></script> <![endif]--> <!--[if gt IE 8]><!--> <link rel="stylesheet" href="/ux.jisc.2.0.0/css/ux.jisc-2.0.0.style.min.css" media="all" /> <link rel="stylesheet" href="/javascript/JavaScript-autoComplete-master/auto-complete.css" /> <!--<![endif]--> <script src="/ux.jisc.2.0.0/js/ux.jisc-2.0.0.script-head.min.js">// <!-- No script --></script> <meta http-equiv="X-UA-Compatible" content="IE=edge" /> <link rel="icon" href="/favicon.ico" type="image/x-icon" /> <link rel="shortcut icon" href="/favicon.ico" type="image/x-icon" /> <link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/font-awesome/4.7.0/css/font-awesome.min.css" /> <link rel="stylesheet" href="/style/print.css" media="print" /> <link rel="stylesheet" href="/style/banner.css" media="screen" /> <!-- Apple touch icons are used as icons when a user adds your webapp to the home screen of aniOS devices. Though the dimensions of the icon can vary between iOS devices and versions one 180×180px touch icon named apple-touch-icon.png and including the following in the <head> of the page is enough: --> <link rel="apple-touch-icon" sizes="180x180" href="/apple-touch-icon.png" /> <!-- For desktop browsers place favicon.ico in the root directory. --> <!-- The web app manifest is a simple JSON file that allows you to control how your app appears on a device's home screen, what it looks like when it launches in that context and what happens when it is launched. This allows for much greater control over the UI of a saved site or web app on a mobile device. It's linked to from the HTML as follows: --> <link rel="manifest" href="/site.webmanifest" /> <!-- You can add the theme-color meta extension in the <head> of your pages to suggest the color that browsers and OSes should use if they customize the display of individual pages in their UIs with varying colors. --> <meta name="theme-color" content="#191919" /> <!-- Pin pages to the taskbar or start menu in Windows. Windows looks for browserconfig.xml in root by default so place browserconfig.xml in the root directory. More info: https://msdn.microsoft.com/en-us/library/ie/dn455106.aspx --> <title> Accessibility Statement - Sherpa Services </title> <link rel="Top" href="https://v2.sherpa.ac.uk/" /> <link rel="Sword" href="https://v2.sherpa.ac.uk/sword-app/servicedocument" /> <link rel="SwordDeposit" href="https://v2.sherpa.ac.uk/id/contents" /> <link rel="Search" type="text/html" href="https://v2.sherpa.ac.uk/cgi/search" /> <link rel="Search" type="application/opensearchdescription+xml" href="https://v2.sherpa.ac.uk/cgi/opensearchdescription" title="Sherpa Services" /> <script type="text/javascript"> // <![CDATA[ var eprints_http_root = "https://v2.sherpa.ac.uk"; var eprints_http_cgiroot = "https://v2.sherpa.ac.uk/cgi"; var eprints_oai_archive_id = "v2.sherpa.ac.uk"; var eprints_logged_in = false; var eprints_logged_in_userid = 0; var eprints_logged_in_username = ""; var eprints_logged_in_usertype = ""; // ]]></script> <style type="text/css">.ep_logged_in { display: none }</style> <link rel="stylesheet" type="text/css" href="/style/auto-3.4.4.css?1718105074" /> <script type="text/javascript" src="/javascript/auto-3.4.4.js?0"> //padder </script> <!--[if lte IE 6]> <link rel="stylesheet" type="text/css" href="/style/ie6.css" /> <![endif]--> <meta name="Generator" content="EPrints 3.4.4" /> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /> <meta http-equiv="Content-Language" content="en" /> </head> <body> <header class="masthead" role="banner" data-mobilemenu=""> <div class="masthead__top"> <div class="inner"> <a id="skiplinks" class="visuallyhidden focusable in-page" href="#main" tabindex="1"> <span>Skip to main content</span> </a> <a class="masthead__logo" href="https://www.jisc.ac.uk"> <img alt="Jisc logo" src="/ux.jisc.2.0.0/logo.png" /> </a> </div> </div> <div class="masthead__main masthead__main--with-content masthead__main--opendoar"> <div class="inner"> <div id="new-opendoar-banner" class="new-opendoar-banner"> <div> <p class="banner-title">OpenDOAR will be moving!</p> <p>Our new site is launching soon. We'll redirect you, so you won't have to do anything.</p> </div> <img src="/img/OPENDOAR_image.png" alt="Illustration of two people using the OpenDOAR service" /> </div> <p class="masthead__title masthead__title--short"> <a href="/opendoar/">OpenDOAR</a> </p> <div class="nav-wrapper"> <nav class="masthead__nav header__nav--primary" role="navigation" data-dropdown=""> <ul> <li class="nav__item" id="nav_about_tab"> <a href="https://v2.sherpa.ac.uk/opendoar/about.html">About</a> </li> <li class="nav__item" id="nav_search_tab"> <a href="https://v2.sherpa.ac.uk/opendoar/search.html">Directory</a> </li> <li class="nav__item" id="nav_policytool_tab"> <a href="https://v2.sherpa.ac.uk/opendoar/policytool/">Support</a> </li> </ul> </nav> <nav class="masthead__nav masthead__nav--secondary" id="nav_admin_tab"> <ul> <li class="nav__item" id="nav_contact_tab"> <a href="https://v2.sherpa.ac.uk/opendoar/contact.html">Contact</a> </li> <!-- <li class="nav__item"> <a href="{$config{http_url}}/cgi/users/home">Admin</a> </li> --> </ul> </nav> </div> </div> </div> </header> <main id="main" role="main" class="main"> <div class="inner l-pull-left featured"> <div class="l-centre-offset" style="min-height: 300px"> <div class="row"> <h1 class="h1_like_h2"> Accessibility Statement </h1> <div class="static-page"> <p>This statement applies to content published on https://v2.sherpa.ac.uk. It does not apply to content on www.jisc.ac.uk (for example, www.jisc.ac.uk/open-access).</p> <p>This website is run by Jisc. It is designed to be used by as many people as possible. The text should be clear and simple to understand. You should be able to:</p> <ul> <li>Change colours, contrast levels and fonts</li> <li>Zoom in up to 300% without problems</li> <li>Navigate most of the website using just a keyboard</li> <li>Navigate most of the website using speech recognition software</li> <li>Use most of the website using a screen reader (including the most recent versions of JAWS, NVDA and VoiceOver)</li> </ul> <p><a href="https://mcmw.abilitynet.org.uk/">AbilityNet</a> has advice on making your device easier to use if you have a disability.</p> <h2>How accessible this website is</h2> <p>We know some parts of this website aren't fully accessible:</p> <ul> <li>Some PDF documents aren't fully accessible to screen reader software</li> <li>Some heading elements are not consistent</li> <li>Some images do not contain alternative text</li> <li>We have issues with some third-party interactive elements</li> <li>We have some content issues</li> </ul> <h2>How to request content in an accessible format</h2> <p>If you need information on this website in a different format like accessible PDF, large print, easy read, audio recording or braille contact us:</p> <ul> <li>email - <a href="mailto:help@jisc.ac.uk">help@jisc.ac.uk</a></li> <li>call - <a href="tel:0300 3002212">0300 3002212</a></li> <li>or speak to your account manager</li> </ul> <p>We'll consider your request and get back to you.</p> <h2>Reporting accessibility problems with this website</h2> <p>If you find any problems that aren't listed on this page or think we're not meeting the requirements of the accessibility regulations, use the 'spotted an issue?' button at the foot of every page, or contact <a href="mailto:help@jisc.ac.uk">help@jisc.ac.uk</a>.</p> <h2>Enforcement procedure</h2> <p>If you contact us with a complaint and you're not happy with our response contact the <a href="https://www.equalityadvisoryservice.com/">Equality Advisory and Support Service (EASS)</a>.</p> <p>The Equality and Human Rights Commission (EHRC) is responsible for enforcing the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018 (the 'accessibility regulations').</p> <h2>Technical information about this website's accessibility</h2> <p>Jisc is committed to making its websites accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018. This website is partially compliant with the Web Content Accessibility Guidelines version (WCAG) 2.1 AA standard, due to the non-compliances listed below.</p> <h2>Non-accessible content</h2> <p>The content listed below non-accessible for the following reasons.</p> <h3>Non-compliance with the accessibility regulations</h3> <ul> <li>Content issues <ul> <li>A small number of pages have HTML content where the language is not identified. This fails WCAG 2.1 A 3.1.1 success criterion (Language of Page). We plan to fix this by the end of August 2024.</li> <li>Our footnote and abbreviations aren't fully accessible to screen readers. This does not meet WCAG 2.1 A success criterion 2.1.1 (Keyboard). We plan to develop an alternative to our current footnote approach. We are investigating what can be done to improve our abbreviations.</li> </ul></li> <li>Issues with page structure <ul> <li>There are some issues with the page structures on our sites. The heading order doesn't always clearly reflect the structure of the page in some sections and headings are not always clearly labelled. This does not meet WCAG 2.1 A success criterion 1.3.1 (Info and Relationships). We are addressing these and plan to fix this by the end of August 2024.</li> </ul></li> <li>Issues with links <ul> <li>There are a small number of redundant links used, where adjacent links go to the same URL. This fails WCAG 2.1 A 2.4.4 (Link Purpose (In Context)). We plan to fix this by the end of August 2024.</li> <li>Some linked images are missing alternative text. This fails WCAG 2.1 A 1.1.1 (Non-text Content) and 2.4.4 (Link Purpose). We plan to fix this by the end of August 2024.</li> </ul></li> <li>Keyboard controls <ul> <li>We have some issues with pages that can't be fully controlled using the keyboard — for example, the publisher policy section of publication pages on Sherpa Romeo. This doesn't meet WCAG 2.1 A success criterion 2.1.1 (Keyboard). We plan to fix this by the end of August 2024.</li> </ul></li> <li>Issues with PDFs and other documents <ul> <li>We provide links to PDF documents which don't meet accessibility standards - for example, they may not be marked up so they're accessible to a screen reader. This doesn't meet WCAG 2.1 A success criterion 4.1.2 (Name, Role, Value). We plan to fix this by the end of August 2024. Any new PDFs or Word documents we publish should meet accessibility standards.</li> </ul></li> <li>Issues with images, video and audio <ul> <li>A small number of images do not contain alternative text. This fails WCAG 1.1.1 (Non-text Content). We plan to fix this by the end of August 2024.</li> <li>There is unhelpful alt text on some images, especially where icons are used. This does not meet WCAG 2.1 A success criterion 1.1.1 (non-text content). We plan to fix this by the end of August 2024.</li> <li>There are some instances of redundant alternative text where the advisory information is very similar to the alternative text. This does not meet WCAG 2.1 A success criterion 1.1.1 (Non-text Content). We plan to fix this by the end of August 2024.</li> </ul></li> <li>Issues with interactive tools <ul> <li>Some of our search functions are missing descriptions of elements and therefore may be difficult to navigate using screen readers. This fails WCAG 1.1.1 (Non-text Content) and WCAG 3.3.2 (Labels or Instructions).</li> <li>Some of our interactive forms are difficult to navigate using a keyboard. For example, because some form controls are missing a 'label' tag. This does not meet WCAG 2.1 A success criterion 4.1.2 (Name, Role, Value). We plan to fix this by the end of August 2024.</li> </ul></li> <li>Third-party tools: YouTube <ul> <li>We embed YouTube videos on the site. We know there are accessibility issues with these features. We don't have accessible alternatives and, as we don't control the platform, are unable to make the changes required to improve them. Let us know if you would like an accessible version of any video we provide and we will send it through to you.</li> </ul></li> <li>Third-party links: Links to external websites <ul> <li>Some of our pages link to external websites and external PDFs which may contain accessibility issues. We don't have accessible alternatives and, as we don't control these websites, and are unable to make the changes required to improve them. Let us know if you would like an accessible version of any third-party PDF and we will consider your request.</li> </ul></li> <li>Issues with forms <ul> <li>Some form elements do not have labels and may cause assistive technologies to not behave as expected.</li> </ul></li> <li>Issues with page elements <ul> <li>Some select drop down functionality and frames do not have appropriate aria labels and may cause assistive technologies to not behave as expected.</li> <li>Some elements do not meet the minimum colour contrast ratio thresholds thus some users may find reading particular sections difficult.</li> <li>Some links may not be distinguishable without relying on colour thus may not be obvious at a glance.</li> <li>Some list elements are not contained correctly. This may cause assistive technologies to not behave as expected.</li> <li>Some ARIA roles that must contain particular children do not. This may cause assistive technologies to not behave as expected.</li> </ul></li> </ul> <h3>Disproportionate burden</h3> <p>Resources has been focused towards the development of Unified Sherpa Services (V3 Sherpa) and as such the Sherpa Development team are unable to address all accessibility issues on V2 Sherpa. This is due to V2 Sherpa being legacy and that the technical knowledge of the system has degraded over time. Any major reported issue(s) however will be addressed to improve user experience and inclusion on V2 Sherpa until Unified Sherpa Services is released. The Sherpa Development team's resources are focused on progressing Unified Sherpa Services' release.</p> <p>The new Unified Sherpa Services application, when fully launched, is expected to address all accessibility issues currently experienced on V2 Sherpa and be fully WCAG 2.1 AA compliant.</p> <p>Unified Sherpa Services is scheduled to be fully launched by the end of January 2025.</p> <h2>How we tested this website</h2> <p>This website was and is currently being tested for compliance with the Web Content Accessibility Guidelines 2.1 Level A and Level AA, and these tests have been carried out internally on 21 November 2023.</p> <p>We used the Website Accessibility Conformance Evaluation Methodology (WCAG-EM) approach to decide on a sample of pages to test. We tested our sample using manual testing and accessibility tools, including Wave and Axe.</p> <h2>What we're doing to improve accessibility</h2> <p>Whenever new features are released, they must meet WCAG 2.1 AA. We're also committed to working on the issues above. This content is modified from the GOV.UK accessibility statement - used through the Open Government Licence v3.0.</p> <h2>Version information</h2> <p>This is V1 of the Sherpa Services Accessibility Statement. This statement was first published on 3rd September 2020.</p> <p>This statement was prepared on 28 August 2020. It was last updated on 22 November 2023.</p> </div> </div> </div> </div> </main> <footer role="contentinfo"> <!--.light here denotes depth of bg tint--> <div class="inner l-pull-left light l-gutter--top"> <div class="l-centre-offset row"> <div class="col span-4"> <div class="linklist l-gutter--right"> <div class="linklist__title">Useful links</div> <ul> <li class="linklist__item"><a href="https://www.jisc.ac.uk/guides?f%5B0%5D=field_project_topics%3A455&amp;topic=9">Open access guides by Jisc</a></li> </ul> </div> </div> <div class="col span-4"> <div class="linklist l-gutter--right"> <div class="linklist__title">Contact</div> <a href="mailto:help@jisc.ac.uk">help@jisc.ac.uk</a> </div> </div> <div class="col span-4"> <div class="linklist l-gutter--right"> <div class="linklist__title">Accessibility</div> <a href="/opendoar/accessibility.html">Accessibility Statement</a> </div> </div> </div> </div> <!--.medium here denotes depth of bg tint--> <div class="inner l-pull-left medium bottom-section"> <div class="l-centre-offset row"> <div class="col span-12"> <div class="l-gutter--right"> <div class="divisional-info"> <div class="divisional-info__side"> <a href="https://jisc.ac.uk"> <img alt="Jisc logo" src="/ux.jisc.2.0.0/jisc-logo.png" width="158" height="93" /> </a> </div> <div class="divisional-info__body"> <div class="linklist__title">Open research</div> <p>Removing barriers, embedding open practices and developing open infrastructure.</p> <p><a href="https://www.jisc.ac.uk/open-research">Find out more at jisc.ac.uk/open-research</a></p> </div> </div> </div> </div> </div> </div> <!-- .heavy here denotes depth of bg tint --> <div class="inner l-pull-left heavy"> <div class="l-centre-offset row cc-wrap"> <div class="cc media-object"> <div class="media-object__media"> <a rel="license" href="http://creativecommons.org/licenses/by-nc-nd/4.0/"> <img src="/img/by-nc-nd.png" alt="License" /> </a> </div> <div class="media-object__body"> <!-- @CHANGE Add the following print version of the copyright notice. Should always display current year --> <span class="print-only">©2017 Jisc.</span> This work is licensed under the <a class="cc__link" rel="license" href="http://creativecommons.org/licenses/by-nc-nd/4.0/">CC BY-NC-ND 4.0</a><br /> <span class="cc"><a class="cc__link" id="about-our-content" href="https://www.jisc.ac.uk/website/copyright?loc=cc">About using our content</a></span> </div> </div> </div> </div> </footer> <script src="/ux.jisc.2.0.0/js/ux.jisc-2.0.0.script-foot.min.js">// <!-- No script --></script> <script src="/javascript/JavaScript-autoComplete-master/auto-complete.min.js">// <!-- No script --></script> <script>jQuery.noConflict()</script> <script src="/javascript/select_tab.js">// <!-- No script --></script> <script src="/javascript/search_field_autocomplete.js">// <!-- No script --></script> </body> </html>

Pages: 1 2 3 4 5 6 7 8 9 10