/**
 * Run axe against a subtree, now.
 *
 * The a11y addon audits a story **once**, in an `afterEach` that
 * fires when `run()` resolves — i.e. immediately after the first
 * paint. That was enough while the assertions lived in `play`,
 * because the addon's hook ran after the play had finished driving.
 * With the tests split out, `run()` returns before a test has
 * clicked anything, so the states that most need auditing — an open
 * dialog, a shown popover, a selected tab panel — would never be
 * seen by axe at all.
 *
 * So a driven state audits itself explicitly. The rule set is left
 * at axe's default, matching the addon, except that `region` is
 * disabled for the same reason the addon disables it: a component
 * mounted on its own is not a page and owes nobody a landmark.
 */
export declare const expectNoAxeViolations: (element: Element) => Promise<void>;
//# sourceMappingURL=expectNoAxeViolations.testHelpers.d.ts.map