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 |
Page name: Time off Rules |
Page name: Time off Summary |
Page name: Manage Request |
|---|---|---|---|
|
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 |
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 |
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 |
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 |
Yes |
|
Forms and Error Messages Make input clear and fixable Fields have a label, and mistakes should be showing clearly. |
Yes |
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 |
Yes |
|
Accessibility criteria |
Page name: Approval Rules |
Page name: General Tab |
Page name: Netstaffing Tab |
Page name: Conditions Tab |
|---|---|---|---|---|
|
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 |
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 |
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 |
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 |
Yes |
Yes |
|
Forms and Error Messages Make input clear and fixable Fields have a label, and mistakes should be showing clearly. |
Yes |
Yes |
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 |
Yes |
Yes |