| > As you mentioned, without proof. I feel that claiming the web now consistently complies with ARIA is an incredibly bold claim, and the burden of proof is on you but you can test the top 50 websites yourself if you genuinely believe that. > are somewhat last resort when you can't do what you aim to do with bare HTML This thinking was popular 20 years ago when ARIA was created. Application-like behaviour, which nearly always means JS, is the majority of websites. > ARIA attributes were somewhat harmful Wasted engineering effort on minimally effective outcomes is harmful. > "software has had 50+ years to be bug free, let's put the burden on the users to deal with it since obviously developers can't do bug free". Others not following your religion is not a defect. |
... that I didn't make
> This thinking was popular 20 years ago when ARIA was created. Application-like behaviour, which nearly always means JS, is the majority of websites.
That's besides the point, your JS code still generates HTML. Writing applications in JS doesn't change anything about the topic.
What I'm saying is that you mostly don't need to use aria attributes with a good HTML structure, generated from JS or not. Use them sparingly when you can do it in pure HTML (again, generated or not).
> Others not following your religion is not a defect.
That's not an answer to the stuff you quoted and there's no religion here.
You have a point about web accessibility lacking but we'll have to disagree about "let's just give up good practice since it's not been perfect despite all these years". Actually, you are not claiming "not perfect", you are claiming "not present", but you're wrong on this as other commenters told you.