Accessibility

Message
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 organisation_name phrase may need to be set if upgrading to EPrints 3.4.2+.

Table of Contents

Accessibility statement for Repository UHAMKA

Repository UHAMKA is run by ["organisation_name" not defined]. We want as many people as possible to be able to use Repository UHAMKA. For example, that means you should be able to:

We have also made the website text as simple as possible to understand.

AbilityNet has advice on making your device easier to use if you have a disability.

How accessible Repository UHAMKA is

We know some parts of Repository UHAMKA are not fully accessible:

Using the WAVE Accessbility checker tool we are also aware of alerts that it raises which cannot be resolved:

What to do if you cannot access parts of Repository UHAMKA

If you need information on Repository UHAMKA in a different formats please contact our repository administrators. We will consider your request and will aim to get back to you within 7 working days.

Reporting accessibility problems with Repository UHAMKA

We are always looking to improve the accessibility of Repository UHAMKA. If you find any problems not listed on this page or think we are not meeting accessibility requirements, please contact us.

Enforcement procedure

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’re not happy with how we respond to your complaint, contact the Equality Advisory and Support Service (EASS).

Technical information about Repository UHAMKA's accessibility

["organisation_name" not defined] is committed to making its website accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.

Repository UHAMKA is not compliant with the Web Content Accessibility Guidelines version 2.1 AA standard. The non-accessible sections are listed below.

Non accessible content

The content listed below is non-accessible for the following reasons.

We are always looking to improve the accessibility of Repository UHAMKA. If you find any problems not listed on this page or think we are not meeting accessibility requirements, contact by email: ict@uhamka.ac.id.

Non compliance with the accessibility regulations

We are yet to compile a list of where and how Repository UHAMKA is non-compliant with accessibility regulations.

Disproportionate burden

We are yet to compile a list of problems with fixing them would be a disproportionate burden.

Content that is not within the scope of the accessibility regulations

PDFs and other documents

As Repository UHAMKA 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:

The accessibility regulations do not require us to fix PDFs or other documents placed in Repository UHAMKA's archive before 23 September 2019 as these items are considered "archives".

PDFs and other documents added after 23 September 2019 may be user provided and therefore not fully accessible. Repository UHAMKA 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: ict@uhamka.ac.id.

General issues

Areas of Repository UHAMKA 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:

How we tested Repository UHAMKA

Repository UHAMKA was last comprehensively tested on 18 April 2021. You can read the comprehensive report.

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.

What we’re doing to improve accessibility

Our accessibility roadmap shows how and when we plan to improve accessibility on Repository UHAMKA.

This statement was first prepared on 2 December 2019. It was last updated on 7 August 2020.