If you know what you are doing it isn't needed. You can solve nearly 60-70% of accessibility issues by writing good HTML. For most of the rest having a simple understanding of CSS and JavaScript events with concern what constitutes a disability you are probably ok.
Personally I often try to avoid ARIA. ARIA is generally there to complicate for problems in the interface. If you solve for those problems directly you don't need ARIA. The role attribute is an exception though, because its always helpful.
There are always edge cases, but if you avoid stupid marketing trickery and understand the web standards you are probably safer than that supposed JS ninja spinning their favorite framework bullshit.
If you know what you are doing it isn't needed. You can solve nearly 60-70% of accessibility issues by writing good HTML. For most of the rest having a simple understanding of CSS and JavaScript events with concern what constitutes a disability you are probably ok.
Personally I often try to avoid ARIA. ARIA is generally there to complicate for problems in the interface. If you solve for those problems directly you don't need ARIA. The role attribute is an exception though, because its always helpful.
There are always edge cases, but if you avoid stupid marketing trickery and understand the web standards you are probably safer than that supposed JS ninja spinning their favorite framework bullshit.