On 26/05/2010 12:47 AM, Andres Gonzalez wrote: >> The downside is to app users not using AT but experiencing a >> performance degradation, however minor. > Not so minor in some cases. The question is why it isn't minor. That suggests that the accessibility code on the app side is doing too much that it doesn't necessarily need to do yet. For example, if something requests only one object, generating the entire tree doesn't make sense. There must be some way of doing this more "lazily". > And it can involved extra GUI as well. This indicates an app design issue. There shouldn't need to be extra GUI because someone is using an AT.
Jamie -- James Teh Vice President NV Access Inc, ABN 61773362390 Email: ja...@nvaccess.org Web site: http://www.nvaccess.org/ _______________________________________________ Accessibility-ia2 mailing list Accessibility-ia2@lists.linuxfoundation.org https://lists.linux-foundation.org/mailman/listinfo/accessibility-ia2
