Introduction to Accessibility Programming Guidelines for Carbon

All Carbon applications can and should be accessible to users with disabilities. The process of making an application accessible is called access enabling. How big a job this is depends on the extent to which your application uses custom user interface objects.

If your Carbon application relies on HIObjects for all its user interface elements (including subclasses of HIView), most of the accessibility infrastructure is provided for you. If, on the other hand, your Carbon application uses some custom subclasses of HIObject or HIView or relies on a custom application framework, you need to supply more of the accessibility infrastructure yourself.

This document outlines how to access-enable applications throughout this range. It provides steps you can follow to access-enable an application that uses only HIObjects and HIViews in its user interface. It then provides guidelines to help you access-enable an application that implements custom views or depends on a custom application framework.

Who Should Read This Document

All Carbon application developers should read this document to learn how to make their applications accessible to users with disabilities. If you’re new to accessibility you should read Accessibility Programming Guide for OS X to get an overview of the Mac OS X accessibility architecture.

If you’re an assistive application developer, you don’t need to read this document. Instead, you should read Accessibility Programming Guide for OS X to become familiar with the Mac OS X accessibility architecture and then you should read Accessibility Reference for Assistive Applications.

Organization of This Document

This document has the following chapters:

See Also

The Accessibility Reference Library contains several documents that cover accessibility:

In addition to these documents, Apple maintains a website devoted to accessibility in Mac OS X, with links to more information about compatible assistive technologies: