Obviously not, but you also shouldn't expect the whole world to be designed around your needs. If you have difficulty using the expected input method, you should use alternatives with the same functionality, not expect others to redesign their apps in your preferred way.
Design for the best accessibility first and foremost, then try and make things look "prettier".
Disabilities can affect anyone at any time and shouldn't be an afterthought.
Most of the terrible designs and accessibility problems stem from software going out its way to write custom controls or force controls to look and behave in a non-default way. It's not an afterthought--people are deliberately adding code to make their software worse.
You design a clear, visible, distinctive scroll bar and buttons? Boom, you've catered to everyone with bad vision (for any reason: from blindness to eye surgery), reduced motor skills (for any reason: from arthritis to old age to hand injuries), non-technical users (so they don't have to hunt around the interface hoping to discover hidden features).
And this goes for everything in software.
Disability is a spectrum, and you yourself will be disabled in one way or another, multiple times, during the course of your life. Be it from old age, surgeries, injuries, strain from sport or mundane tasks like holding a baby.
Yes
It is thr toolkit builder's job.
As an application developer you should not have to
I don't think anyone is expecting that. What's reasonable to expect is that these things are configurable so people can have a UI that works for them.