First stable release: acceptance and publication tracker #15

Track the first stable release of the React accessibility library. The implementation is merged into main; this tracker separates verified work from pending release acceptance. No fixed version, deadline, publication or tag is implied.

Completed implementation

• Stabilized compound API, all fifteen controllers, provider-owned effects, persistence/reset and custom extension contract: PR Stabilize accessibility preferences, compound controls and package integration #2.
• Integrated the complete library into main: PR Introduce the stabilized React accessibility library with tests and documentation #3, commit 2893b6c.
• Node 22/24 validation, archive consumers and full browser CI on merged main: passing run. 61 unit tests and 37 browser passes, five intentional skips.
• Examples, architecture/API/parity/migration documentation and release procedure.

Release acceptance sequence

• Resolve the historical GPL/ISC licensing conflict #4
• Confirm npm package identity, ownership and release version #5
• Complete screen-reader accessibility acceptance #6
• Verify physical devices, actual zoom and visual accessibility #7
• Complete representative host-application acceptance #8
• Update documentation to reflect the merged main implementation #9
• Validate and prepare the final release candidate #10
• Publish the approved package and verify the registry release #11

Licensing and package identity are owner decisions. Manual screen-reader/device/zoom/host checks can run alongside documentation updates. Final candidate validation depends on those gates. Publication depends on candidate sign-off and separate explicit authorization.

Later enhancements (outside this milestone)

• Profile large documents and refresh late font/style changes #12
• Design scoped effects and stronger host compatibility #13
• Improve localization and optional widget positioning controls #14

Deferred pending usage evidence: multiple-provider arbitration and live cross-tab synchronization.

Acceptance: every release-gate sub-issue has recorded evidence, no known P0 defect remains, and any publication/tag actions are separately authorized and verified. An automated axe pass is not a WCAG certification.