Autofill failure on Q2 Digital Banking Web Components (Identifier-First Step 2)

Hi 1Password Team / Community,

I’m reporting an issue where the 1Password browser extension detects Step 1 (username) of an identifier-first login workflow, but fails to detect or offer autofill for Step 2 (password).

After contacting the institution's tech team, they confirmed that their platform is powered by Q2 Digital Banking and provided specific technical details on why the extension is struggling:

• Web Components (Shadow DOM): The password input on Step 2 is rendered inside a Q2 Web Component, isolating the field.

• Generic Attributes: The forms use generic autocomplete="on" attributes rather than autocomplete="username" and autocomplete="current-password".

Direct response from the bank:

"The current Q2 login is a multi-step process... The password step is rendered through a Q2 web component, which may explain why some password-manager extensions recognize the first step but do not consistently associate or autofill the password field on the second step."

Since Q2 powers the digital banking stack for hundreds of credit unions and regional banks, updating 1Password’s DOM-parsing rules to handle Q2's Shadow DOM/Web Components would resolve this issue for a huge number of users across multiple financial institutions.

Could the extension team review Q2's web components and consider adding a custom fill rule or heuristic patch for this platform?

Much obliged.

[for transparency, I’m not a developer, but a consultant trying to make 1Password as usable for my clients as possible; my outreach to the PECU team was filtered via Claude, as was the summary above.]