Skip static top-bar filenames during keyboard navigation

User intention

Navigate the top bar of my open text document using the keyboard.

The intention is included in the agent’s input prompt alongside environment details and task instructions.

What breaks, and what should happen

Play Both
BeforeThe defect at the parent commit
0:00.00 / 0:00.00Frame 0

Reverse Tab reaches the document filename; after Enter, its outline and the open document remain visible.

AfterThe same script once the merged fix is applied
0:00.00 / 0:00.00Frame 0

Reverse Tab reaches My Account after the context-menu control; Enter opens the account menu.

How is it judged?

01 · Given
Restore the data and starting state.
Meeting notes.txt is open in Text Editor in the prepared admin account. Its name appears in the app top bar, and keyboard focus starts on Close. The filename identifies the open document and has no available activation action.

02 · When
Perform the interaction.
Press Shift+Tab twice from Close, traversing the top-bar controls, then press Enter on the resulting focused element.

03 · Judge
Rationale: The app top bar identifies the open document and provides actions such as its context menu and Close. A keyboard user needs to move between those actions without a static filename appearing to offer another command. Keeping the filename visible but out of sequential focus preserves document orientation while avoiding an inert stop between usable controls.
Require
Skip the static top-bar filename during sequential keyboard traversal, including reverse Tab, while keeping it visible. Preserve keyboard reachability and visible focus for surrounding actions; Enter must activate the actual focused control according to its purpose.
Allowed
  • The exact preceding focus destination may vary if existing actions remain reachable in a logical order and the static filename is skipped.
  • Focus styling and the visual presentation of the filename may differ, provided the open document remains identifiable and the focused actionable control remains clear.

Who repaired it