Skip to main content
Ex Libris Knowledge Center

360 Core Accessibility Statement

All researchers, regardless of ability, need access to scholarly information. ProQuest and Ex Libris are 
committed to providing all our users with a fully accessible experience for research, teaching and 

At ProQuest and Ex Libris, we make every effort to ensure that our platforms – including 360 Core – can 
be used by everyone. 360 Core is continually designed and developed to meet Level AA of the W3C Web 
Content Accessibility Guidelines (WCAG 2.1) and Section 508 of the US Rehabilitation Act for features 
and functions.

The following sections of 360 Core have been evaluated as part of this statement:

  • Management Tools

  • Overlap Analysis

  • Management Reports

Accessibility Features and Gaps

Users of 360 Core should be able to:

  • Navigate most of the website using just a keyboard.

  • Listen to most of the website using a screen reader.

  • View text at sufficient levels of color contrast.

  • Zoom in up to 200% using browser tools without loss of content or functionality.

There may be some parts of this website that are not fully accessible:

  • Some visual headings are note coded as headings.

  • There are no skip links for bypassing repetitive navigation.

  • Page titles are not sufficiently descriptive.

  • The website is not responsive to different screen and device sizes.

  • Status messages on the page are not communicated to screen readers.

If you have a disability and need to make your computer, tablet or other device easier to use, AbilityNet is a recommended resource. We also recommend browsing free add-ons offered for Google Chrome and Mozilla Firefox.

Technical Information about This Site’s Accessibility

360 Core is committed to making its website accessible, in accordance with:

  • Level A and Level AA of the W3C Web Content Accessibility Guidelines (WCAG 2.1)

  • Section 508 of the US Rehabilitation Act for features and functions.

  • The Americans with Disabilities Act (ADA)

  • Public Sector Bodies (Websites and Mobile Applications) (No.2) Accessibility Regulations 2018.

Compliance Level and Report

This website is partially compliant with the Web Content Accessibility Guidelines v2.1 AA standard, due 
to the non-compliances listed below.

To access the full report for 360 Core, see Accessibility Compliance Report (VPAT 2.4 and WCAG 2.1).

Accessibility of This Platform

While much of 360 Core is accessible with assistive technologies, we realize there are several significant 
gaps noted in this document. The 360 Core team is currently working on several accessibility-related 
enhancements that will be published in the second quarter of 2021.

Screen Reader Navigation

Most of 360 Core is navigable and readable with a screen reader. There are many tables throughout the 
application, and you should be able to easily navigate table cells using the arrow keys. Row and column 
headings will be read to you as you navigate.

There are some areas that might cause difficulty while you use the site with a screen reader. Page titles 
are sometimes not sufficiently descriptive and while visual headings are used throughout the interface, 
they are not coded as headings for assistive technology. This may make it difficult while using a screen 
reader to determine which page you’re on. To help understand where you are within the site, there is a 
breadcrumb trail on every page besides the homepage which indicates the current page. This is located 
directly after the header and specifically after the search button.


Most form elements in 360 Core have visual labels, but these labels are not consistently identified as 
labels in code. To help identify the purpose of form controls without programmatically assigned labels, 
refer to the text labels that appear consistently before their corresponding controls.

Status Messages

At this time, when operations or actions on table elements are performed, status messages are not 
presented to confirm the successful completion of the operation, either visually or to assistive 

Keyboard Navigation

360 Core is almost entirely navigable with just a keyboard. The one exception is the Default Status List 
widget, which requires reordering items using a drag and drop mouse operation.

Accessibility Testing

360 Core code is checked for accessibility using a range of automated and manual checks including but 
not limited to: 

  • Color Contrast Analyzer provided by WebAIM

  • Deque aXe accessibility testing tool

  • High Contrast Chrome extension

  • Keyboard-access manual testing and assessment

  • WAVE (Web Accessibility Evaluation tool) provided by WebAIM

  • NVDA for Windows

What We’re Doing to Improve Accessibility

Making content accessible is an ongoing effort at ProQuest. We’re committed to working with the 
community to ensure we continue to meet our customers’ needs. A list of our ongoing efforts include:

  • The ProQuest Accessibility Council: a team of stakeholders working to increase accessibility resources and capabilities.

  • Pursuing partnerships with colleges, universities and other institutions to assist us in reviewing and updating our accessibility standards.

  • Supporting certifications for our employees.

  • Consulting with accessibility experts such as Deque.

Support and Feedback

If you have difficulty accessing specific ProQuest content or features with adaptive technology after trying the workarounds suggested in this statement, you can contact us using the links provided below. Our support services will respond within three days and are available to accommodate the communication needs of end users with disabilities. We will work with you to identify the best option for remediation, subject to content licensing restrictions and technical capability. 

Current customers: submit questions or issues by opening a case using the Support Portal.


Preparation of This Accessibility Statement

This accessibility statement was prepared on February 25, 2021. It was last updated on March 27, 

The website was last tested on December 6, 2022. This test was carried out internally at ProQuest.

  • Was this article helpful?