Accessible Fieldset & Legend Grouping Auditor

Use this package to review supplied group structure before changing or publishing a form. It does not inspect your site.

PRESERVE-WHAT-WORKS

Preserve first. This audit changes nothing by itself. Installation is not authorization to redesign, restyle, reorganize, replace, or materially alter any existing page, route, form, branding, layout, content, mobile behavior, accessibility behavior, SEO, analytics, authentication, checkout, integration, database, API, or unrelated feature.

Create a source-control checkpoint and record the current deploy artifact. Touch only a narrow evidence adapter and, after confirmed review, the smallest form-group owner. Avoid global CSS, broad selectors, theme resets, homepage or navigation changes, layout rewrites, and unrelated component replacement. If a fix requires wider structural or visual change, stop and label PRESERVATION CONFLICT / REVIEW REQUIRED; use the smallest compatible alternative.

1. Verify the package

npm test

2. Run the example

node examples/basic.mjs

3. Build a minimal adapter

Supply opaque group, control, and instruction IDs plus structural facts. Exclude field values, payment data, addresses, names, email addresses, and instruction copy.

4. Review, implement, and test

Resolve errors first, investigate warnings and review findings in context. Run adapter fixtures, affected-form tests, keyboard and name/role/state checks, validation and submission tests, responsive/zoom checks, required browser and assistive-technology checks, and unrelated critical-journey regressions. The live DOM, visual result, assistive-technology behavior, submissions, and production environment remain unverified until those checks pass.

5. Recover or publish

If integration fails, remove the adapter or restore the checkpoint; never auto-apply the remediation plan. Follow ROLLBACK.md and rerun targeted and regression tests. Publish only after the bounded change, real-host verification, monitoring, and rollback path pass.

Boundary: a valid report is only evidence that the supplied model triggered no packaged rule. It is not proof of WCAG conformance or production accessibility.