Accessibility - Performance Management (Native) Pages

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

Accessibility criteria

Metrics

Objectives

Reporting Set

Data Recalculation

PM Widgets

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.

Y

Y

Y

Y

Y

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.

Y

Y

Y

Y

Y

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.

Y

Y

Y

Y

Y

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.

Y

Y

Y

Y

Y

Forms and Error Messages

Make input clear and fixable

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

Y

Y

Y

Y

Y

Status Messages and Alerts

Announce changes for assistive tools

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

Y

Y

Y

Y

Y