Re: UAAG 1.0 and Rich Internet Applications

I would add these programmatic access checkpoints as well:

Priority 1

6.1 Programmatic access to HTML/XML
6.2 DOM Access to HTML/XML
6.4 Programmatic access to information about rendered content
6.6 Programmatic notification of changes
- Updates needed based on DOM access versus accessibility APIs and how that
all works for both HTML pages as well as AJAX/ARIA Web apps in both Firefox
and IE.

Related to these checkpoints, I just realized I didn't mention IBM's
announcement  of a new open standard accessibility API extension to MSAA on
Windows - IAccessible2. It was announced on December 14, 2006. It will be
further developed and maintained as an open standard through the Free
Standards Group.

http://www-03.ibm.com/press/us/en/pressrelease/20773.wss

It has the potential to change the dependence on a browser's DOM, and for
Firefox 3 this dependence will change this year. We can talk about it some
at next week's UAAG meeting, but Aaron may also want to discuss it some at
the F2F.

Cathy Laws

Manager - IBM Software Group (SWG) Accessibility Architecture and
Development
11501 Burnet Road,  Bldg 902 Office 2C016, Austin, Texas 78758
Phone: (512) 838-4595  FAX: (512) 246-8502
E-mail: claws@us.ibm.com, Web: http://www.ibm.com/able

Make a careful exploration of who you are and the work you have been given,
and then sink yourself into that. Don't be impressed with yourself. Don't
compare yourself with others. Each of you must take responsibility for
doing the creative best you can with your own life.  Eugene Peterson


                                                                           
             Jan Richards                                                  
             <jan.richards@uto                                             
             ronto.ca>                                                  To 
             Sent by:                  WAI-UA list <w3c-wai-ua@w3.org>     
             w3c-wai-ua-reques                                          cc 
             t@w3.org                                                      
                                                                   Subject 
                                       UAAG 1.0 and Rich Internet          
             01/12/2007 01:27          Applications                        
             PM                                                            
                                                                           
                                                                           
                                                                           
                                                                           
                                                                           





Hi,

This is the result of my action item to crunch Jim's Issue Tracking
document (http://www.tsbvi.edu/technology/uawg/issues-jan11.htm) down
into a listing of areas of UAAG 1.0 that we think might be most affected
by the advent of AJAX Rich Internet Application technologies such as
AJAX... ("AJAX" will be the shorthand used in this message)

PRIORITY 1:

1.3 Provide text messages (P1)
2.1 Render content according to specification (P1)
- Accessible notification of user about changes in content when specific
content is refreshed without a total page refresh (Reference WAI-ARIA)

2.4 Allow time-independent interaction (P1)
3.5 Toggle automatic content retrieval (P1)
- AJAX refresh out of UA control

3.1 Toggle background images (P1)
- what happens if background images used in AJAX widgets and images are
turned off?

3.2 Toggle audio, video, animated images (P1)
3.3 Toggle animated or blinking text (P1)
- AJAX can be used to create animations [JR added]

8.1 Implement accessibility features (P1)
TABINDEX and ACCESSKEY as currently implemented are confusing to end
users. Although TABINDEX=-1 and ACCESSKEY are used extensively in AJAX
and new web applications. How to resolve? [JR: not sure what this refers
to]

9.1 Provide content focus (P1)
- need to update the definitions of "enable elements" and "interactive
elements" to provide for components used in DHTML/AJAX. Definition
change may impact the scope of other checkpoints.

9.2 Provide user interface focus (P1)
- Related to Compound Documents and DHTML/AJAX. Focus management between
base UA and nested/child UA (Object, flash, mathml, svg).


PRIORITY 2:

7.3 Respect operating environment conventions (P2)
- There are some issues between AJAX widgets/controls and High contrast
mode and alternate keyboard interfaces (sticky keys)

9.5 No events on focus change (P2)
- often events on AJAX controls important

11.2 Current author input configuration (P2)
11.3 Allow override of bindings (P2)
- How should UA expose author specified keybindings that occur in AJAX
which are not exposed in the DOM or to accessibility APIs. [should this
be a WCAG requirement?]
- if can't see AJAX bindings how can they be over-ridden?


PRIORITY 3:

None.



----

Cheers,
Jan