Agent Tools dialog: Change in content from buttons

[kangabell]

When adding a new agent tool that requires an API key, a new form to add the key appears but is not announced to the screen reader. To a non-sighted user, these buttons appear to do nothing.

WCAG Criteria

4.1.3 Status Messages - AA

Testing Method

Manual - VoiceOver, Chrome, MacOS

Notes

Move keyboard focus to the API key field when button is clicked, or use aria-live to announce the change in content.

Screenshot or Screen Recording

View Screen Recording

[kangabell]

Originally identified in #5187:

When you add a tool to an agent that requires to enter an API key, the input box to open that key should automatically get focus. Otherwise, it just appears on top of the tools list, and I as the user wonder why nothing happens when I press the add button.