storybook-addon-accessibility-checker doesn't install

[wkeese]

Describe the bug

You've listed the Storybook dependency as ^9.2.0, but no such Storybook version exists (although there is a 9.2.0 alpha version). Why not list storybook V10 as a peerDependency, or >= 9.0.0 etc.?

BTW, https://www.npmjs.com/package/storybook-addon-accessibility-checker is confusing. Is your package called storybook-addon-accessibility-checker, or is it called storybook-addon-a11y, or is it called @storybook/addon-a11y?

The install problem happens with storybook-addon-accessibility-checker@9.2.0-rc.4.

To Reproduce

% npm i storybook-addon-accessibility-checker
npm warn ERESOLVE overriding peer dependency
npm warn While resolving: storybook-addon-accessibility-checker@9.2.0-rc.4
npm warn Found: storybook@undefined
npm warn node_modules/storybook
npm warn
npm warn Could not resolve dependency:
npm warn peer storybook@"^9.2.0" from storybook-addon-accessibility-checker@9.2.0-rc.4
npm warn node_modules/storybook-addon-accessibility-checker
npm warn   storybook-addon-accessibility-checker@"*" from the root project
npm error code ETARGET
npm error notarget No matching version found for storybook@^9.2.0.
npm error notarget In most cases you or one of your dependencies are requesting
npm error notarget a package version that doesn't exist.
npm error A complete log of this run can be found in: /Users/bill/.npm/_logs/2026-01-27T02_57_42_137Z-debug-0.log

Expected behavior
Install works.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: Mac

Definition of Done

• Design artifacts reviewed
• Work item implemented
• Automated test case created (when applicable)
• Unit test completed
• Run Checker (when applicable)
• Manual and Screen Reader Testing (when applicable)
• Video recording of user experience walkthrough (if impact to UX)
• PR created

[tombrunet]

This is built as a fork of storybook and not intended to be its own standalone plugin forever (hence the naming in the docs and the version oddity). We've had some conversations with the storybook team, but I need to follow up with them.