Accessibility - Dashboard Pages

In the tables below, you can see the accessibility fixes completed for the 26.2 release. The tables present the application, page, and accessibility criteria that were fixed.

Accessibility criteria	widget settings: plan-status, quality-score, evaluation calibration, forms calibration, kpi trend, coaching	widgets: cxone agent contact view
Text Alternatives and Captions Make visuals understandable for all Images, icons, and media must have clear text alternatives like alt text, labels, or transcripts.	Yes	Yes
Visual Design: Color and Contrast Make content easy to read and see Text and visual elements need enough contrast from the background, and pages must work well with 200% zoom.	Yes	Yes
Keyboard Navigation and Focus Make sure the product works without a mouse Users should reach elements by keyboard. Focus (like outlines) must always be visible and not hidden behind headers.	Yes	Yes
Assistive Tech Support (JAWS, Voice, etc.) Work well with screen readers and voice tools Elements must have correct labels and roles so assistive tools (like JAWS or Dragon) can read or activate them.	Yes	Yes
Page Navigation Keep movement clear and predictable Menus and links should be in the same spot on every page, keyboard-friendly, and clearly labeled with logic navigation between components.	Yes	Yes
Forms and Error Messages Make input clear and fixable Fields have a label, and mistakes should be showing clearly.	Yes	Yes
Status Messages and Alerts Announce changes for assistive tools When something changes (like “saved” or “error”), tools like screen readers should hear it.	Yes	Yes

Accessibility criteria	Add Left/right navigation arrows on lower resolutions on widget panel
Text Alternatives and Captions Make visuals understandable for all Images, icons, and media must have clear text alternatives like alt text, labels, or transcripts.	Yes Left/right arrow icons include descriptive alt text (e.g., 'Navigate left', 'Navigate right').
Visual Design: Color and Contrast Make content easy to read and see Text and visual elements need enough contrast from the background, and pages must work well with 200% zoom.	Yes Arrow navigation controls meet WCAG 2.2 contrast requirements against widget panel background.
Keyboard Navigation and Focus Make sure the product works without a mouse Users should reach elements by keyboard. Focus (like outlines) must always be visible and not hidden behind headers.	Yes Arrow navigation is keyboard operable; users can tab to arrows and activate with Enter/Space.
Assistive Tech Support (JAWS, Voice, etc.) Work well with screen readers and voice tools Elements must have correct labels and roles so assistive tools (like JAWS or Dragon) can read or activate them.	Yes Navigation arrows include ARIA labels and role='button'; panel scroll position announced.
Page Navigation Keep movement clear and predictable Menus and links should be in the same spot on every page, keyboard-friendly, and clearly labeled with logic navigation between components.	Yes Widget panel navigation area properly structured as a navigation landmark.
Status Messages and Alerts Announce changes for assistive tools When something changes (like “saved” or “error”), tools like screen readers should hear it.	Yes Panel scroll position and visible widget changes announced to assistive technology.

Accessibility criteria

Add Left/right navigation arrows on lower resolutions on widget panel

Text Alternatives and Captions

Make visuals understandable for all

Images, icons, and media must have clear text alternatives like alt text, labels, or transcripts.

Yes

Left/right arrow icons include descriptive alt text (e.g., 'Navigate left', 'Navigate right').

Visual Design: Color and Contrast

Make content easy to read and see

Text and visual elements need enough contrast from the background, and pages must work well with 200% zoom.

Yes

Arrow navigation controls meet WCAG 2.2 contrast requirements against widget panel background.

Keyboard Navigation and Focus

Make sure the product works without a mouse

Users should reach elements by keyboard. Focus (like outlines) must always be visible and not hidden behind headers.

Yes

Arrow navigation is keyboard operable; users can tab to arrows and activate with Enter/Space.

Assistive Tech Support (JAWS, Voice, etc.)

Work well with screen readers and voice tools

Elements must have correct labels and roles so assistive tools (like JAWS or Dragon) can read or activate them.

Yes

Navigation arrows include ARIA labels and role='button'; panel scroll position announced.

Page Navigation

Keep movement clear and predictable

