SXSW 2009 | Making Web Widgets Accessible

One of the tings that interests me in the dev community is the focus on accessibility. (Back in 1995 we used to build website with versions in Lnyx!) But when it comes to being accessible to those with disabilities, often these findings help all of us. I am constantly amazed and inspired by the collaborative ways in which the web is continually being developed--and would argue this collaboration lends life to the web. (Thanks Tim Berners-Lee :) No other medium I am aware of is developed like this.

Speakers: Michael Cooper (Accessibility Prod Mgr, W3C - World Wide Consortium), Shawn Henry (W3C Web Accessibility Initiative, WAI), Catherine Laws (IBM), Thomas Logan (VP of Product Development, HiSoftware), Richard Schwerdtfeger(Distinguished Engineer, IBM)

Description: Browser vendors, code library developers, and Ajax gurus demo best practices for making widgets and dynamic web content accessible. You'll also see how they're implementing W3C's new Accessible Rich Internet Applications Suite, WAI-ARIA (nearing completion or done by SXSW 2009!). Get tips and tricks for next generation web accessibility.

Thomas Logan:

Goal is to standardize keyboard interactions on the Web. ARIA allows for screen refresh without click and allows you to provide status to user. Can assist user in surfacing information. More info at codetalks.org.

Cathy Laws:

Talking about challenges to companies trying to support standards, especially ARIA. What users where need these app first? What tools do we use ... Adobe, OpenSource...? Need to develop accessibility of tool. Do we need to try out apps with every screen reader or just popular ones? Do we comply at basic compliance levels or go beyond that? How do we make social networking tools available?

We participate in Open Source projects and develop our own tools as well. We educate our teams by setting up a check list that harmonizes with standards coming out in different countries and set up information sharing tools from conferences to wikis to FAQs, etc. We encourage going beyond basic level A compliance. .Not just accessible but usable. More discoverable, logical, consistent, etc via usability. Incorporate people with disabilities in testing.

Shawn Henry:

WAI-ARIA overview overview is here: http://www.w3.org/WAI/intro/aria Currently in working draft.

Richard Schwerdtfeger:

Next step is application delivery will change according to user!