Skip to main content
NICE CXone Expert
Expert Success Center

CXone Expert Accessibility Conformance Report - WCAG 2.1 Edition

Voluntary Product Accessibility Template

VPAT® Version 2.4 – Created August 2023

For questions or additional information about this report, contact CXone Expert support at: 

NICE may update this support contact information by posting updated information to the above website or otherwise informing the customer.

Product/Version Product Description
Expert Spring '23

CXone Expert is a Knowledge Management System that allows for the creation, management, extension, and optimization of self-service knowledge to an organization's customers.

The product can be broken up into two portions:

  • public-facing content
  • admin functionality (TBD)

About this VPAT

A VPAT® is an audit of a product's conformance with web accessibility guidelines and best practices to assist buyers and consumers in assessing that product. CXone Expert does not claim to completely meet WCAG 2.1 AA conformance, though we do support or partially support all criteria in the guideline.

For this report, we will only reference the accessibility of the public-facing content portion of the product, which includes anonymous and authenticated viewers (formerly Community members).

Except as may be agreed in a signed agreement, this document is provided for informational purposes only and the contents hereof are subject to change without notice. CXone Expert does not warrant that this document is error free, nor does it provide any other warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or fitness for a particular purpose. CXone Expert specifically disclaims any liability with respect to this document and no contractual obligations are formed either directly or indirectly by this document. CXone Expert further makes no representation concerning the ability of assistive technologies or other products to interoperate with CXone Expert products.

This report supersedes a previous version: VPAT® Version 2.3 – Created May 2019

Evaluation methods used

This product was evaluated using the following methods (links open in a new window):

Applicable guidelines

This report covers the degree of conformance for the following accessibility guideline:

Guideline Included In Report
Web Content Accessibility Guidelines 2.1, at https://www.w3.org/TR/WCAG21
  • Level A (Yes)
  • Level AA (Yes)
  • Level AAA (No )

VPAT organization

The VPAT consists of a three column table.

  1. The first column contains the individual success criteria of WCAG 2.1 guidelines being evaluated.
  2. The second column contains the level of conformance for the success criteria.
  3. The third column contains additional remarks and explanations regarding the level of conformance.

VPAT Conformance Levels

The terms used in the Conformance Level information are defined as follows:

  • Supports: The functionality of the product has at least one method that meets the criterion without known defects or meets with equivalent facilitation.
  • Partially Supports: Some functionality of the product does not meet the criterion.
  • Does Not Support: The majority of product functionality does not meet the criterion.
  • Not Applicable: The criterion is not relevant to the product.

WCAG 2.1 Report

Table 1: Success Criteria, Level A

For Level A conformance (the minimum level of conformance), the webpage satisfies all the Level A Success Criteria, or a conforming alternate version is provided.

Criteria Conformance Level Remarks and Explanations
1.1.1 Non-text Content (Level A) Partially Supports All non-text content has a text alternative in the product except for the following functionality:
  • guide tab scroll buttons do not have text describing their functionality
  • recaptcha form field missing a label
  • classification select options in search results do not have the correct attribute to identify their labels
  • search input on the home page (optional feature) is does not have a legend
Note: Customer has the ability to add custom content that could fail this criteria.
1.2.1 Audio-only and Video-only (Prerecorded) (Level A) Supports The product does not contain pre-recorded audio or video content.

Note: Product offers the ability to embed third-party pre-recorded audio or video content which could cause this criteria to fail.
1.2.2 Captions (Prerecorded) (Level A) Supports The product does not contain prerecorded audio content in synchronized media.

Note: Product offers the ability to embed third-party pre-recorded audio content which could cause this criteria to fail.
1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A) Supports The product does not contain time-based media or audio descriptions of pre-recorded video.

Note: Product offers the ability to embed third-party pre-recorded video content which could cause this criteria to fail.
1.3.1 Info and Relationships (Level A) Partially Supports All information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text except for the following functionality:
  • Home page does not have a default H1 (can be added by customization)
  • Guide tab links use the ARIA role="presentation" on a focusable object that contains content
  • Registration form fields contain duplicate IDs to user sign-in fields located on the same page
  • Recaptcha form field missing a label
  • Classification select options in search results do not have the correct attribute to identify their labels
  • Search input on the home page (optional feature) is does not have a legend or an accessible name
  • Sign-on page contains form landmarks with the same parent region that do not have unique labels.
  • Table of contents and the template "ContentSide" both use "complementary" landmarks (aside) with the same parent region are not distinguished from one another because they have the same "" label
  • User toolbar "navigation" landmarks with the same parent region are not distinguished from one another because they have the same "" label
  • Icons in product are added using CSS pseudo-elements ::before or ::after may not be interpreted by assistive technologies, however these icons usually present a decorative image used as an alternative to and alongside a text link
  • Skip-to-the-main-content link does not reside in a landmark role but it is tabbable and appears on screen when receiving keyboard focus