Menus and links should be in the same spot on every page, keyboard-friendly, and clearly labeled with logic navigation between components.

Yes

Widget panel navigation area properly structured as a navigation landmark.

Status Messages and Alerts

Announce changes for assistive tools

When something changes (like “saved” or “error”), tools like screen readers should hear it.

Yes

Panel scroll position and visible widget changes announced to assistive technology.

Accessibility criteria	Zoom in support to domain names in dashboard
Text Alternatives and Captions Make visuals understandable for all Images, icons, and media must have clear text alternatives like alt text, labels, or transcripts.	Yes Domain name icons and visual elements include descriptive alt text.
Visual Design: Color and Contrast Make content easy to read and see Text and visual elements need enough contrast from the background, and pages must work well with 200% zoom.	Yes Domain name text and UI elements maintain WCAG 2.2 contrast compliance at 200% zoom.
Keyboard Navigation and Focus Make sure the product works without a mouse Users should reach elements by keyboard. Focus (like outlines) must always be visible and not hidden behind headers.	Yes Add Widget domain selection remains fully keyboard navigable at 200% zoom.
Assistive Tech Support (JAWS, Voice, etc.) Work well with screen readers and voice tools Elements must have correct labels and roles so assistive tools (like JAWS or Dragon) can read or activate them.	Yes Domain list items and selection controls properly labeled with ARIA at all zoom levels.
Page Navigation Keep movement clear and predictable Menus and links should be in the same spot on every page, keyboard-friendly, and clearly labeled with logic navigation between components.	Yes Domain section maintains proper heading and landmark structure during zoom reflow.
Forms and Error Messages Make input clear and fixable Fields have a label, and mistakes should be showing clearly.	Yes Domain search/filter inputs properly labeled and accessible at 200% zoom.
Status Messages and Alerts Announce changes for assistive tools When something changes (like “saved” or “error”), tools like screen readers should hear it.	Yes Domain selection changes and list updates announced via ARIA live regions.

Accessibility criteria

Zoom in support to domain names in dashboard

Text Alternatives and Captions

Make visuals understandable for all

Images, icons, and media must have clear text alternatives like alt text, labels, or transcripts.

Yes

Domain name icons and visual elements include descriptive alt text.

Visual Design: Color and Contrast

Make content easy to read and see

Text and visual elements need enough contrast from the background, and pages must work well with 200% zoom.

Yes

Domain name text and UI elements maintain WCAG 2.2 contrast compliance at 200% zoom.

Keyboard Navigation and Focus

Make sure the product works without a mouse

Users should reach elements by keyboard. Focus (like outlines) must always be visible and not hidden behind headers.

Yes

Add Widget domain selection remains fully keyboard navigable at 200% zoom.

Assistive Tech Support (JAWS, Voice, etc.)

Work well with screen readers and voice tools

Elements must have correct labels and roles so assistive tools (like JAWS or Dragon) can read or activate them.

Yes

Domain list items and selection controls properly labeled with ARIA at all zoom levels.

Page Navigation

Keep movement clear and predictable

Menus and links should be in the same spot on every page, keyboard-friendly, and clearly labeled with logic navigation between components.

Yes

Domain section maintains proper heading and landmark structure during zoom reflow.

Forms and Error Messages

Make input clear and fixable

Fields have a label, and mistakes should be showing clearly.

Yes

Domain search/filter inputs properly labeled and accessible at 200% zoom.

Status Messages and Alerts

Announce changes for assistive tools

When something changes (like “saved” or “error”), tools like screen readers should hear it.

Yes

Domain selection changes and list updates announced via ARIA live regions.

