Re: [spec-reviews] ARIA (#107)

Léonie's points are important. In particular, they point to some fundamental problems with ARIA:

1. Developers have to do a lot of work to get it right, and can easily forget something or get it wrong
2. Developers are required, in this model, to implement interaction behaviour. This can only work reliably if they know the user's platform and the user's capabilities for interaction. But they do not, and can not. (This is the issue I first brought to the TAG in San Francisco in March last year). So we are asking them to solve a problem without the tools to do so.
3. For a lot of accessibility problems ARIA is irrelevant, since they don't involve any Accessibility API, but rather standard functionality. If browsers won't base behaviour on ARIA (and they probably canot re-engineer now to do so without introducing real compatibility issues) then it remains a very narrowly focused approach to a set of problems.

At the same time, it is actually useful and relatively successful in providing a practical resolution to the problems it actually addresses. We should make sure we don't throw out the baby with the bathwater.

---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/spec-reviews/issues/107#issuecomment-202310150