Accessibility - Supervisor Workspace (Supervisor) Pages

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

Alternative text were added for all the existing images.

Aria labels were added to all actionable elements.

Yes

Alternative text were added for all the existing images.

Aria labels were added to all actionable elements.

Yes

Alternative text were added for all the existing images.

Aria labels were added to all actionable elements.

Yes

Alternative text were added for all the existing images.

Aria labels were added to all actionable elements.

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.

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.

Example: Tabbing through the header presents a new button called “skip to main content”, dropdown menus open on keyboard.

Yes.

Added keyboard events support for all clickable elements.

Yes.

Added keyboard events support for all clickable elements.

Yes.

Added keyboard events support for all clickable elements.

Yes.

Added keyboard events support for all clickable elements.

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

Added support for Dragon to make the table rows clickable in order to open the right-hand panel to view additional details.

Yes

Added support for Dragon to make the table rows clickable in order to open the right-hand panel to view additional details.

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

Added support for keyboard navigation for all the inputs exclude context menu on the grid

Added skip to main content.

Yes

Added support for keyboard navigation for all the inputs exclude context menu on the grid.

Added skip to main content.

Yes

Added support for keyboard navigation for all the inputs.

Added skip to main content.

Yes

Added support for keyboard navigation for all the inputs.

Added skip to main content.

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

Added support for announcing error messages in filters.

N/A

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”.