Technique proposal for A.1.2.1

Still more to do.  Here are the first two:

A.1.2.1 Non-Web-Based Accessible: Non-web-based authoring tool user 
interfaces follow (and cite in the conformance claim) accessibility 
standards and/or platform conventions that support accessibility. (Level A)

Intent of the Success Criterion A.1.2.1:
The intent of this success criterion is to ensure that non-web-based 
authoring tool user interfaces are accessible to authors with 
disabilities. Since accessibility standards and platform conventions 
exist for many platforms, those documents are referenced to avoid 
replication of requirements.

Examples that meet the Success Criterion:
WYSIWYG on MacOS
A WYSIWYG text editor is designed in Cocoa following the Mac OS X 
accessibility framework including using Accessibility Objects setting 
attributes for Role, Role Description, Description, Title, Relationship 
and Value. No custom actions are defined and all actions can be 
performed through the keyboard. Hit-testing has been implemented to pass 
current focus to assistive technologies. The recommended and reserved 
keyboard shortcuts for Apple Human Interface Guidelines and for Mac OS X 
accessibility are included in the application and not overwritten. The 
conformance claim includes links to the Accessibility Programming 
Guidelines for Carbon and the Accessibility Keyboard Shortcuts as 
applicable.

Content Management System on Windows
A content management system is written to operate on the Windows 
XP/Vista operating systems. following the Microsoft's Active 
Accessibility. The programs uses IAccessible proxies and only implements 
IAccessible for controls that are not proxied by OLEACC. The conformance 
claim includes links to the the applicable Microsoft Developer Network 
documents.

Received on Monday, 14 September 2009 18:45:58 UTC