Note: Customers have the ability to embed content which could cause this criteria to fail.

1.3.2 Meaningful Sequence (Level A) Supports The product presents content in the correct reading order and can be programmatically determined.

Note: Customers have the ability to embed content which could cause this criteria to fail.
1.3.3 Sensory Characteristics  (Level A) Partially Supports The product supports instructions provided for the understanding and operation of content which do not rely solely on sensory characteristics of components such as shape, size, visual location, orientation, or sound except for the following functionality:
  • Embedded Contextual Help Touchpoint navigation icons (optional feature)
  • CRM Touchpoint navigation icons (optional feature)
1.4.1 Use of Color (Level A) Partially Supports In the product, color is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element except for the following functionality:
  • primary, secondary, and tertiary links do not have an underline or enough contrast ratio with the surrounding text
Note: Customers have the ability to embed content which could cause this criteria to fail.
1.4.2 Audio Control (Level A) Supports There is no audio contained in the product.

Note: Customers have the ability to embed content which could cause this criteria to fail.
2.1.1 Keyboard (Level A) Partially Supports In the product all functionality of the content is operable through a keyboard interface except for the following functionality:
  • Navigation via the hierarchy drop-down (folder icon) in the user toolbar
  • Tooltips generated by the browser via the <title> attribute (ex: the Skip to main content link, the "back to the top" link, and Previous and Next page links) do not magnify
  • In the CRM Touchpoint, the "copy link" icon is not accessible by keyboard
  • In the CRM Touchpoint, the "search" "view", and "create" tabs were not accessible by keyboard
  • In the CRM Touchpoint, the "Refine search" is not able to be properly activated by keyboard

Note: Customers have the ability to embed content which could cause this criteria to fail.

2.1.2 No Keyboard Trap (Level A) Supports  No components of the product will "trap" keyboard focus within sections of content
2.1.4 Character Key Shortcuts (Level A 2.1 only) Supports

The product does not use single key character shortcuts.

Note: Customers have the ability to embed content which could cause this criteria to fail.

2.2.1 Timing Adjustable (Level A) Supports The product has no content with unexpected changes in content or context
2.2.2 Pause, Stop, Hide (Level A) Supports

While the product reflects latest content, this information is not presented in a way that blinks, scrolls, or auto-updates.

Note: Customers have the option of including content which could cause this criteria to fail.

2.3.1 Three Flashes or Below Threshold (Level A) Supports

The product contains no flashing content.

Note: Customers have the option of including images in content that may contain text which could cause this criteria to fail.

2.4.1 Bypass Blocks (Level A) Partially Supports The product contains a skip to main content link at the top of every page as well as table of contents links at the top of each content section to jump to subsections of content. The following functionality:
  • All Touchpoint iframes do not have a title attribute
  • The user toolbar contains multiple elements with the navigation role but lack unique labels
  • The footer contains multiple elements with the navigation role but lack unique labels
  • The table of contents <aside> does not have an accessible name
  • The aside landmark .mt-content-side driven by the Content-Side template does not have an accessible name. 
  • Skip-to-the-main-content link does not reside in a landmark role but it is tabbable and appears on screen when receiving keyboard focus
2.4.2 Page Titled (Level A) Supports All pages in the product have a page title defined.
2.4.3 Focus Order (Level A) Partially Supports Product elements can be navigated sequentially to maintain context except for the following functionality:
  • Contextual help dialogs can be navigated out of by tabbing backwards from the first selectable element
  • Users cannot keyboard navigate through the hierarchy drop-down (folder icon) links in the user toolbar
  • Skip to content link has a tabindex greater than 0
  • Search field on the search results page has a tabindex greater than 0
  • On the search page, the results with a role of "none", have a tabindex="2" which results in the summary not being focusable
  • Search field and button in the user toolbar have a tabindex greater than 0 * user and password fields in the user toolbar have a tabindex greater than 0
  • User/password sign in button has a tabindex greater than 0
  • All input fields in the "Leave Feedback" form have a tabindex greater than 0
  • Status message focus does not change when triggered through user interaction
  • Show more search results button does not change focus to most recently viewable search result
  • CRM Touchpoint's "Show more" button on the search tab is accessible but only appears on the second round through the page.
  • CRM Touchpoint's results are tabindexed dynamically with the "Show more" button having a tabindex=10000. 
  • CRM Touchpoint's tabs (Search, View, Create) are not focusable by the keyboard.
