The problems you're blaming on Core Animation are just a problem of custom interfaces in general. If you're doing a custom interface, Core Animation isn't going to make accessibility any more work than, say, using NSCells and a custom view class that draws them in place.
It's like saying, "Well, the problem with using Core Animation on the iPhone is that if you're using Core Animation, it will limit your app to 128 MB of RAM." The 128 MB limit is inherent in the iPhone -- it's not something that's wrong with Core Animation. Similarly, lack of accessibility is inherent in custom interfaces -- it's not something that's wrong with Core Animation.
by Chuck — Oct 05
The problems you're blaming on Core Animation are just a problem of custom interfaces in general. If you're doing a custom interface, Core Animation isn't going to make accessibility any more work than, say, using NSCells and a custom view class that draws them in place.
It's like saying, "Well, the problem with using Core Animation on the iPhone is that if you're using Core Animation, it will limit your app to 128 MB of RAM." The 128 MB limit is inherent in the iPhone -- it's not something that's wrong with Core Animation. Similarly, lack of accessibility is inherent in custom interfaces -- it's not something that's wrong with Core Animation.