Primo

Introduction

All library patrons, regardless of ability, need access to scholarly information. Clarivate is committed to providing all our users in academia and government with an accessible experience for research, teaching, and learning.

We make every effort to ensure that our platforms – including the Primo discovery service for libraries – can be used by everyone. Primo is continually designed and developed to meet Level AA of the W3C Web Content Accessibility Guidelines (WCAG 2.2) and Section 508 of the US Rehabilitation Act for features and functions.

Primo NDE transition and purpose of this statement

As indicated in the Primo VE 2025 Release Notes, we have shared the timeline to expect for transition for the Primo VE original UI to the New Discovery Experience (NDE).

As of December 2025 – onward, this Accessibility Statement provides information about the NDE UI. Users should refer to the Accessibility Statement for Original UI document for any questions about the original UI.

2026–2027: Mass Onboarding Phase

Institutions are encouraged to begin planning their transition to the NDE UI. You can utilize all the resources under Go NDE to prepare for your transition.

Check whether the NDE UI Transistion Cohort Program is relevant for you. The NDE UI Transition Cohort Program is a structured 4-week training program designed to guide institutions through the migration from the original Primo VE UI to the new NDE UI. The program takes place twice a year.

January 2028: NDE UI Exclusive

The gradual sunset of the original UI is projected to be completed by January 2028. At that time, the NDE UI will become the only supported UI for Primo VE.

Accessibility features and gaps

Primo NDE users can:

• Navigate most of the website using just a keyboard.
• Go directly to the main content areas on the page using skip links.
• Navigate most of the website using a screen reader.
• Navigate most of the website using speech recognition software.
• Navigate page content using headings.
• Adjust color contrast in browser settings. Primo style guides specify using colors that meet minimum contrast specifications.
• Zoom in up to 200% using browser tools without text spilling off the screen.
• Use most websites with devices of different screen sizes and orientations without losing content or functionality.
• Adjust language.
• Use consistent navigation across the site.

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

• Keyboard focus may be reset when activating elements that prompt a dynamic page load. For example, the navigation menu within Journal Search.
• At magnifications higher than 400% (320px), some content may spill off the screen or overlap.
• In some cases, Primo will not be able to correctly identify the language of text while reading a record’s elements (such as title, abstract, and so forth).

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

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

• Level A and Level AA of the W3C Web Content Accessibility Guidelines (WCAG 2.2)
• Section 508 of the US Rehabilitation Act for features and functions
• The Americans with Disabilities Act (ADA)
• EU Directive on the accessibility of the websites and mobile applications of public sector bodies 2016
• UK Public Sector Bodies (Websites and Mobile Applications) (No.2) Accessibility Regulations 2018
• The European Accessibility Act
• EN 301 549 – V3.1.1 – Accessibility requirements for ICT (Information and Communication Technologies) products and services

Compliance level and report

This website partially complies with the Web Content Accessibility Guidelines v2.2 at levels A and AA. For more details, see the full Accessibility Compliance Report for NDE UI (VPAT 2.5 and WCAG 2.2).

As part of our continuous effort to comply with the Web Content Accessibility Guidelines 2.2 (Level A and AA), we have resolved or are planning to resolve issues identified because of customer feedback, internal testing, and external auditing. The status of these issues is listed in the Known Issue Portal.

Clarivate partners with 3^rd party accessibility firm, Deque, to support ongoing validation and re-auditing of pages. Deque will conduct an additional round of review in April 2026. The results of this review will inform the ongoing remediation plan and overall product roadmap. The VPAT will be updated again to reflect the product status at this time, in Spring 2026.

Platform accessibility

The NDE UI integrates some key design changes to improve accessibility from the original UI.

Skip links

Skip Link navigation for accessibility has been expanded to include more areas of the screen, such as the search bar and search-result filters. In addition, in the NDE UI, configuration of the names of Skip Link areas is not required: the names of the regions as they appear in the UI are automatically employed. In the original UI, the names of the areas are configured like labels, in the Aria Labels table. These settings are not used in the NDE UI.

Focus indicators

Throughout the NDE UI, both color and an outline are used to indicate focus.

