polish-ui

To ensure React dialogs close on Escape, you must verify key handlers are actually bound to the interactive surface. Esc-to-close compliance also requires returning focus appropriately to the triggering element after dismissing modals, sheets, drawers, or popovers.

Checking keyboard shortcut visibility in .tsx files involves validating that action buttons display the correct platform-aware glyphs in the visible label. The UI validation process also confirms the shortcut key handler is actually bound to the button's action.

This UI polish workflow does not apply to backend-only or interaction-neutral code changes. It specifically targets user interaction changes in .tsx or .jsx files, skipping edits that do not introduce new interactive surfaces like dialogs, command palettes, or buttons.

Adding accessibility UX checks for command palettes and popovers requires verifying Esc dismissal behavior and correct focus return for attention-trapping UI primitives. You apply these checks only to the newly edited components to ensure keyboard-driven actions meet core accessibility expectations.

Keyboard-driven action buttons need platform-aware shortcut rendering to display the correct glyphs for different operating systems. This ensures keyboard users see the accurate visible shortcut label and that the displayed shortcut matches the actually bound key handler.