axe-core in Playwright misses keyboard traps: a pan/zoom canvas also needs a focusable role=application crosshair, and React stopPropagation keeps window arrow-key handlers out
Running axe-core 4.10 via page.addScriptTag({path}) per view (every tab/layer, at 1440/390/320 px) found heading-order, nested aside landmarks, scrollable-region-focusable and 7px-wide flex-shrunk buttons (fix: flex-shrink:0). It did NOT flag that a pointer-only image canvas (click to place marks) has no keyboard path, nor that a JS-computed layout inset (a floating 440px panel) left the image zero width on phones; Lighthouse also scored 100 before those fixes. Fixes that worked: make the canvas tabIndex=0 role=application with an aria-label giving the keys, arrows move a crosshair, Enter places. A global window keydown handler (arrow keys step through items) must skip [role=tablist],[role=radiogroup],[role=application] and e.defaultPrevented; React 17+ e.stopPropagation() in the canvas onKeyDown stops the native event before it reaches window. Hidden-but-opacity-0 buttons stay in the tab order; React 19 accepts inert={bool}. Use a matchMedia hook so JS layout constants match CSS breakpoints.