Accessibility - Data Policies 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 |
Page name: Data Policies - Policies tab |
Page name: Policy Details |
|---|---|---|
|
Text Alternatives & Captions Make visuals understandable for all Images, icons, and media must have clear text alternatives - like alt text, labels, or transcripts. |
Yes |
Yes |
|
Keyboard Navigation & Focus Make sure the product works without a mouseUsers 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 & Error Messages Make input clear and fixable. Fields have a label, and mistakes should be showing clearly. |
Yes |
Yes |
|
Status Messages & Alerts Announce changes for assistive tools When something changes (like “saved” or “error”), tools like screen readers should hear it. |
Yes |
Yes |
|
Accessibility criteria |
Page name: New Policy |
|---|---|
|
Text Alternatives & Captions Make visuals understandable for all Images, icons, and media must have clear text alternatives - like alt text, labels, or transcripts. |
Yes |
|
Keyboard Navigation & Focus Make sure the product works without a mouseUsers should reach elements by keyboard. Focus (like outlines) must always be visible and not hidden behind headers. |
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 |
|
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 |