RE: summary of backward compat discussion

>> 2)      Web-like behavior vs. application-like behavior
>>
>> Web-page behavior would be tabbing to each element and hitting
>> enter to open it.  Application behavior would be tabbing between
>> widgets and using arrows and shortcut keys to navigate within a
>> widget.  Both would be controls that react to both tab+enter
>> navigation and arrow key navigation.
>>
>> Should widgets support web-page like behavior, application-like
>> behavior or both?  Which will be more usable for AT users?

Are you saying the  controls in the application will be tab-navigable and
operable with Enter key with older browsers and AT and the exact same
application will be navigable with arrow keys using ARIA enabled browsers
and AT? If both styles of navigation and activation are available with newer
browsers and AT, it will be very confusing. Or does one have to provide
redundant controls to accommodate backward compatibility and the two styles
of navigation and activation of UI controls? 

Would it not be possible to include the nodes within a list so that a screen
reader user would be able to move to end of list directly without  the use
of the skip link?

The transitioning is going to be very challenging: developers saying they
are using ARIA in their Web 2.0 sites while users have to wait for browsers
and AT to catch up. Sufficient techniques for WCAG 2 for ARIA too need to
evolve.

Sailesh Panchang
Accessibility Services Manager (Web and Software)
Deque Systems Inc. (www.deque.com)
11130 Sunrise Valley Drive, Suite #140,
Reston VA 20191
Phone: 703-225-0380 (ext 105)
E-mail: sailesh.panchang@deque.com

Received on Monday, 22 September 2008 19:56:43 UTC