Dennis Deacon

ARIA should be used as a precise surgical tool to fill HTML's semantic gaps, not as a blanket solution. Common mistakes include overusing aria-label on non-interactive elements and creating mismatches between visible text and screen reader announcements. HTML should always be the first choice, with ARIA applied only when necessary and with deep understanding to avoid breaking accessibility.

ARIA and Real World Dangers

Love the example. This is especially dangerous when copying code from one file to the other.
I think the main problem is that we as “normal” devs are not using the HTML in the same way people using assistive technology use them.
If we would start using Accessibility trees to traverse websites and web apps, i think it would be way more often detected that there actually is an issue.
Its like making a website responsive with CSS but never testing the site on mobile.