Known accessibility issues

Accessibility fixes are being implemented by priority level and are released as they are completed. Known issues are scheduled to be resolved in H1 2026. Additional details are provided at Known Issue Portal. An accessibility roadmap will be published in December 2025.

Maintaining accessibility in library customization and configuration

It is important to note that the accessibility of the end user experience is determined, in part, by the customization and configuration introduced by the library or university. For example, the base interface was designed to adhere to color contrast requirements for text and interactive elements. However, a university should ensure that the color contrast is maintained once adjusting to their custom theme or branding.

To help customers, we’re providing ongoing recommendations on how to maintain accessibility in NDE customization and configuration.

Accessibility testing

Primo’s accessibility is a continual effort. Accessibility standards are built into our design and style guides and included as part of our software development and quality assurance pipeline requirements. Primo code is checked for accessibility using a range of automated and manual checks, including but not limited to:

• NVDA, JAWS, VoiceOver
• Keyboard-access manual testing and assessment
• Deque axe accessibility testing tools
• High Contrast Chrome extension

Primo is tested on the latest versions of Firefox, Safari, Chrome, and Edge, and on devices including Mac and Windows computers, and Android and iOS devices.

What we’re doing to improve accessibility

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

• The Clarivate Accessibility Council: a team of stakeholders working to increase accessibility resources and capabilities
• Collaborating with libraries to help make our solutions as accessible as possible.
• Foster an accessibility culture within the business by funding courses and certification for employees e.g. Deque University courses, IAAP (International Association of Accessibility Professionals) CPACC and WAS qualifications.
• Consulting with accessibility experts such as Deque to audit and review our products.
• Accessibility is embedded in our development process. Our acceptance of new features and functionality requires compliance with WCAG 2.2 AA

Support channels and feedback on accessibility issues

We are committed to providing accessible experiences for all users. If you encounter an accessibility issue in Primo VE or wish to learn more about our accessibility efforts, the support channels described below are available.

Reporting a single accessibility issue

We recommend reviewing the Known Issues Portal and VPAT before submitting a case, as your issue may already be identified.

If you are working on the Primo VE Original UI – please refer to the Accessibility Statement for Original UI.

For individual accessibility concerns:

1. In the Clarivate Support Portal, select Submit a Case.
2. Select the Platform / Serviceand the Product.
3. Fill in the rest of the fields, as required. In particular, follow these guidelines:
4. Under Case Type, select Accessibility (Assistive Technology).
5. Under Priority, select the impact level of the issue:
   • High – Blocking issue; task cannot be completed
   • Medium – Task is difficult, but not impossible
   • Low – Minor impact, may still violate WCAG
6. Under Description, please include:
   • A concise summary and steps to reproduce the issue
   • The assistive technology used (e.g., screen reader and version)
   • Any known WCAG 2.2 AA criterion violated
7. Attach screenshots or screen recordings, if available.

Submitting multiple accessibility issues

If you have multiple accessibility issues after conducting audit testing for accessibility, please follow the below steps:

1. Please review the published documentation, Conformance Report linked above, and Known Issues to see if your issue is already on the roadmap to be addressed.
2. Please review our case submission guidelines and note that we cannot respond to issues submitted from an automated scan alone (e.g. Axe DevTools, WAVE, ANDI)
3. Please use the provided template (available August 2026 and onwards) when possible and ensure to provide for each item:
   • Steps to reproduce the issue including location in the application and expected results
   • Severity level based on user impact such as critical, high, medium, or low
   • Screenshot or link to where the issue occurs so that it can be reviewed accurately
4. Send the report findings and any supporting documentation (screenshots, videos) to accessibility@claivate.com.
5. Issues will be reviewed by the accessibility and product teams. Reproduced issues will be added to the product roadmap for remediation and will be published to the Known Issue Portal.

This process ensures accurate triage, faster turnaround, and effective prioritization.

For prospective customers

Prospective customers: contact pq-primo_product_management@clarivate.com

Preparation of this accessibility statement

This accessibility statement was originally prepared in November 2025. It was last updated in July 2026. The application was last audited by 3^rd party vendor, Deque, in June 2026.