Contain keyboard focus within the active sign-in overlay

[Copilot]

The sign-in overlay allowed keyboard focus and screen reader navigation into background Clipper content, breaking the expected focus order (MAS 2.4.3).

• Modal isolation: Make the preview, sidebar, and background live region inert while sign-in is active. Cycle Tab/Shift+Tab through enabled sign-in buttons.
• Focus transitions: Focus the first account button on entry, the progress message during authentication, and an enabled button after cancellation or failure. Restore background interaction and focus after successful sign-in.

Leave the bug open for TCS/E+D accessibility verification.

Original prompt

[OneNote Clipper] [Web] [Sign In] [Keyboard]: Incorrect focus order allows keyboard focus to move to background page content while Sign-in page is active.

Work Item Details

Note: Please focus on the descriptions and information that provide context about the task requirements, functionality, and implementation details. Dates, priorities, and administrative metadata are less relevant for coding tasks.

Description

"Please do not close this bug. This bug should only be closed by TCS, E+D Accessibility tester after verification of the fix."

Environment Details:

Application Name: OneNote Clipper-web

Platform: Web

OS Version: Windows 11 25H2(26220.8764)

Edge Version: Version 150.0.4078.65 (Official build) (64-bit)

Repro Steps:

1. Open OneNote Clipper-web.
2. Navigate to the Sign-in page.
3. Use the Tab key to move through the available interactive elements.
4. Observe the focus behavior.
5. Turn on Narrator and continue navigating using the keyboard.
6. Observe the elements that receive focus and are announced by Narrator.

Actual Result:

While the Sign-in page is active, keyboard focus does not remain within the Sign-in page controls. Focus moves to or exposes elements belonging to the underlying OneNote Web Clipper page. Narrator announces background page content and controls that are not part of the active Sign-in experience, resulting in an illogical focus sequence.

Expected Result:

When the Sign-in page is displayed, keyboard focus should be placed on an appropriate interactive element within the Sign-in page and remain restricted to the active page. Users should navigate only through the Sign-in page controls until the page is dismissed. Background content should not receive focus or be exposed in the focus order.

User Impact:

Keyboard and screen reader users may become disoriented because focus navigates to content that is outside the currently active Sign-in page. Users may be unable to determine their current location, understand the intended navigation sequence, or efficiently complete the sign-in process.

MAS Reference:

MAS 2.4.3 – Focus Order

"If the bug is invalid, incomplete, wrong severity, has unclear reproduction steps or attachments, please tag it with "A11yRCA" and provide a detailed comment on why the A11yRCA tag was added. However, do not add the "A11yRCA" tag if the bug is related to partners or if you have any questions about the bug."

Tags

A11yMAS; A11yONTriaged; A11yRT; A11ySev2; Accessibility; Freeway-Bug; FY27; MAS2.4.3; OneNoteClipper_Web; RT-July2026; TCS-E+D; Web

RCA Analysis

Was change validated in devMain first before porting to fork?

Why was Flighting|Backout not used?

Impact of bug (# users affected):

RCA and Mitigation/Fix Details:

What are you doing to prevent this in the future?

Comments

Agency (Thu, 17 Sep 2026 06:44:57 GMT): ⚠️ Attention Required: Missing Repository Link. Reverting the work item assignment.

The work item is missing a link to a repository branch. Without this link, I cannot work on the work item.
Please use one of the following options to link a repository:

Option A: Traditional Artifact Link

1. Navigate to the Work Item: Open the work item in Azure DevOps.
2. Locate the Links Section: Scroll to the Development area or the Links tab in the work item details.
3. Add a Link to the Repository Branch:
   • Click on Add Link.
   • Select Branch from the available link types.
   • Choose the appropriate repository and branch that corresponds to this work item.
   • Assign the work item again to me.
   • Ensure you save the work item to update it properly.

Option B: Repository Tag

1. Navigate to the Work Item: Open the work item in Azure DevOps.
2. Add a tag using the format: copilot:repo=//@
   • Examples:
     • copilot:repo=MyOrg/MyProject/MyRepo@main
     • copilot:repo=MyOrg/MyProject/MyRepo@feature-branch
   • The branch name after @ is required.
3. Assign the work item again to me.

Important: Use only one linking method - either artifact link OR tag, not both. Only one repository can be linked per work item.

Work item: AB#12066576
Created via Azure DevOps