Comment by chrismorgan

Quite a bit of this, mainly later on, feels unjust. Many are problems about mobile devices, not the web. Sizes don’t mean what you might expect? They don’t on any platform. A pixel hasn’t been a physical pixel reliably for at least fifteen years, and far longer in some ecosystems. Physical units never matched reality reliably, which is part of the reason they have steadily been phased out or discouraged across all platforms (Firefox’s mozmm unit is a fun piece of history: it tried to be one physical millimetre).

> One way we could have ensured that designs are accessible is to make it impossible to build anything else.

The only way of achieving this is by hobbling the web in a way that I guarantee would have killed it.

> The <input> tag is like 30 years old, but that has apparently not been enough time for us to figure out how to make it usable!

It was enough time. <input> was fine. But then devices without physical keyboards came along, and ruined it.

You’ll have the same problems if you try adding text input to your landscape mobile game using the platform’s native toolkit. In these areas, the web is not the problem: phones are, due to their limited screen size and different input methods; and mixed-input devices/platforms are—Windows two-in-ones are full of touch/pen niggles Android doesn’t have, whether you’re web or native (and Android with a pointer has issues in the other direction).