Ubaya Repository is run by ["organisation_name" not defined]. We want as many people as possible to be able to use Ubaya Repository. 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.
We know some parts of Ubaya Repository are not fully accessible:
If you need information on Ubaya Repository 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.
We are always looking to improve the accessibility of Ubaya Repository. If you find any problems not listed on this page or think we are not meeting accessibility requirements, please contact us.
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).
["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.
Ubaya Repository is not compliant with the Web Content Accessibility Guidelines version 2.1 AA standard. The non-accessible sections are listed below.
The content listed below is non-accessible for the following reasons.
We are always looking to improve the accessibility of Ubaya Repository. If you find any problems not listed on this page or think we are not meeting accessibility requirements, contact by email: pustaka@unit.ubaya.ac.id.
We are yet to compile a list of where and how Ubaya Repository is non-compliant with accessibility regulations.
We are yet to compile a list of problems with fixing them would be a disproportionate burden.
As Ubaya Repository 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 Ubaya Repository'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. Ubaya Repository 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: pustaka@unit.ubaya.ac.id.
Areas of Ubaya Repository 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:
Ubaya Repository was last comprehensively tested on 4 June 2020. You can read the comprehensive report.
Based on testing a default publication flavour installation of EPrints using standard test data, all tested public-facing pages currently report no errors, contrast errors or alerts except where this is essential for the functioning of EPrints as on Open Access repository (i.e. links to PDF documents) or due to duplications in the test data leading to alerts about shared alternative texts for nearby images. It should be noted that although Chromium's WAVE extension does not report any contrast errors for public-facing pages Firefox's does but the former was used for testing. Firefox's contrast errors are due to its default settings for the background colour of select boxes.
Many non-public administration pages do have significant numbers of errors or alerts. This will be addressed by the release of EPrints 3.4.3 if not EPrints 3.4.2. Typically where very large number of errors or alerts exist on a page, the majority are the same issue generated by a programmatic layout of information, (e.g. if one search result has an issue, the remainder of search results on that page are likely to have the same issue). This means it is likely only a small number of changes should be necessary to eliminate a significant number of these issues.
Miscellaneous pages like those for OAI metadata harvesting have been tested and found to have issues but are being considered low priority, as they are not generally intended for human use.
Our accessibility roadmap shows how and when we plan to improve accessibility on Ubaya Repository.
This statement was first prepared on 2 December 2019. It was last updated on 20 December 2019.
