Accessibility pass: keyboard navigation, focus states, aria labels

[tsouth89]

The desktop UI could use an accessibility sweep, a well-scoped contribution for anyone who cares about a11y.

Areas

• Keyboard navigation through the server list, dialogs, and sidebar.
• Visible focus states on interactive elements.
• aria-labels on icon-only buttons.
• Screen-reader sanity check on the main flows (add server, browse catalog, playground).

A PR for any one area is welcome, it doesn't have to be all at once.

Acceptance

• The targeted area is keyboard-navigable with visible focus and labeled controls.

[BharadwajKanneveti]

Hi @tsouth89, I pulled the latest main and spent some time testing the areas mentioned in this issue. From what I can tell, keyboard navigation, visible focus, and accessible labels seem to be in place for most of the app already.

Is there a particular workflow or component that you'd still like someone to focus on for this issue (e.g. a specific dialog, the server list, the sidebar, or the playground), or are there known accessibility gaps that aren't immediately obvious?

please just let me know your thoughts on this.

[tsouth89]

First increment merged in #165 (keyboard-operable Activity rows, semantic Onboarding progress, error-text bounding, focus rings). Remaining: a focus-state sweep across the rest of the app.

[tsouth89]

Sorry for the lag here, and thanks for actually pulling main and testing first, appreciate that.

You're right that the obvious stuff is mostly handled after #165, so what's left is the less-visible gaps. A few concrete spots if you want a scoped piece.

• Add/Edit Server dialog and the Catalog. Focus should stay trapped while they're open and land back on the trigger when they close, and the icon-only buttons still need aria-labels.
• Keyboard nav through the server list (tab/arrow order, Enter or Space to activate a row).
• Playground tab order through the server and tool pickers, plus the run button.
• A quick screen-reader pass over add-server, browse-catalog, and playground, since those can read wrong even when they look fine.

Grab whichever one you like, one area per PR is great. If anything's ambiguous just ask here.