Enjoyed the read and I'm always happy to see people put the effort in to understand the Web better. One thing at the end, though: kinda sounds like the author got to a place where they conclude "welp, some stuff like select elements and tables are just too complicated to rely on HTML I guess"... And the thing is that's not 100% wrong, but it misses the larger and more important point of understanding the _role_ of the elements you are using. In essence HTML is just shorthand for a lot of other things you'd have to do (including marking up the correct role). It would have been more fulfilling if instead he reached some epiphany more like: "I realized even when the HTML element doesn't cover 100% of the use case, I realized it's a great place to start reading what other _role_s and aria-descriptions need to be added to that div to make it correct, robust and meaningful"
