---

Making a Semistandard Carbon Application Accessible

Many applications use HIObject and HIView objects, but may implement custom classes to represent some of the contents of those objects. An example is an application that creates a custom HIView to represent a custom control not provided by the system, such as a volume indicator control.

This chapter defines a semistandard Carbon application as one that fits the following criteria:

• It uses only HIObject and HIView objects to represent its user interface objects, although it may use custom classes to implement substructure.

• It is Carbon event driven.

• The accessibility hierarchy may deviate from the containment hierarchy defined by the HIObjects and HIViews.

If this describes your application, there are a few things you must do to make sure assistive applications can access all parts of your application’s user interface. This chapter describes the steps you take to access-enable the custom portions of your application. It does not describe the steps you take to access-enable the standard portions of your application. If you haven’t already, be sure to read “Making a Standard Carbon Application Accessible” to learn how to provide the context-specific attribute values all applications must supply.

Contents:

How Much Work Will This Be?
Create Accessibility Objects for Custom Subviews
Adjusting the Accessibility Hierarchy
Install Custom Event Handlers
Send Notifications

---