The Workspace ONE UEM console is thoughtfully designed to be inclusive, accessible, and user-friendly for everyone. It has been thoroughly audited and updated to meet the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA standard and the WAI-ARIA Authoring Practices Guide (APG). The UEM console supports a wide range of accessibility needs by ensuring compatibility with assistive technologies such as screen readers, enabling full keyboard-only navigation, and providing support for high-contrast display modes. These features help create a good user experience, allowing individuals with diverse abilities to efficiently interact with and manage the console.
Before you begin exploring the full functionality of the UEM console or proceed to log in, review the available accessibility features.
Supported Accessibility Features
Screen Reader Support
The console provides consistent, accurate information to screen readers and other assistive technologies across its key workflows.
- Name, Role, Value (WCAG 4.1.2) -The UEM console has new interactive controls, including buttons, links, combo boxes, sliders, tooltips, popovers, tab widgets, radio buttons, menus, and form fields. These controls now show their name, role, and state to assistive technologies. Previously, some controls had incorrect or missing ARIA attributes — for instance, tooltips were identified as links, and text fields as menu popups. These have been corrected so each control reflects its actual type and interaction model. Dynamic state changes such as expanded/collapsed accordions, active pagination items, and toggle button states are now announced correctly when focus moves to or interacts with those elements.
- Landmark and structural semantics - The main navigation and the settings tree are implemented in accordance with WCAG and WAI-ARIA authoring standards. This gives screen-reader users reliable landmarks to orient and navigate the page.
- Bypass links - Skip navigation links are available across the app. This lets keyboard and screen-reader users skip repeated navigation and go directly to the main content.
- Informative and decorative images - Images that convey meaning have descriptive text alternatives. Decorative images are hidden from assistive technologies using suitable techniques so they are not announced unnecessarily.
Keyboard Navigation
Full keyboard operability has been extended across the console, covering areas that were previously reachable only by pointer input.
- Interactive controls are keyboard-operable - Buttons, dropdowns, select inputs, radio groups, menus, accordions, tooltips, and form controls in workflows can be reached and activated using standard keyboard input.
- Standard key conventions - Navigation follows WCAG and WAI-ARIA keyboard conventions. Tab and Shift+Tab traverse the focus sequence. Arrow keys navigate within composite widgets such as radio groups, menus, and tree structures. Enter and Space activate controls as appropriate to their type. Escape closes dialogs and dismisses overlays without triggering unintended side effects.
- No keyboard traps - Focus is handled correctly within modal dialogs. This means users can move within the dialog and exit it easily using the Escape key, without the dialog closing unexpectedly or trapping focus.
- Consistent behavior across flows - Keyboard operability improvements across all critical console flows.
Focus Management
Focus handling has been standardized to give users a clear and predictable experience as they navigate and perform actions.
Improvements include:
- Visible focus indicators - A consistent focus outline ring is now visible on all interactive controls across the console, including buttons, links, form fields, radio buttons, tabs, filter dropdowns, and pagination controls. Previously, focus indicators were absent or invisible in large portions of the UI
- Logical focus order - The tab sequence follows the visual reading order of the page. Focus order issues affecting various pages have been resolved. When a dialog, menu, or overlay opens, focus is moved into it. It is placed on the dialog title or the first interactive element, orienting users to the new context right away. When the overlay is dismissed, focus returns to the triggering element, maintaining the user's position in the page.
- Non-interactive elements excluded - Elements that are visual but not interactive do not receive keyboard focus, preventing confusion during navigation.
Color Contrast
Text and informational content across the console now meet the WCAG 2.1 AA minimum contrast ratio of 4.5:1 between foreground text and its background.
Contrast improvements have been applied across:
- Devices Dashboard
- Add Application (Add flow and Assignment workflow)
- Add Profile (Android Legacy)
- Freestyle Orchestrator (canvas and Add New Flow)
- App List View and Devices List View
- Content Dashboard, Monitoring Dashboard, and Deployment Tracking
- Enrollment Settings tabs
- Device Summary and Troubleshooting pages
- Error message and warning text
- Connectivity status indicators (Wi‑Fi, LAN, and similar labels)
- Organization Groups Column headers
Page Structure and Heading Hierarchy
Correct heading structure is in place across the console, enabling screen reader users to scan pages using heading navigation and understand content hierarchy at a glance.
- Single H1 per page - Pages that previously contained multiple H1 elements now have a single, descriptive page-level heading.
- Correct heading levels - Subheadings are coded at the proper level in the hierarchy without skipping levels.
- Heading coverage - Content sections that were missing headings now include suitable markup so users can understand the structure of complex pages.
Alternative Text and Non-Text Content
Images, icons, and other non-text elements are handled correctly for assistive technology users:
- Meaningful alt text - Informative images and icons (including device logos, graph tick marks, location pins, infographics, platform column headers such as Android, iOS, Chrome, and Windows, and navigation icons) now have descriptive text alternatives that convey their meaning.
- Decorative images suppressed - Decorative images that do not add information are hidden from screen readers using alt="" or aria-hidden="true", preventing unnecessary announcements. This applies to images in Device Summary, Getting Started, Monitoring Dashboard, and elsewhere.
- Actionable icon labels - Icons used as interactive controls (including Edit, Add, Delete, Refresh, Previous/Next Device arrows, and expand/collapse indicators in Organization Groups) now have clear, accurate labels that describe their function rather than their appearance.
- Asterisk and symbol handling - Required field asterisks and other symbolic pseudo-elements that were being announced by screen readers are now hidden from assistive technologies where appropriate, or their meaning is conveyed through accessible text.
Was this page helpful?