>Damon Rose wrote:
>
> If WAI-aria buys into newer technology and allows for a path forward
> rather than backward, then that's all good and needs encouragement
> rather than going back for older solutions. It may solve the immediate
> access problem but not future ones.

Keep in mind that WAI-ARIA makes it a lot easier for us to solve future
problems. It's not just a solution for current problems, but provides a
more general mechanism for adding accessibility information to web content.

I'm glad people will be looking at what the problems are without
specifically thinking about the solution. It will also be a good
exercise to see how WAI-ARIA would solve these problems.

Right now, the process of adding new features to WAI-ARIA has to be:
1) Draft proposal
2) Submit to W3C for discussion
3) If it gets in, make sure browsers expose the new WAI-ARIA semantics
correctly
4) Convince screen reader and other AT developers to utilize the new
information

In the future, we hope to simplify this process quite a bit. However, at
least there is a way forward. It's not necessary to be stuck in a rut.

- Aaorn