Keyboard Focus for Pop-up Window and Default Button Accessibility

[aayushi_mali]

Hello SmartGWT Team,

I am currently reviewing keyboard accessibility in our SmartGWT application with ScreenReader mode enabled (SC.setScreenReaderMode(true)) and had a few questions regarding pop-up windows and window controls.

• Pop-up window focus
  In some cases, when a pop-up window opens, keyboard focus does not automatically move into the dialog. As a result, keyboard users or screen reader users cannot immediately interact with the contents, and may need to manually move focus into the window.
  
  A similar example can be seen in the SmartGWT Showcase:
  
  https://smartclient.com/smartgwt/sho...ultilevel_sort Could you please recommend any approach to ensure that keyboard focus moves into the pop-up window when it opens?
  • Click the “Multilevel Sort” button.
  • The Sort dialog (MultiSortDialog) opens.
  • Keyboard focus does not appear to automatically move into the dialog or its first interactive element.
  • Keyboard navigation may remain on the element behind the dialog until the user manually sets focus inside the window.

• Default Window control buttons (Close/Minimize)
  For default Window class UI elements, the Close and Minimize buttons do not appear to be accessible for screen reader users. Since these are defaultSmartGWTcomponents, we cannot assign alt text or ARIA labels directly to their icons.
  Is there a recommended way to make these default window controls accessible for keyboard and screen reader users?

Thank you for your guidance.

[Isomorphic]

Thanks for the report - we've made some changes to improve popup (modal) window focus - without changing your code, you should find things working as you expect in tomorrow's builds, dated March 19, and later ones.

We'll get back to you on the window control-buttons.