Results / React Spectrum
100% against @adobe/react-spectrum@3.47.3. Every check below cites the clause it measures, and every failure carries the command that reproduces it.
Reproduce this whole run
Serve the adapter from a clone of the repository, then:
npx @railing-dev/runner run --target react-spectrum --component menu \
--repeat 3 \
--base-url http://localhost:5180Or replay it without running anything: download the Playwright trace and open it with npx playwright show-trace.
menu.trigger-has-accessible-namemenu.trigger-has-haspopupmenu.trigger-collapsed-by-defaultmenu.opens-on-entermenu.opens-on-down-arrowmenu.expanded-state-communicatedmenu.has-menu-rolemenu.items-have-menuitem-rolemenu.focus-enters-menu-on-openmenu.arrow-moves-between-itemsmenu.escape-closesmenu.focus-restored-on-closemenu.item-has-accessible-nameWhat this cannot tell you
A high score means no violations were detected by automated testing. It does not mean the component is accessible. Automated tests cannot judge whether a label is meaningful, whether a reading order makes sense, or whether the experience is usable with a screen reader. Those need human judgement and disabled users. This is a floor, not a ceiling.