Accessibility - Quality Management (CXone) Admin Pages

In the table below, you can see the accessibility fixes completed for the 26.3 release. The table presents the application, page, and accessibility criteria that were fixed.

Acceptance

guidelines

Page name: 1. Manage Forms(grid)

Page name: 1.1 New Form (Form Designer )

Page name: 1.2 Test Form, Settings and Set Rule

Page name: 2. Quality Planner for Segements

Page name: 2.1 Quality Planner for Tickets

Page name: 2.2 New Plan

Page name: 2.3 New Plan tickets Page name: 3. Category Manager Page name: 4. QM Score Metric Page name: 5. ScoreCard Page name: 5.1 New Score Card

 

 

 

 

 

Perceivable

All text, labels, and UI elements meet minimum contrast ratio requirements as per WCAG 2.2 AA. Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
Alternative text is provided for all non-text elements, images, icons, and informative graphics. Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
Page structure is correctly conveyed through semantic HTML (headings, landmarks, lists). No Yes Yes No No Yes Yes No No No No
Visible focus indicators comply with WCAG 2.2 AA guidelines. Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
Form fields have clear, descriptive labels and instructions. Yes Yes Yes Yes Yes No No Yes Yes Yes No
Error messages are accessible, descriptive, and programmatically associated with their fields. Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes

 

 

 

 

 

 

 

Operable

All functionality is available through keyboard-only navigation, without requiring a mouse. Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
No keyboard traps exist—users can enter and exit all components using standard keys. For popup it is and it is as per standard Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
All interactive components (buttons, toggles, dropdowns, tables, modals) meet operability standards. Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
Time-sensitive interactions (if any) are adjustable or clearly communicated. N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A
Drag-and-drop or pointer-based features (if present) have accessible alternatives. N/A Yes Yes N/A N/A N/A N/A N/A N/A N/A N/A

 

 

 

 

 

Understandable

All pages have descriptive and unique titles. Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
Form validations are accessible, non-ambiguous, and provide contextual instructions. Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
Navigation elements and UI controls are consistent across all Admin pages. Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
Components behave predictably and provide proper ARIA roles, states, and attributes. Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
Drag-and-drop or pointer-based features (if present) have accessible alternatives. Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes

 

 

 

Robust

All content and components are compatible with major assistive technologies (JAWS, NVDA, VoiceOver). Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
ARIA attributes are used correctly and do not override native semantics. Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
HTML markup passes validation and is free of accessibility blockers. Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes

 

Testing & Validation

All identified WCAG 2.2 AA violations are fixed and revalidated. Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
Manual testing is completed for keyboard navigation, screen reader flow, and UI interaction. Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes

 

Definition of Done

All Admin pages meet WCAG 2.2 AA compliance. Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
Test results and remediation logs are attached to the epic. Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes