Keyboard Navigation and Accessibility in Resource Admin
Resource Admin is designed to be fully usable without a mouse. Administrative tasks across all resource types — viewing and editing resource details, managing entitlements, working with tables and data grids, and completing forms — are reachable and operable using keyboard alone. The application also supports screen readers and other assistive technologies through semantic markup, labeled controls, and announced state changes throughout the interface.
This article describes the keyboard conventions that apply across Resource Admin and documents known limitations in the current release.
Visual Accessibility
Resource Admin includes the following visual accessibility improvements across the interface:
Color contrast — The default blue and gray values used throughout the application have been updated to improve contrast, targeting a minimum ratio of 3:1 against adjacent surfaces and 4.5:1 for text. This applies to labels, table headers, search fields, and form controls.
Focus indicators — Every interactive control displays a visible focus outline when it receives keyboard focus. In areas with dense layouts or scrolling containers, focus rings are inset to prevent them from being clipped by surrounding content.
State not conveyed by color alone — Status information such as errors, warnings, and active selections is communicated through icons, text labels, or patterns in addition to color.
Global Keyboard Conventions
The following keys apply across Resource Admin regardless of which area you are working in.
Key | Behavior |
|---|---|
Tab | Moves focus forward through interactive controls in the current view. |
Shift+Tab | Moves focus backward through interactive controls. |
Enter | Activates buttons and most interactive controls. |
Space | Activates many of the same controls as Enter. Prefer Enter when Space does not produce the expected result. |
Arrow keys | Navigate within composite controls: menus, tab strips, and trees. |
Escape | Closes open menus and dialogs where supported. |
Screen Reader Support
Resource Admin exposes semantic information to screen readers throughout the interface:
Page title updates — When navigating between pages within the application, the document title updates to reflect the current view, helping screen reader users confirm where they are.
Labeled controls — Icon-only controls — including dialog close buttons, icon-only action buttons, and navigation controls — carry descriptive labels. Disabled controls are marked as inactive so they are not presented as operable.
Announced state changes — Menus announce whether they are open or closed. Tree nodes announce when they are expanded or collapsed.
Form errors — Validation errors are linked to their fields so screen readers announce the error message alongside the relevant input when focus reaches it.
Live regions — Asynchronous updates such as save confirmations and loading states are announced without interrupting the user's current position. Critical alerts are announced immediately so screen reader users receive time-sensitive information promptly.
Table semantics — Data tables use semantic markup so screen readers can announce row and column context. Sortable column headers include labels that describe both the column name and the current sort direction.
Navigation and Page Structure
Tab strips in Resource Admin use a roving tab index — only one tab holds Tab-stop focus at a time. Tab to enter the strip, then use Arrow keys to move between tabs and Enter to activate the selected tab.
After navigating to a new page within the application, the document title updates to reflect the current view.
Menus and Dropdowns
Tab to a menu trigger and press Enter to open it. Use Arrow keys to move between items. Escape closes the menu and returns focus to the trigger. Menu triggers announce their open and closed state to assistive technologies.
Trees
Tree controls in Resource Admin support full keyboard navigation.
Key | Behavior |
|---|---|
ArrowDown / ArrowUp | Move focus to the next or previous visible node. The active node scrolls into view automatically. |
ArrowRight | Expands a collapsed node; moves focus to the first child if the node is already expanded. |
ArrowLeft | Collapses an expanded node. |
Enter or Space | Selects the focused node. |
Forms and Validation
Form controls throughout Resource Admin follow these conventions:
Every input has an associated label that screen readers announce when the field receives focus.
Validation errors are linked to their fields so screen readers announce the error message alongside the relevant input.
Required fields are indicated both visually and programmatically.
Errors are surfaced as text, not by color alone.
Placeholder text is not used as a substitute for a label.
Tables and Data Grids
Resource Admin uses semantic table markup throughout. Screen readers announce row and column context as you navigate. Sortable column headers include labels describing both the column name and current sort direction. Keyboard focus is maintained during table interactions — loading new data does not trap or lose focus.
Modals and Drawers
Dialogs and drawers are labeled with a title and, where applicable, a description that screen readers announce when they open. Focus is trapped within an open dialog so keyboard users cannot navigate behind it. When a dialog or drawer closes, focus returns to the control that opened it. Close controls are labeled for assistive technologies.
Notifications
Save confirmations and loading states are announced to screen readers without interrupting the user's current position. Critical alerts are announced immediately so screen reader users receive time-sensitive information promptly.
Known Limitations
The following limitations are documented in the current release:
Inconsistent Enter / Space support — Not every custom control responds to both Enter and Space. Prefer Enter when Space does not produce the expected result.
Skip navigation — There is no global skip-to-main-content link in the current release. Keyboard users must Tab through the application header and navigation to reach the main content area on each page.
Reduced motion — There is no global reduced-motion setting in the current release. Users who require reduced motion should configure their operating system accessibility settings; the browser will honor those settings for most animations.
Third-party embedded content — Embedded iFrames and third-party workflow components may have their own accessibility behavior that is outside EmpowerID's direct control. Where EmpowerID controls the markup for embedded content, titles and labels are applied.
Related Articles
Keyboard and Accessibility Support in the IAM Shop — Keyboard reference for the IAM Shop application
Keyboard and Accessibility Support in My Identity — Keyboard reference for the My Identity application
Keyboard and Accessibility Support in My Tasks — Keyboard reference for the My Tasks application