@Nick Caldwell: I'm terrible at browsing API documentation but I can't see anything that indicates the framework hooks into an OS's accessibility system
I agree with you it's an important point, but I'm not convinced it's something that's really in the hands of Cappuccino itself. Mac apps are much more tightly couple to the physical computer and have specific Accessibilities APIs to work with, provided by Apple. A web app, on the other hand, is just providing content to the browser to interpret as it will. The browser is ultimately responsible for handing off the data to the screen reader software.
I'm not sure how browsers like Safari and Firefox go about being the bridge between page content and the OS-specific Accessibility API, but I'm certain it's something they have to facilitate. Cappuccino isn't in a position to talk to directly the Accessibility frameworks on Mac OS X.
Asynchronous page updates are a reality of modern web apps. It's how Gmail, Google Maps, MobileMe, and countless other online services work. It's not at all specific to a single JavaScript framework.
If the Cappuccino application is entirely generated in the browser through complex javascript, I'd assume the result will simply be a blank page for a typical screen reader app
This part puzzles me. Why does the complexity of the JavaScript matter at all to the screen reader. It's not actually running the JavaScript, is it? Is the issue in determining visibility? This is a completely open-ended question -- I'm truly curious about the answer.
by Scott Stevenson — Sep 07
I agree with you it's an important point, but I'm not convinced it's something that's really in the hands of Cappuccino itself. Mac apps are much more tightly couple to the physical computer and have specific Accessibilities APIs to work with, provided by Apple. A web app, on the other hand, is just providing content to the browser to interpret as it will. The browser is ultimately responsible for handing off the data to the screen reader software.
I'm not sure how browsers like Safari and Firefox go about being the bridge between page content and the OS-specific Accessibility API, but I'm certain it's something they have to facilitate. Cappuccino isn't in a position to talk to directly the Accessibility frameworks on Mac OS X.
Asynchronous page updates are a reality of modern web apps. It's how Gmail, Google Maps, MobileMe, and countless other online services work. It's not at all specific to a single JavaScript framework.
If the Cappuccino application is entirely generated in the browser through complex javascript, I'd assume the result will simply be a blank page for a typical screen reader app
This part puzzles me. Why does the complexity of the JavaScript matter at all to the screen reader. It's not actually running the JavaScript, is it? Is the issue in determining visibility? This is a completely open-ended question -- I'm truly curious about the answer.