This is reductionist and myopic. I've personally been through building forms online and it's hell to try to find consensus on perhaps the most common forms used online.

Let's take a credit card form:

- Do I let the user copy and paste values in?

- Do I let them use IE6?

- Do I need to test for the user using an esotoric browser (Brave) with an esoteric password manager (KeePassXC)?

- Do I make it accessible for someone's OpenClaw bot to use it?

- Do I make it inaccessible to a nefarious actor who uses OpenClaw to use it?

I could go on...

Balancing accessibility and usability is hard.[0]

[0] Steve Yegge's platform rant - https://gist.github.com/chitchcock/1281611

The thing that winds me up about credit card input is that it won't let me enter it as it is written on my card, in groups of four digits.

The same applies to fields that expect telephone numbers. They should all accept arbitrary amounts of white-space.

If you don't allow me to paste a card number in I might well not buy from you.

All you need to do is use standard HTML form elements. None of those questions are even relevant, just excuses to increase complexity and make things harder for everyone.

Funny, I'd assume we'd got consensus on that one.

- Anyone who recommends disabling paste as a security feature is a fraud

- Doing UA sniffing is always a mistake

- If the user's browser doesn't support `autocomplete="cc-number"` then they're already used to it not working, you don't need to care about it

- You should always make your form as accessible as possible regardless of if the user is a robot or visually impaired

- Making your website intentionally inaccessible may be a federal crime in the USA as the ADA doesn't care what you think about openclaw.