this might not be the highest priority on our list.
I totally agree. There are more important things to take care of first.
You probably created big accessibility issues
I’m not so sure about that. In the solutions I’ve looked at the checkboxes and the labels are still there. It’s just a matter of using an own pseudo elements to show the state of the checkbox.
there are going to be bugs in some browsers and platforms you didn’t test.
Most of the browsers has great support for pseudo elements (:checked for example):
If you look into it, it’s not really rocket sience:
It even falls back to the default on failure.
testing it in many browsers, platforms, on many devices, and with screen readers
If there really are a reason to test everything on every browser/device/os, then this is a nice tool for it:
The effort is very big
In not sure about that.
compared to the theoretical gains you were aiming for
Theoretical gains? How rude!
I think it’s completely acceptable if there are differences in look/style on different platforms.
I agree. It’s totally acceptable, but I always aim at perfection down to the pixel. I think this is a minor thing, but I still think it’s a thing.
Some form fields are tricky when it comes to styling them
In this case it’s just hide and replace with an own pseudo element. I don’t think there is a “native” way of styling them. But it’s great to still keep the real checkboxes around to keep the form functions attached to it.
it might not be worth the effort.
Maybe not today… but tomorrow (in tha future), right?
I still don’t want to say no to this, but I fully agree that we should push it to the future.