This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 22978 - [AAPI]: Update Sections 1 and 2
Summary: [AAPI]: Update Sections 1 and 2
Status: RESOLVED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML a11y APIs (editor: Steve Faulkner, Cynthia Shelly) (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Jason Kiss
QA Contact: HTML a11y API spec bugbot
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-08-15 20:59 UTC by Jason Kiss
Modified: 2014-12-07 21:43 UTC (History)
4 users (show)

See Also:


Attachments

Description Jason Kiss 2013-08-15 20:59:20 UTC
The Introduction and the section on Exposing HTML features that do not directly map to accessibility API properties should be updated. I suggest that at least the following changes be made:

1. Introduce the APIs in a way that matches how they are are presented in the mapping tables, e.g., explain UIAExpress, and why MSAA+UIAExpress and MSAA+IA2 are columns to themselves. 

2. Explain what an "accessible" is.

3. Update the use of <header> as the example in Section 2. A few of the APIs now assign specific roles for this element.

There's undoubtedly more that could be done to improve these sections.
Comment 1 Jason Kiss 2014-12-07 21:43:03 UTC
Document updated to more closely align with Core-AAM: A11y APIs introduced in way consistent with how they are presented in the mappings; "accessible object" included in glossary; use of <header> as example removed.