CXone Expert Accessibility Conformance Report - WCAG 2.2 Edition

• 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
• decorative images associated with redundant links should be marked with blank alt attributes
• Touchpoints feature SVGs with no accessible name

• Classification select options in search results do not have the correct attribute to identify their labels
• Feedback consent checkbox has an invalid reference label
• GenSearch output generates in paragraph format, but visually may appear as a list
• Guide tab links use the ARIA role="presentation" on a focusable object that contains content (can be avoided by using "single" rather than "tabbed" guide pages)
• Home page does not have a default H1 (can be added with content)
• 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
• Open registration page contains a Recaptcha form field missing a label
• Registration form fields contain duplicate IDs to user sign-in fields located on the same page
• Search input on the home page (optional feature) is does not have a legend or an accessible name
• Search page filters contain checkboxes that are not grouped together
• Sign-on page contains form landmarks with the same parent region that do not have unique labels
• 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
• 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

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

• Embedded Contextual Help Touchpoint navigation icons (optional feature)
• CRM Touchpoint navigation icons (optional feature)

• primary, secondary, and tertiary links do not have an underline or enough contrast ratio with the surrounding text

• 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.

The product does not use single key character shortcuts.

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

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.

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.

• Touchpoint iframes do not have a title attribute, the "skip-to-main" requires surrounding context, and not all content resides in a landmark element.
• 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 Sign In page and Search Touchpoints contain form elements that 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 tab-able and appears on screen when receiving keyboard focus

• 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
• 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.

• Site navigation links in the embedded contextual help Touchpoint
• Empty home link appears on special:search and Special:userlogin

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.

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.

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.

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.

• All Touchpoints do not have a default site language declaration in their <html> tags

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.

• 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.

All elements for help product do not change position on page.

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

• 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.

Changing the setting of any user interface component does not automatically cause a change of context unless the user has been advised of the behavior before using the component.

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

For WCAG 2.0 and 2.1, the September 2023 errata update indicates this criterion is always supported. See the WCAG 2.0 Editorial Errata and the WCAG 2.1 Editorial Errata.

WCAG 2.0 and 2.1 – Always answer ‘Supports’

WCAG 2.2 (obsolete and removed) - Does not apply

• All Touchpoint iframes do not have a title attribute
• Top level header navigation (an optional feature) 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.

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.

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.

• quaternary font colors
• touchpoint link colors

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

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)

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)

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.

with the exception of the following functionality:

• Instant Translation drop down & the Search input on the user toolbar do not currently text spacing adjustments

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. 

When a user interface component receives keyboard focus, the component is not entirely hidden due to author-created content except for the following functionality:

• "F1" windows allow for keyboard navigation of the page underneath that is not visible due.

Note: Customer has the ability to add content that would cause this criteria to fail.

Product does not include any features that require any dragging movement to achieve an operation.

Note: Customer has the ability to add content that would cause this criteria to fail.

Controls in product that require pointer inputs for interaction are at least 24 x 24 CSS pixels or larger and spaced sufficiently.

Note: Customer has the ability to add content that would cause this criteria to fail

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.

The product uses consistent and repeatable navigation across the site.

Note: Customer has the ability to add content that would cause this criteria to fail.

• Registering for a site does not allow a user to confirm their data before submitting the form.

Product does not require a cognitive function test (such as remembering a password or solving a puzzle) for any step in an authentication process.

Note: Customer has the ability to add content that would cause this criteria to fail.