Accessibility criteria	dashboard (manage dashboard, header, modal popups, webapps)	reports (my reports, prebuilt reports, report modal popups)	Widgets & charts (widget settings, grids, chartjs, highcharts, widget container, queue counter)
Text Alternatives and Captions Make visuals understandable for all Images, icons, and media must have clear text alternatives like alt text, labels, or transcripts.	Yes Added alt text to all dashboard icons and images.	Yes Alt text added for report page icons.	Yes Alt text added to chart elements and widget icons.
Visual Design: Color and Contrast Make content easy to read and see Text and visual elements need enough contrast from the background, and pages must work well with 200% zoom.	Yes Increased contrast in dashboard pages. Tested at 200% zoom.	Yes Contrast improvements in report pages and modals.	Yes Color contrast improved in charts and widget settings.
Keyboard Navigation and Focus Make sure the product works without a mouse Users should reach elements by keyboard. Focus (like outlines) must always be visible and not hidden behind headers.	Yes Keyboard navigation enabled. Skip-to-main-content added (DASH-AMP1). Keyboard operability ensured (DASH-AMP13).	Yes Keyboard navigation for report pages and modals.	Yes Keyboard navigation for widget settings, grids, charts.
Assistive Tech Support (JAWS, Voice, etc.) Work well with screen readers and voice tools Elements must have correct labels and roles so assistive tools (like JAWS or Dragon) can read or activate them.	Yes ARIA labels and roles added (DASH-AMP6, DASH-AMP7).	Yes ARIA attributes added to report controls.	Yes ARIA labels for charts, widgets, grids.
Page Navigation Keep movement clear and predictable Menus and links should be in the same spot on every page, keyboard-friendly, and clearly labeled with logic navigation between components.	Yes Skip navigation (DASH-AMP1). Meaningful frame titles (DASH-AMP20).	Yes Consistent report page navigation.	Yes Logical tab order in widget containers.
Forms and Error Messages Make input clear and fixable Fields have a label, and mistakes should be showing clearly.	Yes Form field labels and error messages added.	Yes Report modal forms properly labeled.	Yes Widget settings forms with validation.
Status Messages and Alerts Announce changes for assistive tools When something changes (like “saved” or “error”), tools like screen readers should hear it.	Yes ARIA live regions for status messages.	Yes Status announcements for report operations.	Yes Widget status messages use ARIA live regions.

Accessibility criteria

dashboard (manage dashboard, header, modal popups, webapps)

reports (my reports, prebuilt reports, report modal popups)

Text Alternatives and Captions

Make visuals understandable for all

Images, icons, and media must have clear text alternatives like alt text, labels, or transcripts.

Yes

Added alt text to all dashboard icons and images.

Yes

Alt text added for report page icons.

Yes

Alt text added to chart elements and widget icons.

Visual Design: Color and Contrast

Make content easy to read and see

Text and visual elements need enough contrast from the background, and pages must work well with 200% zoom.

Yes

Increased contrast in dashboard pages. Tested at 200% zoom.

Yes

Contrast improvements in report pages and modals.

Yes

Color contrast improved in charts and widget settings.

Keyboard Navigation and Focus

Make sure the product works without a mouse

Users should reach elements by keyboard. Focus (like outlines) must always be visible and not hidden behind headers.

Yes

Keyboard navigation enabled. Skip-to-main-content added (DASH-AMP1). Keyboard operability ensured (DASH-AMP13).

Yes

Keyboard navigation for report pages and modals.

Yes

Keyboard navigation for widget settings, grids, charts.

Assistive Tech Support (JAWS, Voice, etc.)

Work well with screen readers and voice tools

Elements must have correct labels and roles so assistive tools (like JAWS or Dragon) can read or activate them.

Yes

ARIA labels and roles added (DASH-AMP6, DASH-AMP7).

Yes

ARIA attributes added to report controls.

Yes

ARIA labels for charts, widgets, grids.

Page Navigation

Keep movement clear and predictable

Menus and links should be in the same spot on every page, keyboard-friendly, and clearly labeled with logic navigation between components.

Yes

Skip navigation (DASH-AMP1). Meaningful frame titles (DASH-AMP20).

Yes

Consistent report page navigation.

Yes

Logical tab order in widget containers.

Forms and Error Messages

Make input clear and fixable

Fields have a label, and mistakes should be showing clearly.

Yes

Form field labels and error messages added.

Yes

Report modal forms properly labeled.

Yes

Widget settings forms with validation.

Status Messages and Alerts

Announce changes for assistive tools

When something changes (like “saved” or “error”), tools like screen readers should hear it.

Yes

ARIA live regions for status messages.

Yes

Status announcements for report operations.

Yes

Widget status messages use ARIA live regions.