>
> > Still, I'd change the emphasis. Why not spend the majority of time on
> > how to actually solve problems now, rather than just saying what the
> > problems are?
> >
> > So much work has been put into this -- into specs, browsers, JavaScript
> > toolkits, screen readers, docs, etc. Right now the word isn't out there
> > about what can be done.
>











Well, how exactly is WAI-ARIA helping the needs of people with learning
disabilities or the hard of hearing? Day one is about opening our
horizons as developers to understand that to develop *real* accessible
products we need to listen to and talk to people who know the issues we
are trying to solve. Technology can help us there, but as tech geeks we
are far too fast to say we use technology XYZ and it'll solve
everything. Scripting Enabled is also about bridging the communication
barriers between non-tech and tech people, something in my experience is
one of the major issues of accessible development out there. Tech folk
don't want to heard details and non-tech folk go to sleep when people
start talking about markup changes and adding attributes.

As to the word not being out there - nobody is stopping you. I am
promoting any good article on WAI-ARIA on Ajaxian, Yahoo Developer
Network and my communication channels - happily. Bring it on :)



Chris