CINXE.COM

<!DOCTYPE html> <html xmlns="http://www.w3.org/1999/xhtml"> <head> <meta http-equiv="X-UA-Compatible" content="IE=edge" /> <title>Accessibility - ROARMAP</title> <link rel="icon" href="/favicon.ico" type="image/x-icon" /> <link rel="shortcut icon" href="/favicon.ico" type="image/x-icon" /> <link rel="Top" href="https://roarmap.eprints.org/" /> <link rel="Sword" href="https://roarmap.eprints.org/sword-app/servicedocument" /> <link rel="SwordDeposit" href="https://roarmap.eprints.org/id/contents" /> <link rel="Search" href="https://roarmap.eprints.org/cgi/search" type="text/html" /> <link rel="Search" href="https://roarmap.eprints.org/cgi/opensearchdescription" title="ROARMAP" type="application/opensearchdescription+xml" /> <script type="text/javascript"> // <![CDATA[ var eprints_http_root = "https://roarmap.eprints.org"; var eprints_http_cgiroot = "https://roarmap.eprints.org/cgi"; var eprints_oai_archive_id = "roarmap.eprints.org"; 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" href="/style/auto-3.4.5.css?1730989155" type="text/css" /> <script src="/javascript/auto-3.4.5.js?1730989155" type="text/javascript"> //padder </script>  <meta content="EPrints 3.4.5" name="Generator" /> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /> <meta http-equiv="Content-Language" content="en" /> </head> <body> <div class="ep_tm_header ep_noprint"> <div class="ep_tm_site_logo"> <a href="https://roarmap.eprints.org/" class="ep_tm_archivetitle" title="ROARMAP"> <img alt="ROARMAP" src="/images/ROARMAP_logo.png" /> </a> </div> <ul class="ep_tm_menu"> <li> <a href="https://roarmap.eprints.org"> Home </a> </li> <li> <a href="https://roarmap.eprints.org/information.html"> About </a> </li> <li> <a href="https://roarmap.eprints.org/view/country/un=5Fgeoscheme.html" menu="ep_tm_menu_browse"> Browse </a> </li> <li> <a href="https://roarmap.eprints.org/help.html"> Help </a> </li> <li> <a href="https://roarmap.eprints.org/dataviz.html"> Data Visualisations </a> </li> </ul> <table class="ep_tm_searchbar"> <tr> <td align="left"> <ul id="ep_tm_menu_tools" class="ep_tm_key_tools" role="toolbar"><li class="ep_tm_key_tools_item"><a href="/cgi/users/home" class="ep_tm_key_tools_item_link">Login</a></li><li class="ep_tm_key_tools_item"><a href="/cgi/register" class="ep_tm_key_tools_item_link">Create Account</a></li></ul> </td> <td align="right" style="white-space: nowrap"> <form method="get" accept-charset="utf-8" action="https://roarmap.eprints.org/cgi/search" style="display:inline"> <input class="ep_tm_searchbarbox" size="20" type="text" name="q" /> <input class="ep_tm_searchbarbutton" value="Search" type="submit" name="_action_search" /> <input type="hidden" name="_action_search" value="Search" /> <input type="hidden" name="_order" value="bytitle" /> <input type="hidden" name="basic_srchtype" value="ALL" /> <input type="hidden" name="_satisfyall" value="ALL" /> </form> </td> </tr> </table> </div> <div> <div class="ep_tm_page_content"> <h1 class="ep_tm_pagetitle"> Accessibility </h1> <div class="ep_msg_message"> <div class="ep_msg_message_content"> <div class="ep_msg_message_icon" style="width: 32px;"> <img alt="Message" src="/style/images/message.png" /> </div> <div class="ep_msg_message_text">This page is intended as a generic accessibility statement for EPrints and should be amended as required before deployment of your EPrints repository. In particular the <code>organisation_name</code> phrase may need to be set if upgrading to EPrints 3.4.2+.</div> </div> </div> <h2>Table of Contents</h2> <ul> <li><a href="#accessibility-statement-for-website-name">Accessibility statement for ROARMAP</a> <ul> <li><a href="#how-accessible-website-is">How accessible ROARMAP is</a></li> <li><a href="#what-to-do-if-you-cannot-access-parts-of-this-website">What to do if you cannot access parts of ROARMAP</a></li> <li><a href="#reporting-accessibility-problems-with-this-website">Reporting accessibility problems with ROARMAP</a></li> <li><a href="#enforcement-procedure">Enforcement procedure</a></li> </ul> </li> <li><a href="#technical-information-about-this-websites-accessibility">Technical information about ROARMAP's accessibility</a></li> <li><a href="#non-accessible-content">Non accessible content</a> <ul> <li><a href="#non-compliance-with-the-accessibility-regulations">Non compliance with the accessibility regulations</a></li> <li><a href="#disproportionate-burden">Disproportionate burden</a></li> <li><a href="#content-that-is-not-within-the-scope-of-the-accessibility-regulations">Content that is not within the scope of the accessibility regulations</a></li> </ul> </li> <li><a href="#how-we-tested-this-website">How we tested ROARMAP</a></li> <li><a href="what-were-doing-to-improve-accessibility">What we鈥檙e doing to improve accessibility</a></li> </ul> <h2 id="accessibility-statement-for-website-name">Accessibility statement for ROARMAP</h2> <p>ROARMAP is run by University of Southampton. We want as many people as possible to be able to use ROARMAP. For example, that means you should be able to:</p> <ul> <li>change colours, contrast levels and fonts</li> <li>zoom in up to 300% without the text spilling off the screen</li> <li>navigate most of the website using just a keyboard</li> <li>navigate most of the website using speech recognition software</li> <li>listen to most of the website using a screen reader (including the most recent versions of JAWS, NVDA and VoiceOver)</li> </ul> <p>We have also made the website text as simple as possible to understand.</p> <p><a rel="external" href="https://mcmw.abilitynet.org.uk/">AbilityNet</a> has advice on making your device easier to use if you have a disability.</p> <h3 id="how-accessible-website-is">How accessible ROARMAP is</h3> <p>We know some parts of ROARMAP are not fully accessible:</p> <ul> <li>most older PDF documents are not fully accessible to screen reader software</li>  </ul> <p>Using the WAVE Accessbility checker tool we are also aware of alerts that it raises which cannot be resolved:</p> <ul> <li>empty listing of items displays "No Items" in the middle of the table that WAVE thinks should be a table caption. This is not appropriate and displaying a row with the text "No Otems" makes it clear there are no items whereas no rows at all might make it look as though something has broken.</li> </ul> <h3 id="what-to-do-if-you-cannot-access-parts-of-this-website">What to do if you cannot access parts of ROARMAP</h3> <p>If you need information on ROARMAP in a different formats please contact our <a href="mailto:info@services.eprints.org">repository administrators</a>. We will consider your request and will aim to get back to you within 7 working days.</p> <h3 id="reporting-accessibility-problems-with-this-website">Reporting accessibility problems with ROARMAP</h3> <p>We are always looking to improve the accessibility of ROARMAP. If you find any problems not listed on this page or think we are not meeting accessibility requirements, please <a href="/contact.html">contact us</a>.</p> <h3 id="enforcement-procedure">Enforcement procedure</h3> <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'). If you鈥檙e not happy with how we respond to your complaint, <a rel="external" href="https://www.equalityadvisoryservice.com/">contact the Equality Advisory and Support Service (EASS)</a>.</p> <h2 id="technical-information-about-this-websites-accessibility">Technical information about ROARMAP's accessibility</h2> <p>University of Southampton is committed to making its website accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.</p>  <p>ROARMAP is not compliant with the <a rel="external" href="https://www.w3.org/TR/WCAG21/">Web Content Accessibility Guidelines version 2.1</a> AA standard. The non-accessible sections are listed below.</p> <h2 id="non-accessible-content">Non accessible content</h2> <p>The content listed below is non-accessible for the following reasons.</p> <p>We are always looking to improve the accessibility of ROARMAP. If you find any problems not listed on this page or think we are not meeting accessibility requirements, contact by email: <a href="mailto:info@services.eprints.org">info@services.eprints.org</a>.</p> <h3 id="non-compliance-with-the-accessibility-regulations">Non compliance with the accessibility regulations</h3> <p>We are yet to compile a list of where and how ROARMAP is non-compliant with accessibility regulations.</p>  <h3 id="disproportionate-burden">Disproportionate burden</h3> <p>We are yet to compile a list of problems with fixing them would be a disproportionate burden.</p>  <h3 id="content-that-is-not-within-the-scope-of-the-accessibility-regulations">Content that is not within the scope of the accessibility regulations</h3>  <h4 id="pdfs-and-other-documents">PDFs and other documents</h4> <p>As ROARMAP is an open access research repository, the principal content made available to users are research outputs such as articles, papers, posters and reports, many of which are PDF documents. Many PDF documents, especially older ones, are not fully accessible to screen reader software and do not contain other common accessibility features. In particular:</p> <ul> <li>many documents, especially older ones, do not conform to the PDF/A archiving format.</li> <li>many lack bookmarks or document titles, therefore failing to meet WCAG 2.1 success criteria 2.4.5 and 2.4.2.</li> <li>many discuss scientific or scholarly concepts which may be abbreviated with no mechanism for discovering the meaning of the abbreviations, or unusual words arising from scholarly discourse without definitions. These issues each fail WCAG 2.1 criteria 3.1.4 and 3.1.1 respectively.</li> <li>there may be some documents that fail to specify their human language, thereby failing WCAG 2.1 success criterion 3.1.1.</li> <li>many documents may not reflow satisfactorily. This fails WCAG 2.1 success criterion 1.4.10.</li> </ul> <p>The accessibility regulations <a rel="external" href="http://www.legislation.gov.uk/uksi/2018/952/regulation/4/made">do not require us to fix PDFs or other documents placed in ROARMAP's archive before 23 September 2019</a> as these items are considered "archives".</p> <p>PDFs and other documents added after 23 September 2019 may be user provided and therefore not fully accessible. ROARMAP has a review process that should identify these before they are made available for download. If this is not the case please contact by email: <a href="mailto:info@services.eprints.org">info@services.eprints.org</a>.</p> <h4 id="general-issues">General issues</h4> <p>Areas of ROARMAP which are not document-based demonstrate good levels of accessibility. However, the following issues have been identified and are in the process of being addressed:</p> <ul> <li>Headings on some of our pages do not appear in a logical order. This does not meet WCAG 2.1 success criterion 2.4.10.</li> <li>Some of the forms and interactive search pages on ROARMAP are not appropriately labelled or do not have labels. This does not meet WCAG 2.1 success criterion 3.3.2.</li> <li>Interactive elements of ROARMAP (such as search) do not utilise status messages to update screen readers of a change in state. This does not meet WCAG 2.1 success criterion 3.2.2.</li> </ul>  <h2 id="how-we-tested-this-website">How we tested ROARMAP</h2> <p>ROARMAP was last comprehensively tested on <b>19 May 2023</b>. You can read the <a href="report.html">comprehensive report</a>.</p> <p>Based on testing a default publication flavour installation of EPrints using standard test data, all tested public-facing and back-end administration pages currently report no errors or contrast errors. These pages may have one or more alerts. If so, these alerts are considered acceptable and/or essential for the functioning of EPrints as an Open Access repository and will fall into one of the following categories:</p> <ol> <li>Links to PDF documents.</li> <li>Duplications in the test or third-party data leading to alerts about shared alternative texts for nearby images.</li> <li>Reports of suspicious link texts that are not considered suspicious within the context of where they appear.</li> <li>Apparent missing table captions due to a feature in EPrints to make clear a table has no items rather than leaving the table empty.</li> </ol> <p>It should be noted that whilst Chromium's WAVE extension that was used for testing. It did not report any contrast errors for any of the tested public-facing and back-end administration pages. However, Firefox's WAVE extension has been seen to report some contrast errors. Firefox's contrast errors are due to its default setting for the background colour of select form elements.</p> <p>Miscellaneous pages like those for OAI metadata harvesting have been tested and found to have issues with tables being reported as being used for layout when they are genuinely being used as tables. However, as these pages are not intended for general human use, there is no intention to further address these issues.</p>  <h2 id="what-were-doing-to-improve-accessibility">What we鈥檙e doing to improve accessibility</h2> <p>Our <a href="roadmap.html">accessibility roadmap</a> shows how and when we plan to improve accessibility on ROARMAP.</p> <p><em>This statement was first prepared on <b>2 December 2019</b>. It was last updated on <b>7 August 2020</b>.</em></p> </div> </div> <div class="ep_tm_footer ep_noprint"> <div class="ep_tm_eprints_logo"> <a href="http://eprints.org/software/"> <img alt="EPrints Logo" src="/images/eprintslogo.png" /> </a> </div> <span>ROARMAP is powered by <em><a href="http://eprints.org/software/">EPrints 3.4</a></em> which is developed by the <a href="https://www.ecs.soton.ac.uk/">School of Electronics and Computer Science</a> at the University of Southampton. <a href="/eprints/">About EPrints</a> | <a href="/accessibility/">Accessibility</a></span> </div> </body> </html>