Application accessibility statement inline with Public Sector Body (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018

This accessibility statement applies to the Entitlement Registry service accessible https://entitlements.edina.ac.uk/

This website is run by EDINA, for the University of Edinburgh. Our aim is for as many people as possible to be able to use this website. That means you should be able to:

  • zoom in up to 200% without the text spilling off the screen,
  • navigate most of the website using just a keyboard,
  • navigate most of the website using speech recognition software,
  • listen to most of the website using a screen reader (including the most recent versions of JAWS, NVDA and VoiceOver),
  • access and use the application without any time limits,
  • using your browser settings, change colours, contrast levels and fonts.

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

Customising the application

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

AbilityNet - My Computer My Way

With a few simple steps you can customise the appearance of our website to make it easier to read and navigate.

Additional information on how to customise our website appearance

How accessible this application is

We know some parts of this website are not fully accessible:

  • Some parts may contain specialist words: notable the names of journals and of publishers,
  • Non text content whos purpose is decorative does not have a text alternative, however also use aria to hide from screen readers,
  • Semantically meaninfull content is sometimes provided in a pop-up,
  • Not all colour contrasts meet the recommended Web Content Accessibility Guidelines 2.1 AA standard.

Feedback and contact information

If you need information on this website in a different format such as an accessible PDF, large print, easy read, audio recording or braille:

  • email edina@ed.ac.uk, or
  • call 0131 650 3302, or
  • British Sign Language (BSL) users can contact us via contactSCOTLAND-BSL, the on-line BSL interpreting service.

We will consider your request and get back to you within 5 working days.

Reporting accessibility problems with this application

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

  • email edina@ed.ac.uk, or
  • call 0131 650 3302, or
  • British Sign Language (BSL) users can contact us via contactSCOTLAND-BSL, the on-line BSL interpreting service.

We will consider your request and get back to you within 5 working days.

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

Contact details for the Equality Advisory and Support Service (EASS)

The UK government has produced information on how to report accessibility issues: Reporting an accessibility problem on a public sector website

Contacting us by phone using British Sign Language

British Sign Language service

contactSCOTLAND-BSL runs a service for British Sign Language users and all of Scotland’s public bodies using video relay. This enables sign language users to contact public bodies and vice versa. The service operates 24 hours a day, 7 days a week.

contactSCOTLAND-BSL service details

Technical information about this website’s accessibility

EDINA is committed to making its Entitlement Registry website 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 2.1 AA standard, owing to the non-compliances listed below.

The full guidelines are available at:

Web Content Accessibility Guidelines (WCAG) 2.1 AA standard

Non accessible content

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

Noncompliance with the accessibility regulations

The following items to not comply with the WCAG 2.1 AA success criteria:

  • 1.1.1 Non Text Content
    • Images that are decorative, without semantic meaning, have no alt text (they are also hidden from screen-readers),
  • 1.3.2 Meaningful Sequence
    • The "popups" for the notes of an entitlement are not in page order, nor are they programmatically determinable (there's no attribute to indicate new content has been made available, or where it is),
    • There is also an accessibility failure in that this pop-up is not beside it's trigger, so some assistive technologies will not show the new content,
  • 1.3.5 Identify Input Purpose
    • Most inputs do not have auto-complete function,
  • 1.3.6 Identify Purpose
    • We cannot guarentee that all landmarks and regions are semantically marked, or given aria labels,
  • 1.4.3 Contrast (Minimum)
    • We know that our contrast minimums are low - particularly within tables,
  • 1.4.12 Text Spacing
    • We cannot guarentee that content or functionality is not lost if a user overrides text-sizes,
  • 1.4.13 Content on Hover or Focus
    • Whilst we have generally tried to dispense with "tooltips", there are instances where such popups are used (primarily in the "resource description" page), they cannot be dismissed with a keystroke,
  • 2.2.1 Timing Adjustable
    • There is a built-in time-limit for the session, however that is measured in hours,
  • 2.4.4 Link Purpose (In Context)
    • Not all links have an obvious purpose based in their text alone. For example, Titles (of journals or publishers) are used to link to details of that item,
  • 2.4.5 Multiple Ways
    • There is no site map or search function available,
  • 3.1.6 Pronunciation
    • Pronouniation of nouns (particulartly the titles of journals and publishers) is not provided,
  • 3.3.1 Error Identification
    • We do not guarentee that all errors are clearly identifyable, intuitive, or provide access to the problem element,
  • 3.3.3 Error Suggestion
    • Not all errors detected by the ingest process provide suggestions for fixing the input,
  • 3.3.4 Error Prevention (Legal, Financial, Data)
    • If a document of entitlements is withdrawn (by a user) then all entitlements listed in that document are deleted. This cannot be "un-deleted" - however a replacement document can be uploaded,
  • 4.1.3 Status Messages
    • Important status messages are not annouced to screen readers / accessibility tools.

Unless specified otherwise, a complete solution, or significant improvement, will be in place for those items within our control by December 2022

Disproportionate burden

We specifically identify two areas that we believe to be a disproportionate burden to resolve, in the context of this specific service:

  • "Un-deleting" withdrawn data requires changes in the design of the service code, and a work-around is given

Otherwise, we are not currently claiming that any accessibility problems would be a disproportionate burden to fix.

Content that’s not within the scope of the accessibility regulations

At this time, we do not believe that any content is outside the scope of the accessibility regulations.

What we’re doing to improve accessibility

The development team will constantly review and, where possible, improve accessibility for this service. We will continue to address the accessibility issues highlighted, working to deliver a solution or suitable workaround for users to use the service.

Due to the potential for complex information to be displayed on the Entitlement Registry, it may not be possible to resolve all accessibility issues. However, while we are in the process of resolving these accessibility issues, or where we are unable, we will ensure reasonable adjustments are in place to make sure no user is disadvantaged. As changes are made, we will continue to review accessibility and retest the accessibility across this service.

Preparation of this accessibility statement

This statement was prepared on 22nd July 2021.

Testing

This service was last tested by the service development team within the Information Services Group directorate in July 2021. The test was carried out primarily using a combination of Firefox and Google Chrome browsers alongside MacOS Safari and Microsoft Edge for comparative purposes, including screen reader compatibility. In particular, the service was primarily tested using Chrome since it is by far the most popular browser when using a screen reader. Current world-wide usage levels for different screen readers and browsers can be found in the 2021 WebAIM annual survey.

Automated testing

A representitive selection of pages were chosen, and tested with a range of tools:

  • IBM Equal Access Accessibility Checker reports on the percentage of elements with no violations,
  • deque's axe Tools is a development and testing toolkit,
  • Lighthouse is an accessibility checker from Google, based on the axe toolkit,
  • wave is both a browser extension toolkit and an external harvestger toolkit from WebAIM,
  • HeadingsMap is a chrome/firefox extension that displays the sequence of headings.

We recognise the limitations of automated testing and we supplemented this with manual testing

Manual Testing

The service was browsed from a linux desktop (chrome and firefox); a text-only browser (lynx, on linux); and windows (chrome and edge)

When using the Microsoft Edge web browser with its native Read Aloud function, running the latest version of Windows (as of July 22nd 2021), all items were read aloud as expected.

Content across the Entitlement Registry has been tested without a mouse through keyboard navigation and has been found to be accessible for end users and/or administrators through a keyboard interface. To navigate service website sections, the arrow keys may be used. To navigate service website menus, the tab key can be used.

Test data was uploaded, with both good and bad data, and the service responded as expected.

We also tested:

  • Spellcheck functionality
  • Scaling using different resolutions from –25% to +400%
  • Options to customise the interface (magnification, font, background colour et. cetera)
  • Notice of links to new window or tab when navigating the service
  • Information conveyed in colour or sound only
  • Flashing or scrolling text
  • Time limits