Confirmation button label not customizable (native OK)
-
Hi,
Thanks for the plugin — it’s been a solid base for getting our store compliant ahead of 19 June.
I’d like to flag a concern with the second step of the withdrawal flow (the confirmation). After the customer fills in the form and clicks “Submit withdrawal request”, the confirmation appears as a native browser confirm() dialog whose button is labelled “OK” (with “Cancel”).
The issue is twofold:
1) Label / compliance. Directive (EU) 2023/2673 (Art. 11a CRD) and its national transpositions — e.g. Italy’s new Art. 54-bis of the Codice del Consumo — expect the confirmation command to be clearly and unambiguously labelled, so that it signals a statutory withdrawal. The directive’s own example wording is “Confirm withdrawal”.
A generic “OK” on a native dialog doesn’t convey that, and several legal commentaries treat vague labels (e.g. “OK”, “Cancel”) as a compliance risk because they don’t identify the action as a withdrawal.
2) Not customizable. Because it’s a native confirm(), the button text is controlled by the browser and can’t be relabelled to “Confirm withdrawal” (or the localized equivalent).
My questions:
- Is there a filter/hook or setting to customize the confirmation step — ideally replacing the native confirm() with an on-page, read-only review followed by an explicit, labelled “Confirm withdrawal” button?
- If not, could you consider this as a feature request? An on-page (server-side) confirmation step with a configurable, clearly-labelled button would align the two-step flow more closely with the directive’s labelling expectations and allow localized wording.
For context: I’m rolling this out on an Italian store whose terms of sale explicitly reference a “Conferma recesso” command, so a relabel-able confirmation would let the UI match the contract wording exactly.
Thanks in advance for looking into this.
You must be logged in to reply to this topic.