|
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. Example: Added alt text to icons on the dashboard and ensured that icons without meaning are marked decorative. |
Yes |
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. Example: Increased contrast between text and buttons; tested main pages on 200% zoom to ensure nothing is cut off. |
No |
No |
No |
|
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. Example: Tabbing through the header presents a new button called “skip to main content”, dropdown menus open on keyboard. |
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. Example: Added accessible names to buttons so Dragon can trigger “Send”; tested screen reader flow for announcements and buttons. |
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. Example: User Keyboard Navigation guide is functional across elements. All menus can be accessed using the Tab key. |
Yes |
Yes |
Yes |
|
Forms and Error Messages Make input clear and fixable Fields have a label, and mistakes should be showing clearly. Example: “Skill Name field is required” now shows below the field. Focus changes to notification. |
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. Example: Success messages use ARIA live region — JAWS reads “Saved successfully”. |
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. Example: Added alt text to icons on the dashboard and ensured that icons without meaning are marked decorative. |
Yes |
Yes |
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. Example: Increased contrast between text and buttons; tested main pages on 200% zoom to ensure nothing is cut off. |
No |
No |
No |
No |
|
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. Example: Tabbing through the header presents a new button called “skip to main content”, dropdown menus open on keyboard. |
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. Example: Added accessible names to buttons so Dragon can trigger “Send”; tested screen reader flow for announcements and buttons. |
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. Example: User Keyboard Navigation guide is functional across elements. All menus can be accessed using the Tab key. |
Yes |
Yes |
Yes |
Yes |
|
Forms and Error Messages Make input clear and fixable Fields have a label, and mistakes should be showing clearly. Example: “Skill Name field is required” now shows below the field. Focus changes to notification. |
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. Example: Success messages use ARIA live region — JAWS reads “Saved successfully”. |
Yes |
Yes |
Yes |
Yes |