> is implementing X an appropriate expenditure of resources
Lot of these things just require devs to not actively try to damage the usability of the defaults. It costs money to break the basics that work for free:
- missing keyboard focus indicator? yeah, dev had to go out of his way to remove it, instead of just doing nothing and focusing on the job/content
- can't paste into inputs? someone had to think about preventing this and implemented it
- ctrl+k / ctrl+f is broken? it works if you just write you page and do nothing extra!
- page is blank for people with JS disabled? someone wasted money on a person who had to learn a whole damn programming language and multi-billion dollar company's framework instead of just html/css
Lot of these things just require devs to not actively try to damage the usability of the defaults. It costs money to break the basics that work for free:
- missing keyboard focus indicator? yeah, dev had to go out of his way to remove it, instead of just doing nothing and focusing on the job/content
- can't paste into inputs? someone had to think about preventing this and implemented it
- ctrl+k / ctrl+f is broken? it works if you just write you page and do nothing extra!
- page is blank for people with JS disabled? someone wasted money on a person who had to learn a whole damn programming language and multi-billion dollar company's framework instead of just html/css