65. Built-In APIs

The success of accessibility APIs depends on several critical factors. First, software developers must embrace the technology. If only a few applications support accessibility APIs, the technology cannot offer a significant accessibility improvement to the visually impaired. Truly accessible computing requires that the impaired have access to a wide range of tools comparable to those available to other users.

Further, the creators of accessibility solutions would have little incentive to support APIs that did not significantly increase the utility of their products. Assuming that the first requirement is met and software developers clamor to adopt accessibility APIs, successful implementation of the technology still faces important hurdles. While this discussion has referred to the technology as APIs in the plural, the technology will prove most beneficial if the number of different APIs is very small.

While asking that all software developers agree on a single API is a considerable request, such an effort would help the technology achieve its greatest potential. A single accessibility API would help ensure that a wide range of accessibility devices and computer applications could interact successfully. Because most applications and many hardware devices are designed for a specific family of operating systems (e.g., the Windows family or the Unix family), a single accessibility API for each operating system family would probably suffice.

With accessibility API technology introduced and some important goals identified, it is important to consider what steps society can take to make these proposals a reality. Who are the important players in the accessibility API arena? Clearly, companies currently offering accessibility solutions have an important role in supporting accessibility APIs. However, they already have a vested interest in the accessibility issue.