Forums Feature Requests Thread

[Enhancement] Accessibility: native confirm() audit on data-confirm forms

Patrick Bass · Jun 3 · 25 · 1 Locked
[Low Priority] [Feature Enhancement] [Deployed to Production]
🚀 OP Jun 3, 2026 6:00pm

What

The platform standard is to use the branded App.modal.confirm() helper instead of native browser confirm(). Several destructive-action forms still carry a data-confirm attribute that falls through to native if JS does not load. This sweep audits and rewrites them to use the modal helper exclusively.

Where it lives

  • Surface: every page with a destructive form (delete, ban, revoke, etc.)
  • Backlog id: B-A11Y-1

Implementation notes

  • grep for data-confirm across templates/
  • Replace bare native fallback paths with a dedicated confirmation route or guaranteed inline modal
  • Standing memory: native confirm() / alert() / prompt() banned anywhere on the platform

Tracked as B-A11Y-1 in docs/BACKLOG.md.


Patrick Bass
@mobieus

🚀 Jun 6, 2026 5:34am

Update — shipped to production. Native-dialog sweep complete. Destructive actions confirm through the branded in-page modal, and the last native browser pop-ups in the app have been replaced with inline toasts. No native confirm/alert/prompt remain anywhere in the platform.


Patrick Bass
@mobieus

Log in or register to reply to this thread.