Skip to content

fix(frame): self-configure engine rules when the run command arrives - #294

Open
Aaryan430 wants to merge 2 commits into
mainfrom
fix/frame-self-configure-engine-rules
Open

fix(frame): self-configure engine rules when the run command arrives#294
Aaryan430 wants to merge 2 commits into
mainfrom
fix/frame-self-configure-engine-rules

Conversation

@Aaryan430

@Aaryan430 Aaryan430 commented Aug 24, 2026

Copy link
Copy Markdown
Collaborator

No description provided.

Aaryan430 and others added 2 commits August 24, 2026 10:04
Frames register a11y-engine rules via the one-shot CONFIGURE_A11YENGINE
broadcast. A frame created after the broadcast, or whose window listeners
were wiped by a document.write() rewrite (GPT ad creatives), keeps
answering axe.ping/axe.start with a default audit and fails the whole run
in normalizeRunOptions with 'unknown rule `fieldset-missing-legend` in
options.rules'.

The engine bundle in every frame already holds the rules and checks, and
options.a11yEngineConfig already carries the engine flags with axe.start.
Call a11yEngine.ensureConfigured(options) (added in a11y-engine-core)
before running rules so the frame registers its engine rules from the
config that travels with the command — no broadcast or listener
dependency. Guarded no-op when the engine bundle is absent or the audit
is already configured.

Companion PR: browserstack/a11y-engine (a11yEngine.ensureConfigured).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants