investigate possible detection of SSO, etc.

> The Issue: The accessibility_scan_status column encounters 18 execution_context_destroyed errors and 15 page_frame_not_ready errors.
> The Pattern: A significant portion of these errors occurs on domains that automatically redirect to a centralized authentication portal (e.g., multiple different subdomains redirecting to [https://idp.nwave.noaa.gov/.](https://idp.nwave.noaa.gov/)..). When a headless browser encounters sudden redirects or complex multi-frame authentication pages, the execution context is frequently destroyed or timed out.
> Actionable Suggestion to GSA: Enhance the scanner's capability to detect when a URL redirects to a known standard login/SSO portal. Instead of letting the browser crash or time out (resulting in generic execution context errors), the scanner should gracefully log the site status as "Authentication Required" or "Login Protected" and terminate the accessibility scan cleanly.

Start by tracing how accessibility_scan_status records execution_context_destroyed and page_frame_not_ready errors when a scanned URL redirects. Compare the redirect and authentication behavior described for idp.nwave.noaa.gov with the current scan flow; done means authentication-protected sites are logged as "Authentication Required" or "Login Protected" and the scan terminates cleanly.

Written by the indexing model from the issue text.