Web accessibility describes specific requirements for people with disabilities to be able to use your website. If you don't implement these features, blind people, colorblind people, people who can't use a mouse, etc., won't be able to use your website. You can make a strategic choice not to support these users for reasons like ROI. But obviously there are plenty of situations where either we make the affirmative choice not to exclude people with disabilities, or we're required by law to accommodate them. In my personal opinion, we should always build on the web with the modern features that support assistive technologies, and that building inaccessible web experiences is synonymous with building poor quality web experiences. Many of the (mostly native) features that enable an experience accessible to people with disabilities improve the experience for all users.
The fascinating thing about accessibility is that (unlike many other characteristics) all of us are going to be at least temporarily disabled at some point in our lives. I've really appreciated the presence of ramps whenever I've injured my foot, or just if I'm rolling a couple heavy suitcases.
The EU has an Accessibility Act coming into play from June this year, so a subset of companies working on things like travel booking systems will have to test to make sure they meet those new requirements.
Your position is really "fuck disabled people", really?
Your ever seen a blind person try to use the internet? You ever seen a person with essential tremors try to use their phone?
Go and educate yourself a little.
These standards are all built from the experiences of users who were unable to access things and they benefit way more than the 15% of people who have disabilities. Ever used closed captioning, automatic doors, or curb cuts? Those things all started as accessibility features.
