The author could have easily written the same article with vague personal opinions of how their own code isn't perfect for a slightly different set of default a

The author could have easily written the same article with vague personal opinions of how their own code isn't perfect for a slightly different set of default assumptions of how buttons should be used. Not everyone wants to dive into <form> behavior oddities like changing element's default behaviors or automatically reloading the page on submission nor do they want to assume the best label in the graphical context always matches the best label in the screen reader context. Doesn't make their example actually bad, it just means short examples are always easy to nit about. One thing I liked about the article is it's a longer dive instead of a short answer, meaning you get more of the nuance presented to you instead of assumed. Of course, it looks like the same thing comes from either source if you set out to ask for a detailed explanation. Also, FWIW since these will all vary anyways, I do actually like the full answer I got from ChatGPT more overall than the one at the end of their article. Even despite that it doesn't bother mentioning form considerations it gives more full answers to the points in the "hand tailored" response, as well as covering when you should consider using a separate aria-label or not https://chatgpt.com/share/e/6754aaad-823c-8010-a5ad-96eff5f0948e https://chatgpt.com/share/e/6754aaad-823c-8010-a5ad-96eff5f0....