fix(ui): resolve additional jsx-a11y violations

[pandego]

refs #11614

Summary

Second small pass on issue #11614 to reduce a11y lint violations with low-risk, focused fixes.

What changed

• Added missing iframe titles on APIs page
• Added missing img alt text in UserPicture and SpanImage
• Removed invalid aria-role usage from experiment token cost components
• Removed explicit autoFocus={false} props in ModelMenu

Validation

• cd app && pnpm fmt:check
• cd app && pnpm lint
• cd app && pnpm typecheck

---

Note

Low Risk
Small, UI-only accessibility attribute changes with minimal behavioral impact (possible minor focus behavior differences in menus).

Overview
Addresses additional jsx-a11y violations across the UI.

Adds missing accessible labels by providing title on the REST/GraphQL docs iframes and alt text on user avatar and span image <img> elements. Removes invalid aria-role usage from experiment token cost displays and drops redundant autoFocus={false} props from model selection menus.

^{Written by Cursor Bugbot for commit da09b48. This will update automatically on new commits. Configure here.}

[dosubot]

Related Documentation

Checked 0 published document(s) in 2 knowledge base(s). No updates required.

^{How did I do? Any feedback?}  

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.}

[cursor]

Removed role instead of fixing to valid role attribute

Low Severity

The invalid aria-role="button" was removed entirely instead of being corrected to the valid role="button". The sibling component ExperimentAverageRunTokenCosts uses role="button" on its TokenCosts element for the same pattern (pressable token cost with tooltip). This creates an inconsistency across three nearly identical components — one has the correct role="button" while the other two now have none.

Additional Locations (1)

• app/src/components/experiment/ExperimentRepeatedRunGroupTokenCosts.tsx#L38-L39

 

[pandego]

good point on consistency

I removed aria-role because it’s invalid, but I didn’t switch to role="button" intentionally. With current lint rules (jsx-a11y), adding role on this element pattern can create new a11y warnings, and I wanted to avoid a superficial role-only fix.

I can take either direction, but I’d prefer to align all related token-cost components in one follow-up pass based on maintainer preference:

1. keep role off and rely on the interactive wrapper semantics, or
2. move to a fully semantic button-like structure consistently across all of them.

happy to update this PR if you want option 2 now.

[mikeldking]

@pandego appreciate your focus on a11y. much appreciated