After the Svelte toolchain update in #310, npm run check reports an accessibility warning for the pointer-drag handler attached directly to .settings-header. The header contains the close button, so assigning an interactive role to the header would create invalid nested controls.
Keep the existing pointer drag behavior while moving event ownership to the already-semantic dialog and explicitly limit drag starts to the non-interactive header surface. Add a regression test and require npm run check to return with no warnings.
After the Svelte toolchain update in #310,
npm run checkreports an accessibility warning for the pointer-drag handler attached directly to.settings-header. The header contains the close button, so assigning an interactive role to the header would create invalid nested controls.Keep the existing pointer drag behavior while moving event ownership to the already-semantic dialog and explicitly limit drag starts to the non-interactive header surface. Add a regression test and require
npm run checkto return with no warnings.