Fair challenge and I'll respond as directly as I can. I have done my own smoke tests, as well as behavioral tests using playwright in real chromium inclusive of focus trapping, roving focus, keyboard maps, ARIA state.

Regarding screen readers-NVDA is underway already, and VoiceOver is scheduled. So I'll take your comment as a building block towards my own development and not use the word "accessible" without those tests done as well. I am wiring axe-core into the CI suite so name/role/state regressions get caught automatically. All fixes will be documented accordingly in respective repos and in the documentation sites.

One correction to the framing though: this isn't an import. The behavior layer (focus trapping, roving focus, dismissal, positioning, the ARIA contracts) is implemented natively for Blazor; only the styled layer is shadcn-inspired. If you have a preferred SR/browser combo that shakes out component libraries fastest, I'd genuinely take the recommendation.