3 ms·
No, this is confusing. Please iterate on this. Two buttons shouldn't do the same thing depending on state. I get it: the intent is that there's always a quick,
by secret-noun 3y ago
No, this is confusing. Please iterate on this. Two buttons shouldn't do the same thing depending on state.
I get it: the intent is that there's always a quick, one-click way to broadly consent/not consent. But with how this is designed, after clicking Accept All or Reject All, I'm left wondering what Confirm My Choices did. (Maybe it persists my consent on subsequent visits? I dunno.)
Perhaps, "Confirm My Choices" (or better put, simply "Submit") stays, but change the "Accept All" and "Reject All" buttons to "Select All" and "Deselect All" buttons, respectively. These buttons should only serve to change the state of the checkboxes without submitting.
- yoavm 3y agoWe actually started with having "Select All", "Deselect All" and "Submit", but users complained about the two clicks flow, and so we changed. UX is hard. I tend to think that the one click flow serves users and respects their time more, even if it comes at the cost of having confusion about the difference between "Confirm my choices" and "Reject all". It's bad when consent managers confuse users between agreeing and disagreeing, but if we're making users confused between two good options, I personally think it's an okay price for a one click and you're done experience.
- snowstormsun 3y ago> I tend to think that the one click flow serves users and respects their time more, even if it comes at the cost of having confusion about the difference between "Confirm my choices" and "Reject all". That's a fair tradeoff. "Reject all" should be one-click imho.