Table 2.0 GAP Analysis - Progressive Filling of the Gaps for HTML in support of Accessibility API

Required Components Related
UAAG Checkpoints 		Who does what today?
(HTML) 		Plan to fill the gaps for XHTML 1.X
 Plan to fill gaps for
XHTML 1.X + XForms 		XML Events Plan to fill the gaps for
XHTML 2.0
Events: 1.2  



FocusChange 1.2, 6.6, 7.1, 9.1 , 9.3 DOM 2 UI Events



Activation 1.2 DOM Level 2 Device Independent UI Events



Caret Change 9.1, 9.3, 9.7 User Agent API User Agent API User Agent API
User Agent API
* Value Change

6.4, 6.5 , 6.6 , 6.9

through activation of a form, the css attribute of an element may change to visible, content appears somewhere on the page, but the page is not refreshed. The user with a screen reader does not know any content has changed.

  User Agent to monitor specific accessibility properties in the AAA. For properties representing platform accessibility API values as specified by a given role, it will generate an accessible value change event. (See Value Change)

User Agent to monitor change from WAI State Taxonomy information  supplied by the Author
and fire the platform specific Accessibility API event
* State Change 6.5 , 6.6   User Agent to monitor specific accessibility properties in the AAA. For properties representing platform accessibility API states, it will generate an AccessibleState Change event. (See State Change Event)

User Agent to monitor change from WAI State Taxonomy information  supplied by the Author
and fire the platform specific Accessibility API event
Selection Change 1.1, 6.5 , 6.6 , 7.1, 10.2 User Agent API
 User Agent API
 User Agent API
User Agent API
Mutation

1.2, 6.4, 6.6 , 6.9

through activation of a form, the css attribute of an element may change to visible, content appears somewhere on the page, but the page is not refreshed. The user with a screen reader does not know any content has changed.

DOM Events



Accessible Actions:  




* Event Handler functional information and descriptive shortcuts

1.2 , 6.1, 6.2, 6.6, 9.6

? are xml events covered under 6.1 and 6.2

no mention of xml in 1.2 - is 1.2 generic enough to include xml?

 

  • XML Event handler "purpose" addition to XML Events

Details:Need for XML Events
  • access element
  • XML Event handler "purpose" addition to XML Events

Details:Need for XML Events*
* Access to the available event handlers for enumerating the actions 1.2, 6.5 DOM 3 Events



* State Information: 6.5, 6.6   Supplied by the AAA specification. User Agent to  map information found in XForms data model
with limited use of  AAA.

User Agent of XForms data model to accessible state meta found in:

(WAI States and Adaptable Properties Module)
User Agent to  map information found in XForms data model
with limited use of  AAA.

User Agent of XForms data model to accessible state meta found in:


(WAI States and Adaptable Properties Module)
* Role Information: 2.1 , 6.1 , 6.4, 6.5, 6.6 Limited to standard HTML tag names. (Mix Content/presentation)


Relationships: Parent/child 1.2, 6.1, 10.1, 10.4 Limited DOM (affected by style) (Mix Content/presentation)



Relationships: (Label, Group, ControllerFor) 2.3 , 6.1, 10.1 Limited to HTML (Title, alt, label) AAA Specification
  • AAA Specification
  • label, group acquired from XForms

label, group acquired from XForms incorporated into XHTML 2
Text: 1.1 , 1.2, 4.1, 4.2, 4.3, 6.1 Core DOM 1 from parsed HTML



Content selection: 1.1 , 5.4 , 6.3, 7.1 , 10.2 User Agent



Font/Font Style Information: 4.1, 4.2, 4.3, 4.14 , 6.3 , 6.4, 6.9 Can set but can’t get final format User Agents final format styling using CSS2 APIs
 User Agents final format styling using CSS2 APIs
User Agents final format styling using CSS2 APIs
* Description/Help: 2.3 , 2.7 , 6.1 limited to HTML 4.0 - Alt Text, title text AAA Specification
 Acquired from XForms help, hint
Acquired from XForms help, hint incorporated into XHTML 2
* Accessible value: 2.1 , 6.1, 9.9 limited to form elements
 AAA Specification
 User Agent acquires from XForms data model
User Agent Acquires from XForms data model incorporated into XHTML 2
Coordinates (Bounding rectangle, etc.): 6.3 , 6.4 User Agents.platform accessibility API



Accessible Name: 2.1 , 6.1 User Agent determines from HTML tag



* Respond Desktop Font/Color Changes 4.1, 4.2, 4.3, 4.14 , 6.3 , 6.4, 6.9 partial (conflicts with CSS and JavaScript) CSS3 - Requires User Agent support
 CSS3 - Requires User Agent support
CSS3 - Requires User Agent Support
* Device independent navigation: 1.1, 1.2, 9.1, 9.2, 9.3, 9.7, 9.9 Use of xhtml2 landmarks through the <link rel"">
 XHTML 2 Role land marks

 XHTML 2 Role land marks
XHTML 2 Role land marks,  and Access Key replacement
*Accessibility API Mapping: 6.1, 6.4, 6.7, partial - User Agents
 User Agent to map new AAA properties and role meta data to the platform accessibility API


Provide focus to all active elements
 1.1 , 6.5, 7.1, 9.1, 9.2, 9.3, 9.9 TABINDEX=-1 best practice
 TABINDEX
 TABINDEX
All XHTML 2 elements shall be focusable.

Updated November 14, 2005