Aias00 opened a new issue, #1831: URL: https://github.com/apache/rocketmq-dashboard/issues/1831
## Problem Several RocketMQ Studio layout commands are rendered as clickable `div` or `span` elements rather than semantic controls: - breadcrumb Home action: `web/src/layouts/MainLayout.tsx:210` - navigation search trigger: `web/src/layouts/MainLayout.tsx:342-371` - Mock/Real data-mode toggle: `web/src/layouts/MainLayout.tsx:373-405` - language and theme toggles: `web/src/layouts/MainLayout.tsx:407-447` - user-menu trigger and search-result rows in the same layout These elements are pointer-operable but do not consistently participate in keyboard navigation or expose an accessible command name and state. ## Impact Keyboard and assistive-technology users cannot reliably invoke common global commands. The visible and accessible labels are also partly hard-coded instead of following the selected Studio language. ## Expected behavior - Render global commands as semantic buttons. - Keep the existing visual layout and click behavior. - Expose localized accessible labels. - Expose toggle state where applicable. - Keep navigation search results keyboard-operable. - Add regression coverage for the semantic controls. ## Scope `MainLayout`, its translation entries, and focused layout tests. This does not change the product policy for exposing Mock/Real mode. ## Existing issue / PR check No existing issue or pull request specifically covering keyboard semantics for these `MainLayout` commands was found. ## Track Track 1 / AI-Native unified control plane / frontend accessibility. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
