Agent Builder: "Run Code" area is confusing

[kangabell]

I was going to report the tooltip here (that appears when you hover on the question-mark icon) as inaccessible to keyboards and screen readers (which it is), but digging around some more I realized this whole area around the code interpreter is a bit confusing. Maybe it's trying to do too many things at once in a very small area:

1. It's a checkbox (but disabled by default, so you can't check it).
2. The label for the checkbox is a button that when clicked doesn't check the box, but rather opens a dialog.
3. The dialog doesn't sufficiently explain the area so there is also a tooltip next to it with more information.

Suggestion:

• Move the tooltip content to the dialog box.
• Add an explicit button for opening the dialog that is distinct from the checkbox, that is
  keyboard-accessible as well as visually identifiable as a button.
• The button can disappear when it is no longer needed.
• The checkbox can stay disabled with a gray label until it is available.

Mockup of the default state with the above changes, and a little bit of decluttering.

---

Related: The bold text that says "Capabilities" appears to be a heading, but on inspection it's actually a <label> with no apparent input associated with it, and no for attribute. It has the same visual style as the text below it that says "Code Interpreter API" so I'm not sure if it's supposed to be a heading that is higher up in the hierarchy, or if it is truly a <label> and the input is missing, or what.

[derekjackson-das]

The Capabilities section as a whole should be included in the rethinking of the UI here too. The "Enable File Search" check box has some accessibility issues, and while it looks the same it behaves differently; the clicking the "Enable File Search" label does select the check box. It is preferable to keep UI elements consistent in how the function for clarity of use.

I agree with Kay when she says that the checkbox is overloaded and trying to do to many things at once and could be simplified to make every action a user distinct with a clearly distinguished control in the the UI rather than adding so much complexity to ask the check box to accomplish more. Since the checkbox is a well established UI element on the Web, and on its own can be easily made accessible I agree that the complexity should be removed and have the other functions moved to something else that can also be made clear and accessible. You could spend a lot of time trying to make the current patter accessible and perhaps succeed with some overwrought aria attributes and announcements, but I suspect it would be easier to simplify the UI and not just benefit accessibility but make the interactions that a user is expected to take much clearer. In my opinion Kay's suggestions are nice and clean and rely on well established web conventions that support accessibility and deliver a clearer UI.