The core capability
The most important pages are behind a login.
Account settings, dashboards, checkout, admin panels: the pages where accessibility failures hurt users most are exactly the pages external scanners never see.
Why crawlers fall short
A crawl-based scanner starts from your homepage and follows links. The moment a page requires a session, a role, a filled cart, or a multi-step form, the crawler stops. Vendors work around this with stored credentials and scripted logins, which breaks the first time your client changes their auth flow, and means handing production credentials to a third party.
The extension approach
Complaudax audits the page you are looking at, in the session you already have. Log in as a real user, navigate to step 3 of checkout, open the side panel, and audit. The state is exactly what a real user experiences, including modals, expanded menus, and error messages that only appear after interaction.
What about sensitive content?
Audits of authenticated pages capture rule findings and element selectors, not your client's data. Text content is redacted before anything leaves the browser. The details are on the security page.
Staging counts too
The same applies to staging and preview environments behind VPNs or basic auth. If your browser can render it, Complaudax can audit it. That means accessibility gets checked before release, not discovered after. There is a full walkthrough in the guide on auditing staging sites.