accessibility-plugin-react 2.0.0 → 2.0.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -1,6 +1,10 @@
1
- # Project status — 2026-10-13
1
+ # Project status — 2026-10-20
2
2
 
3
- **Local stabilization implemented and automatically verified; stable release not yet approved.** Stabilization was merged into `main` through PR #3 at `2893b6c`. No npm publication or release tag. The original stabilization foundation was `new-development` at `6dfbd44`; Clean light merged through [PR #16](https://github.com/prabothcharith/accessibility-react/pull/16) at `15e9465`. Movement and fixed actions are in [PR #17](https://github.com/prabothcharith/accessibility-react/pull/17) on `codex/movable-quick-actions`, not yet merged.
3
+ **Version 2 is published; human accessibility acceptance remains pending.** The
4
+ tested archive from `1d4ab1c` is published as `accessibility-plugin-react@2.0.0`
5
+ and documentation patch `2.0.1` is published under `latest`. The repository now
6
+ prepares `2.0.2` as a patch release with automatic stylesheet injection and automated
7
+ npm release workflows.
4
8
 
5
9
  ## Status categories
6
10
 
@@ -9,9 +13,9 @@
9
13
  | Implemented and verified | Provider-owned built-in/custom effects; reset cancellation; validated restoration; all fifteen controllers; combined filters; host style cleanup; dynamic child content; non-modal focus; portal layout; scoped CSS; React18/19 packed consumers; Next App/Pages and direct Server Component imports |
10
14
  | Implemented but unverified | Broader React19 patch versions, physical devices, assistive technologies and browser versions outside the executed matrix |
11
15
  | Partially implemented | Broad accessibility acceptance: automated keyboard/axe/reflow checks passed, real screen-reader/physical-device/actual zoom review remains. Host-wide integration: known filter/CSP/Shadow DOM/attribute-change limits remain. |
12
- | In progress | Movable trigger and fixed quick actions are implemented in PR #17; manual release acceptance remains pending. |
16
+ | In progress | Manual screen-reader, physical-device, actual-zoom, forced-colors and representative host acceptance remains pending. |
13
17
  | Planned | Large-DOM profiling, attribute/font-load refresh, explicit effect scopes and richer localization |
14
- | Blocked | Local macOS Firefox launch only (Linux coverage passed); npm rejected beta publication due to a temporary maintainer account suspension; stable human acceptance remains pending |
18
+ | Blocked | Local macOS Firefox launch only (Linux coverage passed); stable human acceptance remains pending |
15
19
  | Deferred | Multi-provider arbitration and live cross-tab sync |
16
20
  | Completed | Investigation/baseline, local P0 stabilization, feature regression suite, packed consumer/build verification, documentation, local example verification and full hosted CI meet their stated local acceptance criteria |
17
21
 
@@ -44,7 +48,7 @@ Expected error-path unit tests deliberately trigger missing-provider and duplica
44
48
 
45
49
  ## Merge and review state
46
50
 