Note: Customers have the ability to embed content which could cause this criteria to fail.
2.4.4 Link Purpose (In Context) (Level A) Partially Supports All links in the product convey the purpose of that link except for the following functionality.
  • Site navigation links in the embedded contextual help Touchpoint
  • Empty home link appears on special:search and Special:userlogin
Note: Customers have the ability to embed content which could cause this criteria to fail.
2.5.1 Pointer Gestures (Level A 2.1 only) Supports

The product does not utilize multi-point or path-based gestures.

Note: Customers have the ability to embed content which could cause this criteria to fail.

2.5.2 Pointer Cancellation (Level A 2.1 only) Supports

Where the product can be operated using a single pointer, the down event of the pointer is not used to execute any part of the function.

Note: Customers have the ability to embed content which could cause this criteria to fail.

2.5.3 Label in Name (Level A 2.1 only) Supports

For user interface components with labels that include text or images of text, the name contains the text that is presented visually.

Note: Customers have the ability to embed content which could cause this criteria to fail.

2.5.4 Motion Actuation (Level A 2.1 only) Supports

The product does not utilize multi-point or path-based gestures.

Note: Customers have the ability to embed content which could cause this criteria to fail.

3.1.1 Language of Page (Level A) Partially Supports All pages in the product have a language attribute except for the following functionality:
  • All Touchpoints do not have a default site language declaration in their <html> tags
3.2.1 On Focus (Level A) Supports

All elements in the product do not change context on focus.

Note: Customers have the ability to embed content which could cause this criteria to fail.

3.2.2 On Input (Level A) Partially Supports All user interface components will not automatically cause a change of context without warning the user ahead of time except for the following functionality:
  • Contextual help links do not warn the user when opening a new dialog
  • External links will open a new window without informing the user of the change in context
  • Open page as PDF link will open a new window without informing the user of the change in context
  • Entries into the search field on the search results page will auto update the search results listed below without the user activating the change in context.
  • The site footer contains a link that opens in a new window without warning.   This can be remedied when customizing the site footer template.
Note: Customers have the ability to embed content which could cause this criteria to fail.
3.3.1 Error Identification (Level A) Supports All incorrectly submitted form fields will display an error message.
3.3.2 Labels or Instructions (Level A) Partially Supports All input fields have an associated label that identifies the data required for that field except for the following functionality:
  • Search input does not have a visible label, though it does have a placeholder
  • Email input fields for sign in and registration do not explain the required data format.
  • Recaptcha form field missing a label
  • The instant translation (optional feature) drop-down does not have a visible label, though it does have placeholder text and a title.

Note: Customers have the ability to embed content which could cause this criteria to fail.

4.1.1 Parsing (Level A) Partially Supports All front facing code is generated using semantic HTML, have complete start and end tags, are nested according to their specifications, and do not contain duplicate attributes except for the following functionality:
  • Two script tags have the same ID
  • Sign in, registration, and forgot password fields for username and email have duplicate IDs
  • <nav> on the user toolbar has a redundant ARIA role of "navigation
  • Skip-to-the-main-content link does not reside in a landmark role but it is tabbable and appears on screen when receiving keyboard focus
  • Search Touchpoint utilizes depreciated attributes: "version" and "frameborder"
  • Search In Place Touchpoint utilizes depreciated attributes: "version" and "frameborder"
  • Search input banner on the home page (optional feature) contains a button with a redundant aria role

Note: Customers have the ability to embed content which could cause this criteria to fail.

4.1.2 Name, Role, Value (Level A) Partially Supports All user controls in the product are created through semantic HTML, with appropriate labels, which makes them available to assistive technologies except for the following functionalities:
  • All Touchpoint iframes do not have a title attribute
  • Top level header navigation does not have appropriate aria labels to describe the menus
  • Guide tab scroll buttons do not have text describing their functionality
  • Empty home link appears on special:search and special:userlogin
  • Classification select options in search results do not have the correct attribute to identify their labels
  • User toolbar contains a search that resides in a form lacking an accessible name
  • Sign on page contains a form that lacks an accessible name
  • "View attachments" toggle in the search filters is using an ARIA attribute that is not allowed
  • On the search page, the results, with a role of "none", have a tabindex="2"

Note: Customers have the ability to embed content which could cause this criteria to fail.

Table 2: Success Criteria, Level AA

For Level AA conformance, the Web page satisfies all the Level A and Level AA Success Criteria, or a Level AA conforming alternate version is provided.

Criteria Conformance Level Remarks and Explanations
1.2.4 Captions (Live) (Level AA) Supports The product does not contain live content.

Note: Product offers the ability to embed third-party live content which could cause this criteria to fail.
1.2.5 Audio Description (Prerecorded) (Level AA) Supports The product does not contain audio content.

Note: Product offers the ability to embed third-party audio content which could cause this criteria to fail.
1.3.4 Orientation (Level AA 2.1 only) Supports

