A11y: Improve test runner recipe

[shilman]

Closes N/A

What I did

Also reuse the a11y addon's custom element selector on the test runner, if the user has set it.

Checklist for Contributors

Testing

Manual testing

Did not manual test, but should be simple enough to create a story with a custom element selector and run it in the test runner.

🦋 Canary release

This PR does not have a canary release associated. You can request a canary release of this pull request by mentioning the @storybookjs/core team here.

core team members can create a canary release here or locally with gh workflow run --repo storybookjs/storybook canary-release-pr.yml --field pr=<PR_NUMBER>

Greptile Summary

This change enhances the accessibility testing configuration in the Storybook test runner by allowing custom element selectors in story parameters.

• Added support for custom element selectors in docs/_snippets/test-runner-a11y-configure.md
• Improved flexibility for targeting specific elements in accessibility checks
• Fallback to default '#storybook-root' selector if no custom selector is provided
• Aligns test runner behavior with the a11y addon's custom element selector feature

[greptile-apps]

LGTM

_{1 file(s) reviewed, no comment(s)
Edit PR Review Bot Settings}

[nx-cloud]

☁️ Nx Cloud Report

CI is running/has finished running commands for commit ee2c2bb. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this CI Pipeline Execution

---

✅ Successfully ran 1 target

• nx run-many -t build --parallel=3

---

Sent with 💌 from NxCloud.

[kylegach]

Thank you!

[jonniebigodes]

All is good on my end, going to merge this. Thank you.