47
- [PR #2](https://github.com/prabothcharith/accessibility-react/pull/2) merged stabilization into `new-development`; [PR #3](https://github.com/prabothcharith/accessibility-react/pull/3) merged the complete implementation into `main`. [Merged-main validation](https://github.com/prabothcharith/accessibility-react/actions/runs/38345207412) passed all jobs. PR #16 merged Clean light into main at `15e9465`; [that main run](https://github.com/prabothcharith/accessibility-react/actions/runs/38353340223) also passed all jobs. PR #17 is the movement follow-up awaiting review. No release tag or npm publication has occurred.
51
+ [PR #2](https://github.com/prabothcharith/accessibility-react/pull/2) merged stabilization into `new-development`; [PR #3](https://github.com/prabothcharith/accessibility-react/pull/3) merged the complete implementation into `main`. [Merged-main validation](https://github.com/prabothcharith/accessibility-react/actions/runs/38345207412) passed all jobs. PR #16 merged Clean light into main at `15e9465`; [that main run](https://github.com/prabothcharith/accessibility-react/actions/runs/38353340223) also passed all jobs. PR #17 and PR #18 are merged. Version 2 is published from the reviewed main archive; no Git release tag has been created.
48
52
 
49
53
  ## Hosted validation
50
54
 
@@ -63,7 +67,7 @@ The local suite now passes 61 tests. Font enlargement scales fixed line heights
63
67
  1. **Human accessibility testing pending:** VoiceOver/NVDA, physical touch devices, forced-colors visual review, browser zoom 200/400%. Automated axe and emulation do not establish WCAG conformance.
64
68
  2. **Local Firefox remains unavailable on this Mac.** The complete Firefox browser scenarios passed on Linux, so the local launch issue does not block automated release verification.
65
69
  3. **License resolved for this release:** on 2026-10-13 the owner confirmed authority to license all included code under ISC. LICENSE and package/lock metadata now agree on ISC. Historical GPL/ISC/MIT discrepancies remain recorded in baseline/migration evidence.
66
- 4. **Version 2 identity and channel approved:** the owner now selected `accessibility-plugin-react@2.0.0` under `latest`, superseding the unpublished beta candidate. npm maintainer authentication is verified. Registry latest remains 1.0.0 until a successful upload is independently confirmed; see RELEASE.md.
70
+ 4. **Version 2 identity and channel:** `accessibility-plugin-react@2.0.0` is published under `latest`, superseding the unpublished beta candidate. Registry metadata, integrity, clean React/Next consumers and the browser matrix were verified after npm's publish-time scan completed; see RELEASE.md.
67
71
  5. One provider per document, no live cross-tab sync, immutable definitions/storage configuration. Routes should share the provider.
68
72
  6. Effects target current-document HTML only; no Shadow DOM, iframe interiors, pseudo-elements or SVG/canvas text. Color filters alter host containing blocks. Late fonts/attribute-only style changes need a preference refresh. Very large/changing DOMs need application-specific profiling.
69
73
  7. Media hiding retains layout and does not stop playback. CSP may restrict inline styles/data cursors. No universal host compatibility claim.
@@ -76,11 +80,11 @@ The selected Clean light foundation adds scoped palette variables, decorative ic
76
80
 
77
81
  ## Movement and quick-action follow-up
78
82
 
79
- On PR #17 (movement source `d5e21df`), the trigger persists normalized drag/corner placement alongside display settings, with pointer-cancellation/activation guards and keyboard/click alternatives. Fixed header/footer controls and a keyboard action jump keep reset available without scrolling. Resetting display settings preserves placement; position reset is separate. Local validation: 66 unit tests and packed React18/React19/Next consumers passed; the final local browser matrix passed 46 tests with four intentional skips, including measured-size geometry, mouse/Chromium touch dragging, WebKit mobile taps, cancelled drags, 320px/short-screen fit, persistence and fixed-action checks. Hosted movement validation is tracked by PR #17 checks; it is separate from the earlier merged-main results. Human touch, screen-reader and actual zoom acceptance remains pending.
83
+ Merged through PR #17 (movement source `d5e21df`), the trigger persists normalized drag/corner placement alongside display settings, with pointer-cancellation/activation guards and keyboard/click alternatives. Fixed header/footer controls and a keyboard action jump keep reset available without scrolling. Resetting display settings preserves placement; position reset is separate. Local validation: 66 unit tests and packed React18/React19/Next consumers passed; the final local browser matrix passed 46 tests with four intentional skips, including measured-size geometry, mouse/Chromium touch dragging, WebKit mobile taps, cancelled drags, 320px/short-screen fit, persistence and fixed-action checks. Hosted movement validation is tracked by PR #17 checks; it is separate from the earlier merged-main results. Human touch, screen-reader and actual zoom acceptance remains pending.
80
84
 
81
85
  ## Release tracking
82
86
 
83
- [Project #18](https://github.com/users/prabothcharith/projects/18) and [tracker #15](https://github.com/prabothcharith/accessibility-react/issues/15) hold the first stable release gates. Documentation correction [#9](https://github.com/prabothcharith/accessibility-react/issues/9) is addressed in PR #17. Owner licensing/identity decisions (#4/#5), human acceptance (#6–#8), final candidate checks (#10) and explicitly authorized publication/registry verification (#11) remain required. Build artifacts and merged implementation do not establish registry availability.
87
+ [Project #18](https://github.com/users/prabothcharith/projects/18) and [tracker #15](https://github.com/prabothcharith/accessibility-react/issues/15) track the remaining release work. Owner licensing/identity decisions (#4/#5), documentation correction (#9), final automated candidate checks and npm publication are complete. Human acceptance (#6–#8) and any separately authorized Git tag/GitHub release remain outstanding.
84
88
 
85
89
  ## npm identity follow-up
86
90
 
@@ -93,3 +97,9 @@ Owner-approved ISC beta source `cf4348b` passed [full hosted validation](https:/
93
97
  ## Version 2 channel selection
94
98
 
95
99
  The owner requested 2.0.0 without beta on 2026-10-13. Package/lock version and publishConfig now use 2.0.0/latest; README and migration instructions match. This is explicit publication authorization despite the remaining documented human acceptance checks. The earlier account suspension is a registry blocker independent of version choice. Publication results will be recorded after the retry.
100
+
101
+ ## Published version 2
102
+
103
+ The owner authorized merging PR #17 and PR #18 and dispatching publication. Main commit `1d4ab1c` contains package version 2.0.0, ISC and latest publishConfig. [Pre-merge final validation](https://github.com/prabothcharith/accessibility-react/actions/runs/38359055736) passed all jobs. After the trusted-publisher connection was saved, the failed publish job in [Action 38359604307](https://github.com/prabothcharith/accessibility-react/actions/runs/38359604307) was rerun on 2026-10-16. npm accepted the checksum-verified archive through OIDC.
104
+
105
+ The action's immediate registry check raced npm's publish-time malware scan and therefore remained red even though upload succeeded. After the scan completed, registry metadata reported 2.0.0/latest with ISC and integrity `sha512-CQFzF0pNl/bb+YVauI35+GNK2PIgk4qoh8+PnEkj1HAeW2lLMM/LTV5fq0tigNRnmPVX0M7rpYR4XPo820CQWw==`. Clean public-registry React18, React19/Tailwind and Next16 consumers passed declarations, ESM/CJS, SSR and production builds. The registry-installed browser matrix passed 55 tests with five intentional Next-only skips across Chromium, Firefox, WebKit and mobile WebKit. Workflow follow-up adds propagation-aware verification; no Git release tag was created.
package/docs/RELEASE.md CHANGED
@@ -1,11 +1,17 @@
1
- # npm release candidate — 2026-10-13
1
+ # npm release and verification — updated 2026-10-21
2
+
3
+ ## 2.0.2 patch release
4
+
5
+ Version `2.0.2` is a patch release containing automatic widget stylesheet injection,
6
+ workflow automation for npm publication on pull request merges to `main`, and
7
+ synchronized release metadata.
2
8
 
3
9
  ## Identity and current state
4
10
 
5
11
  - Owner-selected package: `accessibility-plugin-react` (same existing npm package).
6
- - Registry snapshot: `latest=1.0.0`; sole published version 1.0.0; maintainer `praboth`.
7
- - Owner-approved candidate: `2.0.0`, npm tag `latest`. The owner explicitly selected publication without beta.
8
- - Source branch: `codex/npm-v2-release`, based on the movement/fixed-actions PR #17 head. No publication, release tag or main merge performed by this preparation.
12
+ - Registry state before this release: `latest=2.0.1`; published versions 1.0.0, 2.0.0 and 2.0.1; maintainer `praboth`.
13
+ - Current candidate: `2.0.2`, npm tag `latest`.
14
+ - Published source for 2.0.0: main commit `1d4ab1c`, containing the merged movement/fixed-actions and version 2 release work. The v2.0.0 Git tag now exists; no GitHub release was created.
9
15
  - ISC is owner-approved for all included code as of 2026-10-13; LICENSE and package/lock metadata agree. Published 1.0.0 metadata says ISC and its README says MIT; historical inconsistency is retained in migration evidence.
10
16
  - npm CLI authentication as package maintainer `praboth` is verified. Credentials/2FA remain outside repository files and chat.
11
17
 
@@ -32,7 +38,7 @@ Build and inspect a reviewable archive outside the checkout:
32
38
  ```sh
33
39
  npm run build
34
40
  npm pack --pack-destination /tmp
35
- npm publish /tmp/accessibility-plugin-react-2.0.0.tgz --dry-run --tag latest --access public
41
+ npm publish /tmp/accessibility-plugin-react-2.0.2.tgz --dry-run --tag latest --access public
36
42
  ```
37
43
 
38
44
  ## Executed candidate checks
@@ -53,10 +59,12 @@ npm whoami
53
59
  The owner selected the candidate version/channel, resolved licensing and authorized version 2 publication on 2026-10-13. Upload the exact verified archive using:
54
60
 
55
61
  ```sh
56
- npm publish /tmp/accessibility-plugin-react-2.0.0.tgz --tag latest --access public
62
+ npm publish /tmp/accessibility-plugin-react-2.0.2.tgz --tag latest --access public
57
63
  ```
58
64
 
59
- The package's approved publishConfig uses latest. Successful publication makes 2.0.0 the default npm install target. The major API requires migration; see MIGRATION.md. No Git release tag or main merge is authorized by this preparation.
65
+ The package's approved publishConfig uses latest. Successful publication makes
66
+ 2.0.2 the default npm install target. Verify the registry package and clean
67
+ consumer installs before creating an authorized release tag.
60
68
 
61
69
  After upload, verify registry name/version/license and latest tag, archive integrity, and clean registry installations in the React/Next consumers. Record the published version and source commit only after those checks succeed.
62
70
 
@@ -70,13 +78,19 @@ After npm browser authentication, publication was rejected with E403: the mainta
70
78
 
71
79
  The owner subsequently selected 2.0.0 under latest. The registry account hold is independent of release version; record the version 2 retry result separately. The hold duration is unknown; no automatic retry is scheduled. License/identity issues #4 and #5 are resolved; publication and stable human acceptance remain open.
72
80
 
73
- ## Version 2 retry
81
+ ## Historical version 2 retry
74
82
 
75
83
  The owner requested export/publication as 2.0.0 without beta on 2026-10-13. Package/lock metadata and publishConfig were changed to 2.0.0/latest, and a new archive is prepared for verification and upload. The earlier beta integrity above applies only to that unpublished beta artifact. Until successful registry verification, 2.0.0 is not claimed as published.
76
84
 
77
85
  ## GitHub Actions publication
78
86
 
79
- The owner requested a GitHub Actions publishing route for 2.0.0/latest. `.github/workflows/publish.yml` is manually dispatched, defaults to dry-run, validates the exact committed name/version/ISC/latest metadata, runs source/packed-consumer/full Linux browser/audit checks, and uploads the tested archive with its SHA512 checksum. The publishing job downloads that archive and uses npm trusted publishing (OIDC), then verifies registry integrity/latest and clean React18/React19/Next registry consumers. No npm token or automatic push/tag publication is configured.
87
+ `.github/workflows/publish.yml` publishes releases through npm trusted publishing (OIDC). It is triggered automatically when commits are pushed to `main` (such as when a pull request is merged) or manually via `workflow_dispatch`.
88
+
89
+ When triggered on `main`, the workflow inspects the committed `package.json` version:
90
+
91
+ - If the version is already published on npm, publishing is safely skipped without failing the run.
92
+ - If the version is new, it validates the exact committed metadata, executes source/packed-consumer/Linux browser/audit checks, packages and signs the archive with SHA512 checksums, publishes via npm OIDC, and verifies registry integrity and clean React18/React19/Next registry consumers.
93
+ - Manual dispatches remain available with optional `dry_run` inspection.
80
94
 
81
95
  Configure npm’s trusted publisher for package accessibility-plugin-react:
82
96
 
@@ -97,11 +111,43 @@ Browser/2FA authorization may be required. Trusted publishing requires compatibl
97
111
  GitHub requires workflow_dispatch workflows to exist on the default branch. PR #17 supplies movement and PR #18 supplies the npm identity/release workflow; merge #17, retarget #18 to main, and merge it after owner authorization. Then run:
98
112
 
99
113
  ```sh
100
- gh workflow run publish.yml --ref main -f version=2.0.0 -f dry_run=true
114
+ gh workflow run publish.yml --ref main -f version=2.0.2 -f dry_run=true
101
115
  # Authorized real publication:
102
- gh workflow run publish.yml --ref main -f version=2.0.0 -f dry_run=false
116
+ gh workflow run publish.yml --ref main -f version=2.0.2 -f dry_run=false
103
117
  ```
104
118
 
105
119
  References: [npm trusted publishing](https://docs.npmjs.com/trusted-publishers/), [npm trust CLI](https://docs.npmjs.com/cli/v11/commands/npm-trust/), [GitHub manual workflow requirements](https://docs.github.com/en/actions/how-tos/manage-workflow-runs/manually-run-a-workflow). Do not report successful publication until the registry and consumer steps succeed.
106
120
 
107
121
  Local version 2 preparation checks passed: 66 unit tests, type/lint/format/build/archive validation, and packed React18/React19/Next consumer builds. The publication workflow passed actionlint 1.7.12; malformed registry-consumer versions are rejected before installation. The workflow itself has not been dispatched; main-branch availability and npm trusted-publisher setup are still required.
122
+
123
+ ## GitHub Actions attempt — 2026-10-13
124
+
125
+ PR #17 and PR #18 were merged with owner authorization; main is 1d4ab1c. [Publication Action 38359604307](https://github.com/prabothcharith/accessibility-react/actions/runs/38359604307) ran with version=2.0.0 and dry_run=false. Its validate job passed, preserved the tested archive, and the publishing job verified the archive checksum. Upload then failed with npm E404/permission denial. The trusted-publisher connection had not been saved: both CLI and browser setup were rejected, with the browser explicitly showing the temporary account-suspension notice. Registry checks still found only 1.0.0/latest; version 2.0.0 is not published.
126
+
127
+ At the owner's request, a fresh GitHub trusted-publisher form was filled in Chrome with user prabothcharith, repository accessibility-react, workflow publish.yml, no environment and Allow npm publish enabled. It is awaiting the owner's Set up connection/security-key authorization. A filled form is not a saved trusted connection. Once the connection is successfully saved and npm permits publication, rerun the failed publishing job to reuse the validated artifact:
128
+
129
+ ```sh
130
+ gh run rerun 38359604307 --failed
131
+ ```
132
+
133
+ Verify registry metadata/integrity/latest and registry consumers before reporting success. No further retry is automatic.
134
+
135
+ ## Successful version 2 publication — 2026-10-16
136
+
137
+ The owner saved the npm trusted-publisher connection for `prabothcharith/accessibility-react` and `publish.yml`, then authorized the publication retry. The failed publish job in [Action 38359604307](https://github.com/prabothcharith/accessibility-react/actions/runs/38359604307) reused the archive previously validated from main commit `1d4ab1c`. Its SHA512 checksum check passed and npm accepted `accessibility-plugin-react@2.0.0` through OIDC under `latest`.
138
+
139
+ The workflow queried the registry immediately and received a temporary 404 while npm's publish-time malware scan was still processing the tarball. After the scan completed, independent checks confirmed version/latest/ISC metadata and integrity `sha512-CQFzF0pNl/bb+YVauI35+GNK2PIgk4qoh8+PnEkj1HAeW2lLMM/LTV5fq0tigNRnmPVX0M7rpYR4XPo820CQWw==`. Clean installs from the public registry passed React18, React19/Tailwind and Next16 declaration checks, ESM/CommonJS loading, SSR and production builds. The installed-package browser matrix passed 55 tests with five intentional Next-only skips across Chromium, Firefox, desktop WebKit and mobile WebKit.
140
+
141
+ The workflow follow-up retries registry verification for the expected npm scan delay and supports Windows validation. Human screen-reader, physical-device, actual-zoom, forced-colors and representative host acceptance remain pending. Publication did not authorize or create a Git tag/GitHub release.
142
+
143
+ ## GitHub Packages and GitHub release
144
+
145
+ The public npm package remains `accessibility-plugin-react`. The same 2.0.0
146
+ archive is also published to GitHub Packages under the required scoped name
147
+ `@prabothcharith/accessibility-react` through
148
+ `.github/workflows/publish-github-package.yml`. The workflow creates a scoped
149
+ manifest only in its release staging directory, so the repository package name
150
+ and public npm package are unchanged.
151
+
152
+ The GitHub release is tagged `v2.0.0` from the validated `main` commit after
153
+ the GitHub Packages verification succeeds.
package/docs/ROADMAP.md CHANGED
@@ -2,21 +2,21 @@
2
2
 
3
3
  No deadlines or percentage-complete estimates. Status is based on current evidence in PROJECT_STATUS.md.
4
4
 
5
- | Phase | Priority | Objective / tasks | Dependencies | Acceptance / deliverables | Risk / status |
6
- | --------------------------- | -------- | -------------------------------------------------------------------------------------------------------- | -------------------------------------- | ----------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------- |
7
- | Investigation | P0 | Compare vanilla/main/development/new-development, PR #1, history; baseline all checks | Git/registry access | Evidence-backed baseline and parity matrix | Completed locally |
8
- | Core stabilization | P0 | Provider effects, filter composition, independent storage, reset cancellation, no invisible hit area | Baseline | Close/reopen, reset race, restore, dynamic content and cleanup regressions | Implemented; local automated verification |
9
- | Features and extension | P1 | All fifteen controllers, missing original variants, safe custom apply contract | Core | Per-feature bounds/states and custom restore/reset/unmount tests; public examples | Implemented; host-specific effect limits documented |
10
- | Accessibility/UI | P1 | Non-modal semantics, names/focus, safe-area responsive CSS, motion preferences | Core | Keyboard/browser/axe checks plus human SR, actual zoom and device review | Automated checks implemented; human review remains |
11
- | Packaging/frameworks | P1 | Client boundary, ESM/CJS/types/CSS, React 18/19, Next App/Pages, built examples | Core + build | Clean tarball installs, production builds and runtime tests | Local and hosted consumer verification passed; complete Firefox coverage passed on Linux |
12
- | CI/release validation | P1 | Execute hosted matrix; fix Firefox launch environment; record results | Push/PR workflow and compatible runner | Passing Node22/24 jobs and full browser matrix on exact release commit | Completed: hosted Node22/24 and full Chromium/Firefox/WebKit/mobile matrix passed |
13
- | Clean light base design | P1 | Apply owner-selected light concept, icons, tokens and responsive rows | Stabilized core | Browser/axe/target-size checks, actual runtime screenshots and documented overrides | Merged through PR #16; local and hosted checks passed |
14
- | Movement and quick actions | P1 | Persist drag/corner placement, non-drag controls and fixed reset/footer | Clean light foundation | Drag/cancel/reload/resize and pinned-action browser regressions | In PR #17; 66 unit and 46 local browser checks passed |
15
- | Ownership/release | P1 | Continue confirmed npm identity; resolve license; choose version; approve merge/tag/publish | Owner decision + all gates | Traceable authorized release with clean registry install | Beta name/version/ISC approved; stable human acceptance remains |
16
- | Performance/dynamic styling | P2 | Benchmark large documents; incremental observation; attribute/font-load refresh | Real host profiles | Measured budgets, no redundant work, style-change regression tests | Planned; current child-list/resize path works |
17
- | Host effects hardening | P2 | Optional explicit effect scopes, CSP renderer, Shadow DOM strategy, fixed-descendant filter alternatives | API design and real use cases | Documented contract with package/browser tests | Planned; avoid universal-host compatibility claims |
18
- | UX enhancements | P2 | Richer per-control labels and localization polish | Stable core + accessibility review | Pointer/touch/keyboard equivalence, no activation regressions | Planned after current design/movement work |
19
- | Multi-instance/cross-tab | P2 | Decide if needed; deterministic arbitration/synchronization | Usage evidence | Isolated lifetime, persistence and interaction tests | Deferred; one provider/document enforced |
5
+ | Phase | Priority | Objective / tasks | Dependencies | Acceptance / deliverables | Risk / status |
6
+ | --------------------------- | -------- | -------------------------------------------------------------------------------------------------------- | -------------------------------------- | ----------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------- |
7
+ | Investigation | P0 | Compare vanilla/main/development/new-development, PR #1, history; baseline all checks | Git/registry access | Evidence-backed baseline and parity matrix | Completed locally |
8
+ | Core stabilization | P0 | Provider effects, filter composition, independent storage, reset cancellation, no invisible hit area | Baseline | Close/reopen, reset race, restore, dynamic content and cleanup regressions | Implemented; local automated verification |
9
+ | Features and extension | P1 | All fifteen controllers, missing original variants, safe custom apply contract | Core | Per-feature bounds/states and custom restore/reset/unmount tests; public examples | Implemented; host-specific effect limits documented |
10
+ | Accessibility/UI | P1 | Non-modal semantics, names/focus, safe-area responsive CSS, motion preferences | Core | Keyboard/browser/axe checks plus human SR, actual zoom and device review | Automated checks implemented; human review remains |
11
+ | Packaging/frameworks | P1 | Client boundary, ESM/CJS/types/CSS, React 18/19, Next App/Pages, built examples | Core + build | Clean tarball installs, production builds and runtime tests | Local and hosted consumer verification passed; complete Firefox coverage passed on Linux |
12
+ | CI/release validation | P1 | Execute hosted matrix; fix Firefox launch environment; record results | Push/PR workflow and compatible runner | Passing Node22/24 jobs and full browser matrix on exact release commit | Completed: hosted Node22/24 and full Chromium/Firefox/WebKit/mobile matrix passed |
13
+ | Clean light base design | P1 | Apply owner-selected light concept, icons, tokens and responsive rows | Stabilized core | Browser/axe/target-size checks, actual runtime screenshots and documented overrides | Merged through PR #16; local and hosted checks passed |
14
+ | Movement and quick actions | P1 | Persist drag/corner placement, non-drag controls and fixed reset/footer | Clean light foundation | Drag/cancel/reload/resize and pinned-action browser regressions | Merged through PR #17; local and full hosted checks passed |
15
+ | Ownership/release | P1 | Continue confirmed npm identity; resolve license; choose version; approve merge/tag/publish | Owner decision + all gates | Traceable authorized release with clean registry install | 2.0.0/latest published and registry consumers verified; Git tag and human acceptance remain separate |
16
+ | Performance/dynamic styling | P2 | Benchmark large documents; incremental observation; attribute/font-load refresh | Real host profiles | Measured budgets, no redundant work, style-change regression tests | Planned; current child-list/resize path works |
17
+ | Host effects hardening | P2 | Optional explicit effect scopes, CSP renderer, Shadow DOM strategy, fixed-descendant filter alternatives | API design and real use cases | Documented contract with package/browser tests | Planned; avoid universal-host compatibility claims |
18
+ | UX enhancements | P2 | Richer per-control labels and localization polish | Stable core + accessibility review | Pointer/touch/keyboard equivalence, no activation regressions | Planned after current design/movement work |
19
+ | Multi-instance/cross-tab | P2 | Decide if needed; deterministic arbitration/synchronization | Usage evidence | Isolated lifetime, persistence and interaction tests | Deferred; one provider/document enforced |
20
20
 
21
21
  Release gates are not satisfied by checking in tests or CI configuration. Execute them on the final candidate. A local Chromium/WebKit pass is not a Firefox pass, and an axe pass is not screen-reader or WCAG certification.
22
22
 
@@ -27,3 +27,5 @@ The owner confirmed `accessibility-plugin-react` as the registry identity on 202
27
27
  Final ISC beta source cf4348b passed the full hosted matrix. npm rejected the upload due to a temporary account suspension; 2.0.0-beta.1 is not published. Owner decision issues #4/#5 are closed; publication #11 and human stable-release acceptance remain open. See RELEASE.md.
28
28
 
29
29
  The owner subsequently chose 2.0.0 under latest instead of beta. Current release preparation follows that instruction; human accessibility acceptance remains documented as pending. Earlier beta preparation/hold notes above are historical; see RELEASE.md for the current version and publication result.
30
+
31
+ PR #17/#18 are merged into main at `1d4ab1c`. The trusted GitHub publisher uploaded the reviewed archive as `accessibility-plugin-react@2.0.0` under `latest` on 2026-10-16, and clean registry consumers passed after npm's publish-time scan completed. No Git tag/GitHub release was authorized or created. See RELEASE.md for the exact evidence and the remaining human-acceptance work.
@@ -1,25 +1,25 @@
1
1
  # Troubleshooting
2
2
 
3
- | Symptom | Check / resolution |
4
- | ------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
5
- | Widget unstyled | Import `accessibility-plugin-react/style.css` once. Inspect packed CSS, not source Tailwind directives. No consumer Tailwind configuration is required. |
6
- | “useAccessibility must be used within…” | Put custom control below AccessibilityPlugin and import from the same installed package copy. Check npm ls react/react-dom for duplication. |
7
- | “Only one AccessibilityPlugin…” | Mount one provider at the persistent app/layout root; do not mount another in each route. Different persistence keys do not permit competing global effect owners. |
8
- | Changing storage key throws | Remount with React `key`; persistence identity is intentionally immutable. |
9
- | No effect after installing registry version | These changes are unreleased. Install the local packed archive or verified owner-approved release, not an assumed npm version. |
10
- | Hydration warnings | Use the built distribution with preserved client directive. Put custom hooks/effect functions in a Client Component. Avoid conditional browser globals in render. Check host hydration independently. |
11
- | Preference appears after first paint | Storage restores client-side after hydration. A brief default paint is expected; no flash-free SSR claim is made. |
12
- | Gray makes saturation look ineffective | Grayscale is applied last. Turn it off to see retained saturation. |
13
- | Fixed host element moves when filters enabled | CSS filters create containing blocks/stacking contexts. Test your host's fixed descendants; this browser behavior is an integration limitation. The widget itself is portaled outside the filtered roots. |
14
- | Text fails to refresh after theme/font/style change | Child insertion and window resize are observed; pure class/style attribute changes and late font-load metrics are not. Toggle the preference to remeasure. Avoid multiple systems writing the same property. |
15
- | iframe/Shadow DOM content unchanged | Only HTML in the current document is processed. Shadow roots, iframe interiors, SVG/canvas text, pseudo-elements and raw text nodes directly under body are outside scope. |
16
- | Hidden video still audible | Visibility is not playback control. Pause/mute through your application's player. Only recognized video embeds are hidden; maps/documents remain. |
17
- | Custom reset changes UI but not page | Move DOM changes from event handlers to the hook's apply callback with cleanup. For ordinary React effects use value as a dependency and restore prior styles. |
18
- | Removed control's effect persists | Intentional provider ownership. Reset before removing a feature, or reset globally. Remount provider to change the feature set/definitions. |
19
- | Storage unavailable or full | Widget stays usable in memory. There is no server sync. Keep custom values small and JSON-compatible; set persist=false if needed. |
20
- | Preferences differ across tabs | No live cross-tab synchronization. The last write controls the next restoration. |
21
- | CSP blocks styling or cursor | Built-ins use inline style properties and an SVG data cursor. Test your actual CSP; there is no nonce-based stylesheet renderer in this release. Native cursor fallback remains. |
22
- | Extremely large/changing pages are slow | Active text/media effects traverse the document on relevant child mutations. Profile your real page; no universal large-DOM performance promise. |
23
- | Firefox Playwright launch fails before loading the page | On the validation Mac, Firefox 157 build 1555 exited “Could not find profile folder”, including with TMPDIR=/tmp. This is a local environment failure. Full Firefox integration passed on the Linux CI runner; the local launch issue remains reproducible. |
3
+ | Symptom | Check / resolution |
4
+ | ------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
5
+ | Widget unstyled | Ensure the package is imported in the browser bundle. It automatically injects its scoped CSS; applications using an explicit CSS pipeline can load `accessibility-plugin-react/style.css`. Inspect packed CSS, not source Tailwind directives. No consumer Tailwind configuration is required. |
6
+ | “useAccessibility must be used within…” | Put custom control below AccessibilityPlugin and import from the same installed package copy. Check npm ls react/react-dom for duplication. |
7
+ | “Only one AccessibilityPlugin…” | Mount one provider at the persistent app/layout root; do not mount another in each route. Different persistence keys do not permit competing global effect owners. |
8
+ | Changing storage key throws | Remount with React `key`; persistence identity is intentionally immutable. |
9
+ | No effect after installing registry version | Confirm the installed version with `npm ls accessibility-plugin-react` and verify the packed/registry archive rather than importing repository source. Applications using an explicit CSS pipeline should also verify the `accessibility-plugin-react/style.css` load. |
10
+ | Hydration warnings | Use the built distribution with preserved client directive. Put custom hooks/effect functions in a Client Component. Avoid conditional browser globals in render. Check host hydration independently. |
11
+ | Preference appears after first paint | Storage restores client-side after hydration. A brief default paint is expected; no flash-free SSR claim is made. |
12
+ | Gray makes saturation look ineffective | Grayscale is applied last. Turn it off to see retained saturation. |
13
+ | Fixed host element moves when filters enabled | CSS filters create containing blocks/stacking contexts. Test your host's fixed descendants; this browser behavior is an integration limitation. The widget itself is portaled outside the filtered roots. |
14
+ | Text fails to refresh after theme/font/style change | Child insertion and window resize are observed; pure class/style attribute changes and late font-load metrics are not. Toggle the preference to remeasure. Avoid multiple systems writing the same property. |
15
+ | iframe/Shadow DOM content unchanged | Only HTML in the current document is processed. Shadow roots, iframe interiors, SVG/canvas text, pseudo-elements and raw text nodes directly under body are outside scope. |
16
+ | Hidden video still audible | Visibility is not playback control. Pause/mute through your application's player. Only recognized video embeds are hidden; maps/documents remain. |
17
+ | Custom reset changes UI but not page | Move DOM changes from event handlers to the hook's apply callback with cleanup. For ordinary React effects use value as a dependency and restore prior styles. |
18
+ | Removed control's effect persists | Intentional provider ownership. Reset before removing a feature, or reset globally. Remount provider to change the feature set/definitions. |
19
+ | Storage unavailable or full | Widget stays usable in memory. There is no server sync. Keep custom values small and JSON-compatible; set persist=false if needed. |
20
+ | Preferences differ across tabs | No live cross-tab synchronization. The last write controls the next restoration. |
21
+ | CSP blocks styling or cursor | Built-ins use inline style properties and an SVG data cursor. Test your actual CSP; there is no nonce-based stylesheet renderer in this release. Native cursor fallback remains. |
22
+ | Extremely large/changing pages are slow | Active text/media effects traverse the document on relevant child mutations. Profile your real page; no universal large-DOM performance promise. |
23
+ | Firefox Playwright launch fails before loading the page | On the validation Mac, Firefox 157 build 1555 exited “Could not find profile folder”, including with TMPDIR=/tmp. This is a local environment failure. Full Firefox integration passed on the Linux CI runner; the local launch issue remains reproducible. |
24
24
 
25
25
  For a bug report, include package/build SHA, React/framework/browser/OS versions, a small reproducible application, selected settings, host CSS and whether the actual tarball reproduces it. Do not include private stored preferences or credentials. See baseline and project status for known issues rather than relying on historical completion claims.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "accessibility-plugin-react",
3
- "version": "2.0.0",
3
+ "version": "2.0.2",
4
4
  "description": "A composable React display-preference widget with a clean light design, persistent settings and movable accessible controls.",
5
5
  "main": "dist/index.js",
6
6
  "module": "dist/index.mjs",