AxsJAX Uses JavaScript — Isn That Inaccessible?
Web applications that use JavaScript have traditionally proven an access barrier to screen reader users for the following reasons: • Adaptive technologies cannot always interpret the meaning of actions invoked via JavaScript. • Asynchronous page updates leave screen readers at a loss as to what to speak. A set of W3C specifications collectively refered to as W3C ARIA is addressing these issues. Though AJAX applications will continue to remain unusable from legacy browsers like lynx, there is no reason why they should remain forever inaccessible to users of adaptive technologies. Finally, JavaScript in the browser is a powerful mechanism that has enabled us to turn the Web from a world of static documents to a platform for deploying dynamic end-user applications. The primary goal of the AxsJAX framework is to leverage these same advantages presented by JavaScript in the browser to create flexible, powerful accessibility solutions.
Related Questions
- Hushmail uses JavaScript, and I’m worried that there could be security problems with JavaScript. Is the use of JavaScript in Hushmail safe?
- Each tube uses approximately the same electricity as a 40-watt light bulb. How many lamps do you recommend for induct home installations?
- My current site uses PHP and javascript. Are these compatible with Common Ink?
