You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Select "Clip to OneNote" button in top right corner.
Navigate to "Location dropdown" under 'Article' button through Tab key and press enter key.
Observe the issue here.
Actual Result:
Keyboard focus does not land over the selected item after expanding the "location dropdown" using keyboard.
Expected Result:
Keyboard focus should land over the selected item after expanding the "location dropdown" using keyboard.
User Experience:
Keyboard user will face difficulty if focus is not landing first items after expanding 'location dropdown' so the end users will not be able to identify that the focus is actually on which control so the end users will get confused.
I've successfully fixed the keyboard focus issue in the location dropdown. When users expand the dropdown using keyboard navigation (Tab + Enter), focus now automatically moves to the currently selected section item, making it easy for keyboard users to identify where they are in the control.
Added focusOnSelectedSection() method that intelligently finds and focuses on the selected section using three fallback strategies:
Searches by section ID if a current section is selected
Falls back to finding the element with aria-selected="true"
Falls back to the first .Section element if neither is found
Updated onPopupToggle() method to call focusOnSelectedSection() when the popup opens, using a setTimeout to ensure the popup has fully rendered before attempting to set focus.
Technical Details
The OneNotePicker library (an external npm package) doesn't automatically manage focus when the dropdown opens. This fix adds focus management at the wrapper level in the SectionPicker component, ensuring compliance with Microsoft's Liquid accessibility guidelines for Focus Order (requirement 02.04.03).
Testing
TypeScript compilation: ✅ Successful
Generated JavaScript includes the new focus management logic
The solution follows existing patterns in the codebase for focus management
Activity
claude commentedon Feb 2, 2026
Claude finished Aanchal Bhansali (@aanchalbhansali)'s task in 4m 48s —— View job •
claude/issue-622-20260202-1644• Create PR ➔Summary
I've successfully fixed the keyboard focus issue in the location dropdown. When users expand the dropdown using keyboard navigation (Tab + Enter), focus now automatically moves to the currently selected section item, making it easy for keyboard users to identify where they are in the control.
Changes Made
Modified
src/scripts/clipperUI/components/sectionPicker.tsx:Added
focusOnSelectedSection()method that intelligently finds and focuses on the selected section using three fallback strategies:aria-selected="true".Sectionelement if neither is foundUpdated
onPopupToggle()method to callfocusOnSelectedSection()when the popup opens, using asetTimeoutto ensure the popup has fully rendered before attempting to set focus.Technical Details
The OneNotePicker library (an external npm package) doesn't automatically manage focus when the dropdown opens. This fix adds focus management at the wrapper level in the SectionPicker component, ensuring compliance with Microsoft's Liquid accessibility guidelines for Focus Order (requirement 02.04.03).
Testing
Next Steps
--- • Branch: claude/issue-622-20260202-1644
Fix keyboard focus in location dropdown for accessibility