And my point is that discrimination is an active effort, which this is not. Things are, by default, not accessible, because things are generally crafted for able bodied humans.
Where did you get the idea that discrimination has to be the result of an active effort? Anything that makes one group of people excluded or treated worse is discrimination, even if it is the result of an oversight.
Your second sentence is basically exactly the problem: able-bodied people are arbitrarily treated as the “default”, and others are left out.
People like you are exactly why laws like ADA were created and collectively we have decided not to just disagree with you but to pass legislation that makes it illegal for people to follow this lazy and selfish position. The first fights were over physical access and in a lot of cases it required significant reconstruction or re-architecting of spaces at great expense. The next round of fights will be over online access, where the cost of compliance is significantly less -- expect tech firms to start losing these battles now that it is much easier to attach specific harm to failures to provide accessibility.
> Able bodied people are the default because they are the absolutely overwhelming majority.
Almost everyone develops some disabilities as they age. 10-15% of the population has some disability, which is a huge group. I hope you would not argue for discrimination against ethnic minorities on the same grounds.
> And my point is that discrimination is an active effort, which this is not.
That is an absolutely incorrect and indefensible point. Discriminators can be individuals, but discrimination is systemic. It can be a result of collective acts of malice over years or generations, or can be simple ignorance- being left out of the scope of the discourse and never really given a chance to get in the loop.
Discrimination absolutely does not require an active effort. Neglect is just as effective at keeping people out.
In any case Cloudflare's inaccessibility is a direct result of choices they "actively" made. Technical decisions, prioritization, maybe even company culture.
It's not a matter of agreeing; it's a matter of the US govt is saying these are the rules for doing commerce or hiring employees in the US. As codified by the ADA. Post domino case, that clearly applies to company websites.
I don't think I've ever seen a news website with no cookie warnings. Cookies are necessary for the functionality of the ad networks and analytics tools that news websites need to survive. Not to mention the rest of gdpr requirements.
Of course that registry actually has a sane punycode policy, so such impersonations are impossible there, whereas they're happening all the time in .com. Maybe time to re-evaluate your idea of "reality" versus "theory".
Not for English speaking people, as a Dane it is nice to be able to use our actual alphabet to spell words, even if the letters weren't in the ASCII alphabet.
Though why you should be able to purchase .com domains with punycode, I don't know.
Each TLD gets to set its own rules for name registration under that TLD. In particular they all have punycode policies. For example a country which uses a Latin alphabet with a handful of extra characters might requires names under its ccTLD to be from that alphabet, and not, for example, Cyrillic. Or a TLD operated on behalf of a region dominated by one writing system might require names to use that writing system. The attention of TLD registry operators was drawn to the need to prevent the exact types of fraud we're seeing here.
The .com TLD registry's priority is profit at any cost. A crook's money is just as good as anybody else's, right?
Apple's supreme UX and mobile hardware aside, no one in their right mind, who's serious about privacy, would ever use android. The amount of hoops you need to jump through to degoogle an android device (with continuous degoogled upgrades) is insane.
Android is perfect for the burner phones though, the ones that you trash after a call or 2 (still, expect that every sensor possible will be reporting it's data back to "a manufacturing party" the moment you activate it)