The product does not restrict view or operation to a single display orientation.

Note: Customers have the ability to embed content which could cause this criteria to fail.

1.3.5 Identify Input Purpose (Level AA 2.1 only) Partially Supports

The product supports the ability to have input fields to be programmatically determined in order to assist with completing forms in content.

Sign in, registration, and My Preferences forms (username, password, email) inputs have auto-complete turned off.

1.4.10 Reflow (Level AA 2.1 only) Partially Supports

When viewing on 1280 resolution and magnified to 400% (Vertical scrolling content at a width equivalent to 320 CSS pixels), the content was presented without loss of information and did not require scrolling in two dimensions, but some functionality was compromised.

  • Tooltips using the title attribute for the links do not magnify
  • "Sticky” breadcrumb and the member toolbar with search each take up 1/3 of the screen respectively, leaving the rest of page content to scroll underneath (elements can be made "unsticky" using CSS and JavaScript)
  • Breadcrumb "expand" menu may expand to take up entire screen and require backtracking or refreshing to dismiss (customers have the ability to reposition the "close" button using CSS)
1.4.11 Non-text Contrast (Level AA 2.1 only) Partially Supports

The color contrast of every potential visual condition for an active component within the user interface on the page fails to maintain a color contrast ratio of 3.0:1 or higher in all instances, unless the contrast of the state aligns with the browser's default color scheme.

  • Certain links and buttons in the table of contents (in unfocused and hovered states)
  • The submit search button in the search input section (unfocused state)
  • Placeholder text and border of the search input field (unfocused, focused, and hovered states)
1.4.12 Text Spacing (Level AA 2.1 only) Supports

With no loss of content or functionality, the product supports setting all of the following and by changing no other style property:

  • Line height (line spacing) to at least 1.5 times the font size;
  • Spacing following paragraphs to at least 2 times the font size;
  • Letter spacing (tracking) to at least 0.12 times the font size;
  • Word spacing to at least 0.16 times the font size.
1.4.13 Content on Hover or Focus (Level AA 2.1 only) Supports

Content that is triggered by the hover & focus states is dismissible, hoverable, and persistent.

The browser-generated tooltips that occur due to the <title> attribute (ex: the Skip to main content link, the "back to the top" link, and Previous and Next page links) are not hoverable, but the tooltips match the link text. 

1.4.3 Contrast (Minimum) (Level AA) Partially Supports The product supports the correct foreground to background contrast ratios except for the following elements:
  • Primary link color variable
  • Secondary link color
  • Primary link and text inside primary container background
  • Primary link and text inside secondary container background
  • Secondary link and text inside primary container background
  • Secondary link and text inside secondary container background
  • Highlight link and text color in highlight container
  • social share link colors
  • Tertiary, quaternary font colors
  • Disabled view of the "Submit feedback"
  • Touchpoint search result link colors * Touchpoint filter breadcrumb links (active & disabled)

Note: Customers have the option of setting custom CSS/CSS variables in a way that will meet this criteria.

1.4.4 Resize text (Level AA) Supports Note: Customers have the option of setting custom CSS/CSS variables in a way that may cause this criteria to fail.
1.4.5 Images of Text (Level AA) Supports The product does not use images that contain text.

Note: Customers have the option of including images in content that may contain text which could cause this criteria to fail.
2.4.5 Multiple Ways (Level AA) Supports Product supports multiple ways to navigate through content pages as well as a site level search option.
2.4.6 Headings and Labels (Level AA) Supports Note: Customers have the ability to add/remove headings in the content that could cause this criteria to fail.
2.4.7 Focus Visible (Level AA) Supports Note: Customers have the option of setting custom CSS/CSS variables in a way that may cause this criteria to fail.
3.1.2 Language of Parts (Level AA) Supports

Product does not include more than one language in a site.

Note: Customer has the ability to add different languages to a site. The Editor will not strip out the proper language attributes if the customer adds them manually.

3.2.3 Consistent Navigation (Level AA) Supports The product uses consistent and repeatable navigation across the site.
3.2.4 Consistent Identification (Level AA) Supports Components and controls are consistently identified across the product. 
3.3.3 Error Suggestion (Level AA) Supports Note: Password reset errors are not presented as errors to maintain security protocols
3.3.4 Error Prevention (Legal, Financial, Data) (Level AA) Partially Supports Product supports this criteria except for the following functionality:
  • Registering for a site does not allow a user to confirm their data before submitting the form.
4.1.3 Status Messages (Level AA 2.1 only) Supports The product supports status messages that can be programmatically determined through role or other properties so that they can be presented through assistive technologies without receiving focus.

For more information:

  • Was this article helpful?