Skip to main content
ExLibris

Knowledge Assistant

BETA
 
  • Subscribe by RSS
  • Back
    Primo
    Ex Libris Knowledge Center
    1. Search site
      Go back to previous article
      1. Sign in
        • Sign in
        • Forgot password
    1. Home
    2. Primo
    3. Product Documentation
    4. Primo VE
    5. Primo VE (English)
    6. Primo VE User Interface
    7. Accessibility in NDE Customization

    Accessibility in NDE Customization

    1. Last updated
    2. Save as PDF
    3. Share
      1. Share
      2. Tweet
      3. Share
    1. Accessibility in NDE Customization
    2. Accessibility Considerations
      1. Homepage Design and Logo
        1. Homepage Elements Boxes
        2. Library Logo and Images
        3. Adding Images
      2. Customizing Background Images
      3. Customize a Color Theme
      4. Maintain Sufficient Contrast
      5. Font Weight and Size
    3. Customizing Visible Labels
      1. Changing Label Names
      2. Search Filter Names
      3. Removing Customizations to Test Accessibility
      4. Adding Chat or Other Custom Elements
    4. General Information and Resources
    Translatable

    Accessibility in NDE Customization

    Libraries and universities can customize the NDE UI to tailor it to their institutional and user needs. The purpose of this article is to provide recommendations on common accessibility considerations that should be maintained during customization.

    The base UI has been designed to accommodate accessibility prior to configuration. Refer to the Primo Accessibility Statement for more information on accessibility features and gaps in the NDE UI. Some steps are required during configuration to ensure accessibility is maintained.

    These recommendations will continue to be developed and refined with additional examples and best practices. If you have recommendations for material to include, send an email to accessibility@clarivate.com.

    Accessibility Considerations

    Homepage Design and Logo

    The primary Home Screen can be customized using your custom HTML. The May 2026 release has planned future configuration options for the Homepage (CERV #28360). More details will be available on the 2026 roadmap.

    Homepage Elements Boxes

    A clean webpage interface displays five rounded menu icons in a horizontal row, each with a symbol and label: “Opening hours,” “FAQ,” “Ask a librarian,” “Search tips,” and “Study room.” Each icon features a soft purple background and centered layout. Below, browser developer tools show HTML code highlighting a div with anchor tags and icons, and CSS styles defining padding, border-radius, and background color for the menu items.

    Homepage Elements

    Ensure that the homepage element boxes have appropriate aria-label attributes, correct href values, and accurate visible labels.

    Library Logo and Images

    Clarivate provides a generic alt-text. The library should update the alt-text provided for the primary library logo.

    <img alt="Library Logo" height="35" class="black-background ng-star-inserted" src="assets/images/library-logo.png"> For example, the new alt text would read University of Demo Name logo.

    Screenshot of a webpage and its HTML source code shown side-by-side. On the left, the webpage features a pink background with white text reading "Your Discovery Begins Here" and a navigation bar with options like "RESEARCH ASSISTANT" and "JOURNAL SEARCH." A pop-up titled "On Charisma" displays metadata for an image labeled "Library Logo." On the right, the browser's developer tools highlight the HTML code for the logo image, showing its source URL, alt text, and height attribute. The image provides context for analyzing web accessibility and content structure.

    Library Logo

    Adding Images

    If you add additional images on the home screen or other pages in the application, ensure you provide an adequate text alternative based on the purpose of the image on the page.

    Customizing Background Images

    Header images can be used across various pages (such as the main header on the homepage and the header on the collection page) and have been designed to include an overlay above the image. This ensures that there is sufficient contrast between the text and the background image.

    A webpage header titled “Art Collection_Picasso” with the subtitle “Picasso works” overlays a vibrant cubist painting featuring bold colors like yellow, green, and orange. Below, a browser inspector highlights CSS code for .collection-discovery-header .background-image:after, listing properties such as position: absolute, background-color: var(--sys-shadow), opacity: .5, and z-index: 1, all marked with blue checkmarks.

    Customized Background Images

    If you choose to remove the overlay, ensure you test that sufficient color contrast is maintained.

    A header titled “Art Collection_Picasso” with the subtitle “Picasso works” appears over a vivid cubist painting in bold colors. Below, a search bar and filter options are visible, followed by three Picasso-themed book covers in a horizontal row. On the right, browser developer tools highlight CSS for .collection-discovery-header .background-image:after, showing properties like position: absolute, background-color: var(--sys-shadow), opacity: .5, and z-index: 1, all checked in blue.

    Example of a Background with Overlay Removed

    Customize a Color Theme

    The NDE UI adheres to best practices in base theme design for handling color contrast. All color contrast aspects are managed through the color theme, ensuring compliance with accessibility standards. Any changes to the theme directly impact contrast levels across the interface, ensuring readability and usability for all users.

     Horizontal color selection panel labeled “Color Theme – New UI” displays a row of rectangular color swatches under the text “Choose basic color.” The palette includes a gradient of shades starting from bright blue on the left, moving through navy, teal, green, mustard, orange, red, maroon, magenta, purple, and ending with dark brown and gray on the right. The layout is clean and minimal, with the color options arranged evenly for easy selection.

    Color Theme

    Learn more about how color themes are generated, available, and customizable.

    Maintain Sufficient Contrast

    The NDE UI has been tested and designed to maintain sufficient color contrast in various interactive states, including on hover, on focus, and when active/pressed. Ensure that when customizing, you maintain the color contrast requirements.

    Text vs. Background: Ensure a contrast ratio of at least:

    • At least 4.5:1 for normal text
    • 3:1 for large text (18 pt regular or 14 pt bold)
    • Interactive Components (buttons, icons, form borders, inputs, etc.) — Minimum 3:1 contrast between component and adjacent colors.

    Font Weight and Size

    The NDE UI incorporates practices to ensure good readability. When making customizations, consider using minimum font weights to maintain accessibility.

    • Thin weights (under 300) are avoided for small text
    • Sufficient difference between regular and bold weights
    • Font weight does not go below 300 for any text under 18 px
    • All font weights load properly and have fallbacks
    • We encourage using a minimum font size of 14 px

    Customizing Visible Labels

    To display label codes, add &debugLabels=true to the end of the Primo page URL and press Enter to reload the page. The page displays all the configurable labels, replacing them with their corresponding codes. For additional information, see Configuring Display Labels for Primo VE. ARIA labels can be found by inspecting the element.

    webpage with a bookshelf background displays several interface elements outlined in red, drawing attention to placeholder text scattered across the header, search bar, and navigation areas. These red boxes highlight where labels would normally appear in the design. The browser URL includes &debugLabels=true, indicating the page is in debug mode for label rendering.

    Customized Visible Labels

    Changing Label Names

    When changing visible label names, ensure that the corresponding ARIA label is also changed.

    The aria-label should begin with the visible label. For example, if you change the Go to my library card button, adjust the aria-label to match the visible label text. See Providing Accessible Names and Descriptions | W3C.

    purple button labeled “Go to my library card” appears at the top, followed by a snippet of HTML code. The code shows an anchor tag with attributes like id="myLibraryCard", tabindex="0", aria-label="Go to my library card", and role="link". The inner text of the link matches the button label, confirming accessibility features such as the aria-label for screen readers.

    Home Page Example

    An example form titled “REQUEST” appears on a light background. It contains dropdown fields for Request Type, Pickup Location, and Terms of Use, followed by an input for Pickup Date with a calendar icon and a text box for Comment. At the bottom, a prominent magenta button labeled Send Request is displayed, with a smaller Reset Form link beneath it. The design uses clean lines and muted tones with magenta accents for action elements.

    Request Modal Form Label Example

    Search Filter Names

    Search filters are customized by the library to reflect which collection or location is included in the search scope. When configuring the dropdown options, ensure the search labels (menu options) are clear to users.

    Labels and instructions should:

    • Be clear and informative
    • Include any constraints such as required data formats or ranges if relevant
    • Identify required fields

    The search interface with a white background and purple accents displays a dropdown menu expanded on the left, showing options Everything, Library Catalog, and Articles. Next to it, a search bar contains the term art with a magnifying glass icon for search. The top navigation includes links such as Journal Search, Tags, Library Search, ILL Request, and Fetch Item, along with a More menu. Additional links for Ask Anything and Advanced Search appear to the right of the search bar.

    Search Label Example

    Removing Customizations to Test Accessibility

    To test if an accessibility issue you are experiencing is part of the baseline UI, or if it was introduced by a customization, try removing local customizations by adding &noCustomization=true to the page's URL.

    Adding Chat or Other Custom Elements

    Libraries can add additional third-party components, such as chat features, location maps, or create their own. If adding additional components, these may have a range of accessibility built-in and should be tested independently from the NDE UI.

    General Information and Resources

    • NDE UI Customization - Best Practices
    View article in the Exlibris Knowledge Center
    1. Back to top
      • Primo VE Usability Guidelines and Test Script
      • Configuring Display Languages for Primo VE
    • Was this article helpful?

    Recommended articles

    1. Article type
      Topic
      Content Type
      Documentation
      Language
      English
      Product
      Primo
    2. Tags
      This page has no tags.
    1. © Copyright 2026 Ex Libris Knowledge Center
    2. Powered by CXone Expert ®
    • Term of Use
    • Privacy Policy
    • Contact Us
    2025 Ex Libris. All rights reserved