Accessibility report for repo

This report is based on a default publication flavour installation of EPrints 3.4 using the data imported by the testdata/bin/import_test_data script. Any rebranding to EPrints or significant customisation is liable to significantly alter the results show below.

Table of Contents

• Introduction
• Test Results
  • Public-facing Pages
  • Non-public Administation Pages
  • Miscellaneous Page
• Summary

Introduction

This report is intended to present the results of the testing of repo to assess its accessibility compliance. This has been undertaken with the use of the Chrome Extension of the WAVE web accessibilty evaluation tool. To emulate user-generated content EPrints' testdata/bin/import_test_data script has been used to import 100 publications to populate various pages under test. In addition to this one empty (unedited) publication was added and a Saved Search for "Habits" was created.

Where there are known issues, the comments section should describe the reasons and where appropriate how these issues are likely be addressed. For more details on planned future accessiibility improvements, please see our accessibility roadmap.

Test Results

Test last run on 18 April 2021

Public-facing Pages

Non-public Administration Pages

Miscellaneous Pages

Summary

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:

1. Links to PDF documents.
2. Duplications in the test or third-party data leading to alerts about shared alternative texts for nearby images.
3. Reports of suspicious link texts that are not considered suspicious within the context of where they appear.
4. Apparent missing table captions due to a feature in EPrints to make clear a table has no items rather than leaving the table empty.

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.

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.